>Privoxy</SPAN
>
into will contain all of the configuration files.</P
-><P
-> If you would like to build binary images on OS/2 yourself, you will need
- 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
- <TT
-CLASS="FUNCTION"
->select()</TT
-> socket call.</P
-><P
-> In addition to needing the source code distribution as outlined earlier,
- you will want to extract the <TT
-CLASS="FILENAME"
->os2seutp</TT
-> directory from CVS:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="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
- </PRE
-></TD
-></TR
-></TABLE
->
- This will create a directory named os2setup/, which will contain the
- <TT
-CLASS="FILENAME"
->Makefile.vac</TT
-> makefile and <TT
-CLASS="FILENAME"
->os2build.cmd</TT
->
- which is used to completely create the binary distribution. The sequence
- of events for building the executable for yourself goes something like this:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> cd current
- autoheader
- autoconf
- sh configure
- cd ..\os2setup
- nmake -f Makefile.vac
- </PRE
-></TD
-></TR
-></TABLE
->
- You will see this sequence laid out in <TT
-CLASS="FILENAME"
->os2build.cmd</TT
->.</P
></DIV
><DIV
CLASS="SECT3"