This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: user-manual.sgml,v 1.27 2002/01/11 14:14:32 hal9 Exp $
+ $Id: user-manual.sgml,v 1.28 2002/02/24 14:34:24 jongfoster Exp $
Written by and Copyright (C) 2001 the SourceForge
IJBSWA team. http://ijbswa.sourceforge.net
<artheader>
<title>Junkbuster User Manual</title>
-<pubdate>$Id: user-manual.sgml,v 1.27 2002/01/11 14:14:32 hal9 Exp $</pubdate>
+<pubdate>$Id: user-manual.sgml,v 1.28 2002/02/24 14:34:24 jongfoster Exp $</pubdate>
<authorgroup>
<author>
Thanx David Schmidt!
-->
-<para>
- The OS/2 version of <application>Junkbuster</application> requires the EMX
- runtime library to be installed. The EMX runtime library is available on
- the hobbes OS/2 archive, among many other locations:
- <ulink url="http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=emxrt.zip&stype=all&sort=type&dir=%2Fpub%2Fos2%2Fdev%2Femx%2Fv0.9d">http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=emxrt.zip&stype=all&sort=type&dir=%2Fpub%2Fos2%2Fdev%2Femx%2Fv0.9d</ulink>
-</para>
-
<para>
<application>Junkbuster</application> is packaged in a WarpIN self-
installing archive. The self-installing program will be named depending
on the release version, something like:
- <filename>ijbos123.exe</filename>. In order to install it, simply run
- this executable or double-click on its icon and follow the WarpIN
+ <filename>ijbos2_setup_1.2.3.exe</filename>. In order to install it, simply
+ run this executable or double-click on its icon and follow the WarpIN
installation panels. A shadow of the <application>Junkbuster</application>
executable will be placed in your startup folder so it will start
automatically whenever OS/2 starts.
<para>
If you would like to build binary images on OS/2 yourself, you will need
- a working EMX/GCC environment, plus several Unix-like tools. The Hobbes
- OS/2 archive is a good place to start when building such an environment.
- A set of Unix-like tools named gnupack is located here:
- <ulink url="http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&key=gnupack&stype=all&sort=type&dir=%2Fpub%2Fos2%2Fapps">http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&key=gnupack&stype=all&sort=type&dir=%2Fpub%2Fos2%2Fapps</ulink>
-</para>
-<para>
- Once you have the source code unpacked as above, you can build the binaries
- from the <filename>current/</filename> directory:
+ a few Unix-like tools: autoconf, autoheader and sh. These tools will be
+ used to create the required config.h file, which is not part of the
+ source distribution because it differs based on platform. You will also
+ need a compiler.
+ The distribution has been created using IBM VisualAge compilers, but you
+ can use any compiler you like. GCC/EMX has the disadvantage of needing
+ to be single-threaded due to a limitation of EMX's implementation of the
+ select() socket call.
</para>
<para>
+ In addition to needing the source code distribution as outlined earlier,
+ you will want to extract the <filename>os2seutp</filename> directory from CVS:
+ <screen>
+ cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
+ cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
+ cd current
+ </screen>
+ This will create a directory named os2setup/, which will contain the
+ <filename>Makefile.vac</filename> makefile and <filename>os2build.cmd</filename>
+ which is used to completely create the binary distribution. The sequence
+ of events for building the executable for yourself goes something like this:
<screen>
+ cd current
+ autoheader
autoconf
sh configure
- make
+ cd ..\os2setup
+ nmake -f Makefile.vac
</screen>
+ You will see this sequence laid out in <filename>os2build.cmd</filename>.
</para>
</sect2>
Temple Place - Suite 330, Boston, MA 02111-1307, USA.
$Log: user-manual.sgml,v $
+ Revision 1.28 2002/02/24 14:34:24 jongfoster
+ Formatting changes. Now changing the doctype to DocBook XML 4.1
+ will work - no other changes are needed.
+
Revision 1.27 2002/01/11 14:14:32 hal9
Added a very short section on Templates