2000-05-23 01:55:31 +00:00
|
|
|
#
|
2002-10-11 20:15:50 +00:00
|
|
|
# NuFX archive manipulation library
|
2007-02-19 23:12:22 +00:00
|
|
|
# Copyright (C) 2000-2007 by Andy McFadden, All Rights Reserved.
|
2002-10-11 20:15:50 +00:00
|
|
|
# This is free software; you can redistribute it and/or modify it under the
|
2007-02-19 23:12:22 +00:00
|
|
|
# terms of the BSD License, see the file COPYING-LIB.
|
2002-10-11 20:15:50 +00:00
|
|
|
#
|
|
|
|
|
# Makefile for nufxlib (should work with non-GNU "make").
|
2000-05-23 01:55:31 +00:00
|
|
|
#
|
|
|
|
|
# You can use:
|
|
|
|
|
# make (builds library and sample applications)
|
|
|
|
|
# make shared (builds shared library if you're using GNU ld or similar)
|
|
|
|
|
#
|
2002-10-11 20:15:50 +00:00
|
|
|
# The shared library support currently leaves much to be desired.
|
|
|
|
|
#
|
Distinguish Unicode and Mac OS Roman strings
NufxLib has historically made no effort to distinguish between
the character set used for filenames on the local disk, and for
filenames stored within the archive. Now all Unicode filename
strings use the UNICHAR type and have "UNI" in the name, and all
Mac OS Roman strings have "MOR" in the name. (The naming
convention makes it obvious when you're assigning the wrong thing;
on Linux both formats are char*, so the compiler won't tell you
if you get it wrong.)
The distinction is necessary because filesystems generally support
Unicode these days, but on Windows you need to use a separate
set of wide-character file I/O functions. (On Linux it all works
with "narrow" strings, and the UTF-8 encoding is interpreted by
applications.) The character set used for NuFX archive filenames
is MOR, matching what GS/OS + HFS supported, and we want to be able
to convert back and forth between MOR and a Unicode representation.
This change updates the various character types and string names,
adds conversion functions, and updates NuLib2 for proper execution
on Linux. It does not include the (probably extensive) changes
required for Windows UTF-16 support. Instead, the conversion
functions are no-ops, which should result in NuLib2 for Windows
continuing to behave in the same slightly broken way.
This adds "test-names", which exercises Unicode filenames a bit.
It will not pass on Win32.
Also, tweaked the Linux makefiles to have explicit dependencies,
rather than empty space and an expectation that "makedepend" exists.
Also, minor source code cleanups.
While this probably doesn't affect binary compatibility -- it's
mainly a matter of naming and string interpretation -- there's
enough going on that it should be considered an API revision, so
this updates the version to 3.0.0.
2014-12-24 19:14:32 +00:00
|
|
|
# If you build with -DDEBUG_MSGS, nulib2 will be able to use the hidden
|
|
|
|
|
# 'g' command, which generates a verbose archive dump for debugging.
|
|
|
|
|
#
|
2000-05-23 01:55:31 +00:00
|
|
|
|
|
|
|
|
# NufxLib install location.
|
|
|
|
|
prefix = @prefix@
|
|
|
|
|
exec_prefix = @exec_prefix@
|
|
|
|
|
includedir = @includedir@
|
|
|
|
|
libdir = @libdir@
|
|
|
|
|
srcdir = @srcdir@
|
|
|
|
|
|
|
|
|
|
SHELL = @SHELL@
|
|
|
|
|
INSTALL = @INSTALL@
|
|
|
|
|
INSTALL_PROGRAM = @INSTALL_PROGRAM@
|
|
|
|
|
INSTALL_DATA = @INSTALL_DATA@
|
|
|
|
|
CC = @CC@
|
|
|
|
|
AR = ar rcv
|
|
|
|
|
#OPT = @CFLAGS@ -DNDEBUG
|
|
|
|
|
OPT = @CFLAGS@
|
|
|
|
|
#OPT = @CFLAGS@ -DDEBUG_MSGS
|
|
|
|
|
#OPT = @CFLAGS@ -DDEBUG_VERBOSE
|
|
|
|
|
GCC_FLAGS = -Wall -Wwrite-strings -Wstrict-prototypes -Wpointer-arith -Wshadow
|
2018-08-08 03:47:56 +00:00
|
|
|
CFLAGS = @BUILD_FLAGS@ -I. @DEFS@ -fPIC -DOPTFLAGSTR="\"$(OPT)\""
|
2000-05-23 01:55:31 +00:00
|
|
|
|
Distinguish Unicode and Mac OS Roman strings
NufxLib has historically made no effort to distinguish between
the character set used for filenames on the local disk, and for
filenames stored within the archive. Now all Unicode filename
strings use the UNICHAR type and have "UNI" in the name, and all
Mac OS Roman strings have "MOR" in the name. (The naming
convention makes it obvious when you're assigning the wrong thing;
on Linux both formats are char*, so the compiler won't tell you
if you get it wrong.)
The distinction is necessary because filesystems generally support
Unicode these days, but on Windows you need to use a separate
set of wide-character file I/O functions. (On Linux it all works
with "narrow" strings, and the UTF-8 encoding is interpreted by
applications.) The character set used for NuFX archive filenames
is MOR, matching what GS/OS + HFS supported, and we want to be able
to convert back and forth between MOR and a Unicode representation.
This change updates the various character types and string names,
adds conversion functions, and updates NuLib2 for proper execution
on Linux. It does not include the (probably extensive) changes
required for Windows UTF-16 support. Instead, the conversion
functions are no-ops, which should result in NuLib2 for Windows
continuing to behave in the same slightly broken way.
This adds "test-names", which exercises Unicode filenames a bit.
It will not pass on Win32.
Also, tweaked the Linux makefiles to have explicit dependencies,
rather than empty space and an expectation that "makedepend" exists.
Also, minor source code cleanups.
While this probably doesn't affect binary compatibility -- it's
mainly a matter of naming and string interpretation -- there's
enough going on that it should be considered an API revision, so
this updates the version to 3.0.0.
2014-12-24 19:14:32 +00:00
|
|
|
SRCS = Archive.c ArchiveIO.c Bzip2.c Charset.c Compress.c Crc16.c \
|
|
|
|
|
Debug.c Deferred.c Deflate.c Entry.c Expand.c FileIO.c Funnel.c \
|
2002-10-09 23:12:06 +00:00
|
|
|
Lzc.c Lzw.c MiscStuff.c MiscUtils.c Record.c SourceSink.c \
|
|
|
|
|
Squeeze.c Thread.c Value.c Version.c
|
Distinguish Unicode and Mac OS Roman strings
NufxLib has historically made no effort to distinguish between
the character set used for filenames on the local disk, and for
filenames stored within the archive. Now all Unicode filename
strings use the UNICHAR type and have "UNI" in the name, and all
Mac OS Roman strings have "MOR" in the name. (The naming
convention makes it obvious when you're assigning the wrong thing;
on Linux both formats are char*, so the compiler won't tell you
if you get it wrong.)
The distinction is necessary because filesystems generally support
Unicode these days, but on Windows you need to use a separate
set of wide-character file I/O functions. (On Linux it all works
with "narrow" strings, and the UTF-8 encoding is interpreted by
applications.) The character set used for NuFX archive filenames
is MOR, matching what GS/OS + HFS supported, and we want to be able
to convert back and forth between MOR and a Unicode representation.
This change updates the various character types and string names,
adds conversion functions, and updates NuLib2 for proper execution
on Linux. It does not include the (probably extensive) changes
required for Windows UTF-16 support. Instead, the conversion
functions are no-ops, which should result in NuLib2 for Windows
continuing to behave in the same slightly broken way.
This adds "test-names", which exercises Unicode filenames a bit.
It will not pass on Win32.
Also, tweaked the Linux makefiles to have explicit dependencies,
rather than empty space and an expectation that "makedepend" exists.
Also, minor source code cleanups.
While this probably doesn't affect binary compatibility -- it's
mainly a matter of naming and string interpretation -- there's
enough going on that it should be considered an API revision, so
this updates the version to 3.0.0.
2014-12-24 19:14:32 +00:00
|
|
|
OBJS = Archive.o ArchiveIO.o Bzip2.o Charset.o Compress.o Crc16.o \
|
|
|
|
|
Debug.o Deferred.o Deflate.o Entry.o Expand.o FileIO.o Funnel.o \
|
2002-10-09 23:12:06 +00:00
|
|
|
Lzc.o Lzw.o MiscStuff.o MiscUtils.o Record.o SourceSink.o \
|
|
|
|
|
Squeeze.o Thread.o Value.o Version.o
|
2000-05-23 01:55:31 +00:00
|
|
|
|
|
|
|
|
STATIC_PRODUCT = libnufx.a
|
|
|
|
|
SHARED_PRODUCT = libnufx.so
|
|
|
|
|
PRODUCT = $(STATIC_PRODUCT)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Build stuff
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
all: $(PRODUCT) samples
|
|
|
|
|
@true
|
|
|
|
|
|
|
|
|
|
install: $(STATIC_PRODUCT)
|
|
|
|
|
$(srcdir)/mkinstalldirs $(libdir)
|
|
|
|
|
$(INSTALL_DATA) $(STATIC_PRODUCT) $(libdir)
|
2020-10-15 03:18:02 +00:00
|
|
|
$(srcdir)/mkinstalldirs $(includedir) $(libdir)/pkgconfig
|
2000-05-23 01:55:31 +00:00
|
|
|
$(INSTALL_DATA) NufxLib.h $(includedir)
|
2020-10-15 03:18:02 +00:00
|
|
|
$(INSTALL_DATA) nufxlib.pc $(libdir)/pkgconfig
|
2000-05-23 01:55:31 +00:00
|
|
|
|
|
|
|
|
install-shared: $(SHARED_PRODUCT)
|
|
|
|
|
$(srcdir)/mkinstalldirs $(libdir)
|
|
|
|
|
$(INSTALL_DATA) $(SHARED_PRODUCT) $(libdir)
|
2020-10-15 03:18:02 +00:00
|
|
|
$(srcdir)/mkinstalldirs $(includedir) $(libdir)/pkgconfig
|
2000-05-23 01:55:31 +00:00
|
|
|
$(INSTALL_DATA) NufxLib.h $(includedir)
|
2020-10-15 03:18:02 +00:00
|
|
|
$(INSTALL_DATA) nufxlib.pc $(libdir)/pkgconfig
|
2000-05-23 01:55:31 +00:00
|
|
|
|
2019-05-04 21:00:48 +00:00
|
|
|
samples:: $(STATIC_PRODUCT)
|
2000-05-23 01:55:31 +00:00
|
|
|
@echo "Building samples..."
|
|
|
|
|
@(cd samples; set +e; unset CFLAGS OBJS; set -e; \
|
|
|
|
|
@SET_MAKE@ LIB_PRODUCT="../$(PRODUCT)" $(MAKE))
|
|
|
|
|
|
|
|
|
|
shared::
|
|
|
|
|
PRODUCT="$(SHARED_PRODUCT)" $(MAKE) -e
|
|
|
|
|
|
|
|
|
|
$(STATIC_PRODUCT): $(OBJS)
|
2002-10-01 01:05:42 +00:00
|
|
|
-rm -f $(STATIC_PRODUCT) $(SHARED_PRODUCT)
|
2000-05-23 01:55:31 +00:00
|
|
|
$(AR) $@ $(OBJS)
|
|
|
|
|
@RANLIB@ $@
|
|
|
|
|
|
Distinguish Unicode and Mac OS Roman strings
NufxLib has historically made no effort to distinguish between
the character set used for filenames on the local disk, and for
filenames stored within the archive. Now all Unicode filename
strings use the UNICHAR type and have "UNI" in the name, and all
Mac OS Roman strings have "MOR" in the name. (The naming
convention makes it obvious when you're assigning the wrong thing;
on Linux both formats are char*, so the compiler won't tell you
if you get it wrong.)
The distinction is necessary because filesystems generally support
Unicode these days, but on Windows you need to use a separate
set of wide-character file I/O functions. (On Linux it all works
with "narrow" strings, and the UTF-8 encoding is interpreted by
applications.) The character set used for NuFX archive filenames
is MOR, matching what GS/OS + HFS supported, and we want to be able
to convert back and forth between MOR and a Unicode representation.
This change updates the various character types and string names,
adds conversion functions, and updates NuLib2 for proper execution
on Linux. It does not include the (probably extensive) changes
required for Windows UTF-16 support. Instead, the conversion
functions are no-ops, which should result in NuLib2 for Windows
continuing to behave in the same slightly broken way.
This adds "test-names", which exercises Unicode filenames a bit.
It will not pass on Win32.
Also, tweaked the Linux makefiles to have explicit dependencies,
rather than empty space and an expectation that "makedepend" exists.
Also, minor source code cleanups.
While this probably doesn't affect binary compatibility -- it's
mainly a matter of naming and string interpretation -- there's
enough going on that it should be considered an API revision, so
this updates the version to 3.0.0.
2014-12-24 19:14:32 +00:00
|
|
|
# BUG: we need -fPIC, maybe -D_REENTRANT when compiling for this.
|
2002-10-08 23:56:38 +00:00
|
|
|
# BUG: for Linux we may want -Wl,-soname,libnufx.so.1 on the link line.
|
2000-05-23 01:55:31 +00:00
|
|
|
$(SHARED_PRODUCT): $(OBJS)
|
2002-10-01 01:05:42 +00:00
|
|
|
-rm -f $(STATIC_PRODUCT) $(SHARED_PRODUCT)
|
|
|
|
|
$(CC) @SHARE_FLAGS@ -o $@ $(OBJS) @LIBS@
|
2000-05-23 01:55:31 +00:00
|
|
|
|
|
|
|
|
clean:
|
|
|
|
|
(cd samples; make clean)
|
|
|
|
|
-rm -f *.o core
|
|
|
|
|
-rm -f $(SHARED_PRODUCT) $(STATIC_PRODUCT)
|
|
|
|
|
|
|
|
|
|
# build tags; assumes fancy GNU tag generation
|
|
|
|
|
tags::
|
|
|
|
|
@ctags -R --totals *
|
|
|
|
|
@#ctags *.[ch]
|
|
|
|
|
|
|
|
|
|
distclean: clean
|
|
|
|
|
(cd samples; make distclean)
|
|
|
|
|
-rm -f Makefile Makefile.bak
|
|
|
|
|
-rm -f config.log config.cache config.status config.h
|
|
|
|
|
-rm -f tags
|
|
|
|
|
|
2006-02-19 01:55:20 +00:00
|
|
|
# Make a tarfile with a backup of the essential files. We include "Makefile"
|
|
|
|
|
# so that we can do a "make distclean" during packaging.
|
2000-05-23 01:55:31 +00:00
|
|
|
baktar:
|
|
|
|
|
@tar cvf nufxlib.tar *.txt COPYING-LIB INSTALL configure *.in Makefile \
|
2006-02-19 01:55:20 +00:00
|
|
|
Makefile.msc Makefile.dll install-sh config.guess config.sub \
|
|
|
|
|
mkinstalldirs *.[ch] samples/*.txt samples/Makefile* samples/*.[ch]
|
2000-05-23 01:55:31 +00:00
|
|
|
@gzip -9 nufxlib.tar
|
|
|
|
|
@mv -i nufxlib.tar.gz /home/fadden/BAK/
|
|
|
|
|
|
Distinguish Unicode and Mac OS Roman strings
NufxLib has historically made no effort to distinguish between
the character set used for filenames on the local disk, and for
filenames stored within the archive. Now all Unicode filename
strings use the UNICHAR type and have "UNI" in the name, and all
Mac OS Roman strings have "MOR" in the name. (The naming
convention makes it obvious when you're assigning the wrong thing;
on Linux both formats are char*, so the compiler won't tell you
if you get it wrong.)
The distinction is necessary because filesystems generally support
Unicode these days, but on Windows you need to use a separate
set of wide-character file I/O functions. (On Linux it all works
with "narrow" strings, and the UTF-8 encoding is interpreted by
applications.) The character set used for NuFX archive filenames
is MOR, matching what GS/OS + HFS supported, and we want to be able
to convert back and forth between MOR and a Unicode representation.
This change updates the various character types and string names,
adds conversion functions, and updates NuLib2 for proper execution
on Linux. It does not include the (probably extensive) changes
required for Windows UTF-16 support. Instead, the conversion
functions are no-ops, which should result in NuLib2 for Windows
continuing to behave in the same slightly broken way.
This adds "test-names", which exercises Unicode filenames a bit.
It will not pass on Win32.
Also, tweaked the Linux makefiles to have explicit dependencies,
rather than empty space and an expectation that "makedepend" exists.
Also, minor source code cleanups.
While this probably doesn't affect binary compatibility -- it's
mainly a matter of naming and string interpretation -- there's
enough going on that it should be considered an API revision, so
this updates the version to 3.0.0.
2014-12-24 19:14:32 +00:00
|
|
|
# dependency info
|
|
|
|
|
COMMON_HDRS = NufxLibPriv.h NufxLib.h MiscStuff.h SysDefs.h
|
|
|
|
|
Archive.o: Archive.c $(COMMON_HDRS)
|
|
|
|
|
ArchiveIO.o: ArchiveIO.c $(COMMON_HDRS)
|
|
|
|
|
Bzip2.o: Bzip2.c $(COMMON_HDRS)
|
|
|
|
|
Charset.o: Charset.c $(COMMON_HDRS)
|
|
|
|
|
Compress.o: Compress.c $(COMMON_HDRS)
|
|
|
|
|
Crc16.o: Crc16.c $(COMMON_HDRS)
|
|
|
|
|
Debug.o: Debug.c $(COMMON_HDRS)
|
|
|
|
|
Deferred.o: Deferred.c $(COMMON_HDRS)
|
|
|
|
|
Deflate.o: Deflate.c $(COMMON_HDRS)
|
|
|
|
|
Entry.o: Entry.c $(COMMON_HDRS)
|
|
|
|
|
Expand.o: Expand.c $(COMMON_HDRS)
|
|
|
|
|
FileIO.o: FileIO.c $(COMMON_HDRS)
|
|
|
|
|
Funnel.o: Funnel.c $(COMMON_HDRS)
|
|
|
|
|
Lzc.o: Lzc.c $(COMMON_HDRS)
|
|
|
|
|
Lzw.o: Lzw.c $(COMMON_HDRS)
|
|
|
|
|
MiscStuff.o: MiscStuff.c $(COMMON_HDRS)
|
|
|
|
|
MiscUtils.o: MiscUtils.c $(COMMON_HDRS)
|
|
|
|
|
Record.o: Record.c $(COMMON_HDRS)
|
|
|
|
|
SourceSink.o: SourceSink.c $(COMMON_HDRS)
|
|
|
|
|
Squeeze.o: Squeeze.c $(COMMON_HDRS)
|
|
|
|
|
Thread.o: Thread.c $(COMMON_HDRS)
|
|
|
|
|
Value.o: Value.c $(COMMON_HDRS)
|
|
|
|
|
Version.o: Version.c $(COMMON_HDRS) Makefile
|
2000-05-23 01:55:31 +00:00
|
|
|
|
