Updated.

CHANGELOG

@@ -2,6 +2,7 @@
  * CHANGELOG.
  */
 
+08292002 - Fixed a mistake in makeos2.cmd, and updated the INSTALL docs.
 08292002 - Added a physfs/stdio wrapper header to the "extras" dir,
            compliments of Adam D. Moss (file is "abs-file.h").
 08282002 - Cleanups in grp.c so that Visual C++ doesn't complain anymore.

INSTALL

@@ -17,7 +17,7 @@ If you've got Doxygen (http://www.doxygen.org/) installed, you can run it
 
 
 
-UNIX and BeOS:
+UNIX:
 (If you got this code from CVS, run "./bootstrap" first.)
 
 Run ./configure --help and see what features can be optionally enabled or
@@ -29,26 +29,34 @@ As root, run "make install".
 If you get sick of the library, run "make uninstall" as root and it will
 remove all traces of the library from the system paths.
 
-BeOS doesn't seem to be building shared libraries with the version of
-autoconf/automake I used (even though it swears it did). If anyone has some
-insight into this, I'd like to hear from you.
+Primary Unix development is done with GNU/Linux, but PhysicsFS is known to
+work out of the box with several flavors of Unix. It it doesn't work, patches
+to get it running can be sent to icculus@clutteredmind.org.
 
 
+BeOS:
+Use the "Unix" instructions, above.
+
+
+AtheOS:
+Use the "Unix" instructions, above.
+
 
 WIN32:
 If building with CygWin, mingw32 or something else that uses the GNU
 toolchain, follow the Unix instructions, above.
 
-Point Visual Studio 6.0 at "physfs.dsp" in the root of the source tree, and
-build. This will produce a "physfs.dll" and "physfs.lib" (shared library and
-import lib, respectively) in either a "Debug" or "Release" directory,
-depending on what configuration you chose to build. After building the lib,
-you can make sure it works by building the "test_physfs.dsp" project file,
-which will create "test_physfs.exe" in "Debug" or "Release". This EXE is
-linked against the DLL you built previously.
+If you're using Visual C++ 6, point it at "physfs.dsp" in the root of the
+source tree, and build. This will produce a "physfs.dll" and "physfs.lib"
+(shared library and import lib, respectively) in either a "Debug" or
+"Release" directory, depending on what configuration you chose to build.
+After building the lib, you can make sure it works by building the
+"test_physfs.dsp" project file, which will create "test_physfs.exe" in
+"Debug" or "Release". This EXE is linked against the DLL you built
+previously.
 
-Visual Studio.NET probably handles these files, but we'll have honest-to-god
-.vcproj files in the next official release.
+Visual Studio.NET users should do the same thing, but use the "physfs.vcproj"
+and "test_physfs.vcproj" project files instead.
 
 If you're using another compiler, send me a patch when you get it working.  :)
 
@@ -82,24 +90,34 @@ You (currently) need to use the freeware Apple Developer Tools, which are
 based on the GNU toolchain. Fire up a terminal and run "cc"...if this reports
 "no input files" then you've got the tools installed.
 
-From a terminal, run "./configure --disable-shared --enable-static". Run
-"make". This will get you a static library and a "test_physfs" binary.
-
-I would love for someone to fix this so it will build shared libraries (since
-static libraries make it awkward to deal with the license terms), or send me
-Project Builder libraries.
+Follow the Unix directions, above (configure, make, make install).
 
 If someone is willing to maintain prebuilt PhysicsFS Shared Libraries for
 MacOS X, I'd like to hear from you; send an email to icculus@clutteredmind.org.
 
 
+OS/2:
+You need EMX installed. I tried this on a stock Warp 4 install, no fixpaks.
+I used the latest EMX and patches (which are several years old now). You need
+to install link386.exe (Selective Install, "link object modules" option). Once
+EMX is installed correctly, unpack the source to PhysicsFS and run the script
+file "makeos2.cmd". I know this isn't ideal, but I wanted to have this build
+without users having to hunt down a "make" program (While several exist, EMX
+doesn't come with one). If someone wants to hack some REXX to make this a bit
+more piccky about recompiling, I'll accept the patch.
+
+If someone is willing to maintain prebuilt PhysicsFS Shared Libraries for
+OS/2, I'd like to hear from you; send an email to icculus@clutteredmind.org.
+
 
 OTHER PLATFORMS:
 Many Unix-like platforms might "just work" with the GNU autoconf tools. Some
 of these platforms are known to have worked at one time, but have not been
-heavily tested, if tested at all. To implement a new platform or archiver,
-please read the heavily-commented physfs_internal.h and look in the platform/
-and archiver/ directories for examples.
+heavily tested, if tested at all. PhysicsFS is, as far as we know, 64-bit and
+byteorder clean, and is known to compile on several compilers across many
+platforms. To implement a new platform or archiver, please read the
+heavily-commented physfs_internal.h and look in the platform/ and archiver/
+directories for examples.
 
 --ryan. (icculus@clutteredmind.org)
 

TODO

@@ -13,7 +13,7 @@ These are in no particular order. A 1.0 release is reliant on doing most of
   it.
 - Need PHYSFS_LANG_GERMAN.
 - I'm a little nervous about the use of linked lists in qpak.c.
-- Add qpak.c and PHYSFS_SUPPORTS_QPAK to mac classic and win32 projects.
+- Add qpak.c and PHYSFS_SUPPORTS_QPAK to mac classic and vc++6 projects.
 - Figure out that pesky pthread casting problem.
 - macclassic.c :
   "/* (Hmm. Default behaviour is broken in the base library.  :)  )  */"