From cc8f289f09deb74308fd061b2959c860537f42c5 Mon Sep 17 00:00:00 2001 From: Andy McFadden Date: Wed, 19 Mar 2003 01:24:46 +0000 Subject: [PATCH] Updated for v2.0.0 release. --- nufxlib-0/ChangeLog.txt | 2 ++ nufxlib-0/README.txt | 11 +++++------ nulib2/ChangeLog.txt | 2 ++ nulib2/README.txt | 22 ++++++++++------------ 4 files changed, 19 insertions(+), 18 deletions(-) diff --git a/nufxlib-0/ChangeLog.txt b/nufxlib-0/ChangeLog.txt index 8e37ca6..1fa2a1c 100644 --- a/nufxlib-0/ChangeLog.txt +++ b/nufxlib-0/ChangeLog.txt @@ -1,3 +1,5 @@ +2003/03/18 ***** v2.0.0 shipped ***** + 2003/03/10 fadden - Added support for automatic high-ASCII text stripping. diff --git a/nufxlib-0/README.txt b/nufxlib-0/README.txt index 8e00275..c9ecc58 100644 --- a/nufxlib-0/README.txt +++ b/nufxlib-0/README.txt @@ -1,4 +1,4 @@ -NufxLib README, updated 2002/10/11 +NufxLib README, updated 2003/03/18 http://www.nulib.com/ See "COPYING-LIB" for distribution restrictions. @@ -41,10 +41,9 @@ for @CFLAGS@ is "-g -O2". -DDEBUG_VERBOSE (Implicitly sets DEBUG_MSGS.) Spray lots of debugging output. -If you want to do benchmarks, use "-O2 -DNDEBUG". For pre-v1.0 sources, -setting -DNDEBUG is otherwise discouraged. The recommended configuration -is "-g -O2 -DDEBUG_MSGS", so that verbose debug output is available when -errors occur. +If you want to do benchmarks, use "-O2 -DNDEBUG". The recommended +configuration during testing is "-g -O2 -DDEBUG_MSGS", so that verbose +debug output is available when errors occur. The flags are stuffed into Version.c, so the application program can examine and display the flags that were used to build the library. @@ -105,7 +104,7 @@ define it by default.) Legalese ======== -NufxLib, a NuFX archive manipulation library +NufxLib, a NuFX archive manipulation library. Copyright (C) 2000-2002 by Andy McFadden, All Rights Reserved. This library is free software; you can redistribute it and/or diff --git a/nulib2/ChangeLog.txt b/nulib2/ChangeLog.txt index ffd13db..17c1eea 100644 --- a/nulib2/ChangeLog.txt +++ b/nulib2/ChangeLog.txt @@ -1,3 +1,5 @@ +2003/03/18 ***** v2.0.0 shipped ***** + 2003/02/18 fadden - When extracting with "-ee", disk images now have ".PO" appended. - Resurrected HandleAddNotFound(). diff --git a/nulib2/README.txt b/nulib2/README.txt index e8d07f7..bd80b69 100644 --- a/nulib2/README.txt +++ b/nulib2/README.txt @@ -1,4 +1,4 @@ -NuLib2 README, updated 2002/10/11 +NuLib2 README, updated 2003/03/18 http://www.nulib.com/ @@ -19,14 +19,14 @@ 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. -If you have diabled deflate or enabled bzip2 support in libnufx.a, you +If you have disabled deflate or enabled bzip2 support in libnufx.a, you will need to provide the same --enable-METHOD or --disable-METHOD flag to configure here. If you're using shared libraries then the link -dependencies are taken care of and you don't need to worry. +dependencies are taken care of and you don't need to do anything. Run "make depend" if you have makedepend, and then type "make". This should leave you with an executable called "nulib2". If you like, -"make install" will put things into your install directory, usually +"make install" will copy files into your install directory, usually /usr/local/bin/ and /usr/local/man/. You can change this by using "./configure --prefix=directory". @@ -69,8 +69,8 @@ to build with debugging info, or nmake -f makefile.msc nodebug=1 to build optimized. -See the notes in Makefile.msc for building with zlib, libbz2, and against -NufxLib as a DLL. +See the notes in Makefile.msc for building with zlib, libbz2, and when +NufxLib is in a DLL. Other Notes @@ -105,12 +105,10 @@ vs Win32 NuLib2): in them, e.g. "nulib2 v foo.shk > out.orig" and "nulib2 v new.shk > out.new". - Edit both of the "out" files with vi. Do a global search-and-replace - to change '/' to ':' in out.new (:%s/\//:/g) so the filename separator - doesn't mess up the comparison. - - Do a global search-and-replace in both files to set the file dates - to be the same. I used ":%s/..-...-.. ..:../01-Jan-00 00:00/". This - is necessary because, like ShrinkIt, NuLib displays the date on which - the files were archived, not when they were last modified. + in both files to set the file dates to be the same. I used + ":%s/..-...-.. ..:../01-Jan-00 00:00/". This is necessary because, + like ShrinkIt, NuLib displays the date on which the files were archived, + not when they were last modified. - Sort both files, with ":%!sort". This is necessary because you added the files with '*' up above, so the NuLib2-created archive has the top-level files alphabetized.