2014-12-23 19:29:01 +00:00
|
|
|
NufxLib README, updated 2014/12/23
|
2000-05-23 01:55:31 +00:00
|
|
|
http://www.nulib.com/
|
|
|
|
|
|
|
|
See "COPYING-LIB" for distribution restrictions.
|
|
|
|
|
|
|
|
|
|
|
|
UNIX
|
|
|
|
====
|
|
|
|
|
|
|
|
Run the "configure" script. Read through "INSTALL" if you haven't used
|
|
|
|
one of these before, especially if you want to use a specific compiler
|
|
|
|
or a particular set of compiler flags.
|
|
|
|
|
2002-10-09 23:12:06 +00:00
|
|
|
You can disable specific compression methods with "--disable-METHOD"
|
|
|
|
(run "sh ./configure --help" to see the possible options). By default,
|
|
|
|
all methods are enabled except bzip2.
|
|
|
|
|
2000-05-23 01:55:31 +00:00
|
|
|
Run "make depend" if you have makedepend, and then type "make". This will
|
|
|
|
build the library and all of the programs in the "samples" directory.
|
|
|
|
There are some useful programs in "samples", described in a README.txt
|
|
|
|
file there. In particular, you should run samples/test-basic to verify
|
|
|
|
that things are more or less working.
|
|
|
|
|
|
|
|
If you want to install the library and header file into standard system
|
|
|
|
locations (usually /usr/local), run "make install". To learn how to
|
|
|
|
specify different locations, read the INSTALL document.
|
|
|
|
|
|
|
|
There are some flags in "OPT" you may want to use. The "autoconf" default
|
|
|
|
for @CFLAGS@ is "-g -O2".
|
|
|
|
|
|
|
|
-DNDEBUG
|
|
|
|
Disable assert() calls and extra tests. This will speed things up,
|
|
|
|
but errors won't get caught until later on, making the root cause
|
|
|
|
harder to locate.
|
|
|
|
|
|
|
|
-DDEBUG_MSGS
|
|
|
|
Enable debug messages. This increases the size of the executable,
|
|
|
|
but shouldn't affect performance. When errors occur, more output is
|
|
|
|
produced. The "debug dump" feature is enabled by this flag.
|
|
|
|
|
|
|
|
-DDEBUG_VERBOSE
|
|
|
|
(Implicitly sets DEBUG_MSGS.) Spray lots of debugging output.
|
|
|
|
|
2003-03-19 01:24:46 +00:00
|
|
|
If you want to do benchmarks, use "-O2 -DNDEBUG". The recommended
|
2014-12-23 19:29:01 +00:00
|
|
|
configuration is "-g -O2 -DDEBUG_MSGS", so that verbose debug output is
|
|
|
|
available when errors occur.
|
2000-05-23 01:55:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
BeOS
|
|
|
|
====
|
|
|
|
|
|
|
|
This works just like the UNIX version, but certain defaults have been
|
|
|
|
changed. Running configure without arguments under BeOS is equivalent to:
|
|
|
|
|
|
|
|
./configure --prefix=/boot --includedir='${prefix}/develop/headers'
|
|
|
|
--libdir='${exec_prefix}/home/config/lib' --mandir='/tmp'
|
|
|
|
--bindir='${exec_prefix}/home/config/bin'
|
|
|
|
|
|
|
|
If you're using BeOS/PPC, it will also do:
|
|
|
|
|
|
|
|
CC=cc CFLAGS='-proc 603 -opt full'
|
|
|
|
|
|
|
|
|
2003-06-24 20:40:28 +00:00
|
|
|
Mac OS X
|
|
|
|
========
|
|
|
|
|
|
|
|
This works just like the UNIX version, with the exception that when you link
|
|
|
|
against nufxlib, your project must also link against the Carbon framework.
|
|
|
|
This can be done in ProjectBuilder by using the Add Framework option in the
|
|
|
|
Project menu, or by adding "-framework Carbon" to the gcc command line.
|
|
|
|
|
|
|
|
You'll see some warnings due to some namespace collisions between nufxlib and
|
|
|
|
Carbon, but everything will work fine. Carbon is used to provide support for
|
|
|
|
file types and resource forks.
|
|
|
|
|
|
|
|
|
2000-05-23 01:55:31 +00:00
|
|
|
Win32
|
|
|
|
=====
|
|
|
|
|
|
|
|
If you're using an environment that supports "configure" scripts, such as
|
|
|
|
DJGPP, follow the UNIX instructions.
|
|
|
|
|
2014-12-23 19:29:01 +00:00
|
|
|
NufxLib has been tested with Microsoft Visual C++ 12 (Visual Studio 2013).
|
|
|
|
To build NufxLib, run the "Visual Studio 2013 x86 Native Tools Command
|
|
|
|
Prompt" shortcut to get a shell. Change to the nufxlib directory, then:
|
|
|
|
|
2002-09-21 00:59:25 +00:00
|
|
|
nmake -f makefile.msc
|
2000-05-23 01:55:31 +00:00
|
|
|
|
2014-12-23 19:29:01 +00:00
|
|
|
When the build finishes, run "test-basic.exe" to confirm things are working.
|
2002-12-06 01:04:20 +00:00
|
|
|
|
2014-12-23 19:29:01 +00:00
|
|
|
If you want to have zlib support enabled, you will need to have zlib.h,
|
|
|
|
zconf.h, and zlib.lib copied into the directory. See "makefile.msc" for
|
|
|
|
more details.
|
2000-05-23 01:55:31 +00:00
|
|
|
|
2014-12-23 19:29:01 +00:00
|
|
|
The makefile builds NufxLib as a static library and as a DLL.
|
2002-12-06 01:04:20 +00:00
|
|
|
|
2000-05-23 01:55:31 +00:00
|
|
|
|
|
|
|
Other Notes
|
|
|
|
===========
|
|
|
|
|
|
|
|
If you want to use the library in a multithreaded application, you should
|
|
|
|
define "USE_REENTRANT_CALLS" to tell it to use reentrant versions of
|
|
|
|
certain library calls. This defines _REENTRANT, which causes Solaris to
|
|
|
|
add the appropriate goodies. (Seems to me you'd always want this on, but
|
|
|
|
for some reason Solaris makes you take an extra step, so I'm not going to
|
|
|
|
define it by default.)
|
|
|
|
|
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
|
|
|
Originally, NufxLib / NuLib2 were intended to be usable natively on the
|
|
|
|
Apple IIgs, so some of the design decisions were influenced by the need
|
|
|
|
to minimize memory usage (e.g. being able to get a directory listing
|
|
|
|
without holding the entire directory in memory) and interact with GS/OS
|
|
|
|
(forked files have a single filename, files have type/auxtype). The IIgs
|
|
|
|
port was never started.
|
|
|
|
|
2002-10-08 23:56:38 +00:00
|
|
|
|
|
|
|
Legalese
|
|
|
|
========
|
|
|
|
|
2003-03-19 01:24:46 +00:00
|
|
|
NufxLib, a NuFX archive manipulation library.
|
2014-12-23 19:29:01 +00:00
|
|
|
Copyright (C) 2000-2014 by Andy McFadden, All Rights Reserved.
|
2007-02-19 23:12:22 +00:00
|
|
|
|
|
|
|
See COPYING for license.
|
2002-10-08 23:56:38 +00:00
|
|
|
|