path: root/doc/src/compiling.xml

<preface>
	<para>
You need <ulink url="http://www.gtk.org/">Glib</ulink> to compile this stuff.
Take <ulink url="http://www.gimp.org/win32/">the binary distribution</ulink> or compile it
yourself (look into <filename>extras</filename> subdirectory for an example).
	</para>
</preface>

<section>
	<title>Compiling from CVS</title>
	<para>
Run <command>autogen.sh</command>. I used automake 1.8.5, autoconf 2.59
and libtool 1.5.10.
With earlier versions it may not work because some command line options
aren't supported.
Then use <command>configure</command> script as described below.
	</para>
</section>

<section>
	<title>Compiling from source tarball</title>
	<para>
Just use <command>configure &amp;&amp; make</command>.
Option <option>--enable-relocatable</option> affects the location of
configuration directory: if specified, <option>sysconfdir</option>
is prepended with <quote>.</quote>.
For example, if you run
		<screen>
./configure --sysconfdir=/etc --enable-relocateble</screen>
then <command>syslogd.exe</command> and client will read their
configuration file from <filename>etc</filename> subdirectory
located in the same directory with executable file.
	</para>
</section>

<section>
	<title>Compiling documentation</title>
	<para>
You should have DocBook and DocBook Website installed in your system.
Go to <filename>doc/book</filename> directory and run, for example:
<screen>
xmlto html-nochunks syslog-win32.xml</screen>
	</para>
	<para>
Go to <filename>doc/website</filename> directory and issue the following commands:
<screen>
xsltproc --output autolayout.xml \
	http://docbook.sourceforge.net/release/website/2.6/xsl/autolayout.xsl \
	layout.xml
	
xsltproc --stringparam output-root htdocs \
	stylesheets/chunk-tabular.xsl \
	autolayout.xml</screen>
	</para>
</section>

<section>
	<title>Building binary distribution</title>
	<para>
At first, compile documentation in <filename>doc/book</filename>.
Then use <command>build.sh</command>. It does all you need.
You should have some packages&nbsp;&mdash; look into the script
to see which ones.
Also, you should have <ulink url="http://www.jrsoftware.org">Inno Setup</ulink>
with ISPP installed in your system.
	</para>
	
	<section>
		<title>on UNIX</title>
		<para>
You should have cross compiler and <ulink url="http://winehq.org">Wine</ulink>
installed.
Wine is required to run Inno Setup Compiler and the directory in which
you are going to build should be accessible via some drive letter.
		</para>
		<para>
Assuming target triplet is <emphasis>i686-pc-mingw32</emphasis>,
iscc is in its default directory <filename>c:\program files\inno setup 5</filename>
and required packages are in <filename>./distfiles</filename>:
			<screen>
DISTFILES=distfiles \
ISCC=c:\\program\ files\\inno\ setup\ 5\\iscc.exe \
HOST=i686-pc-mingw32 \
./build.sh</screen>
		</para>
	</section>
	
	<section>
		<title>on Windows</title>
		<para>
I've noticed that <ulink url="http://www.mingw.org/msys.shtml">Msys</ulink> has troubles
running some native command-line applications.
So you'll have to run Inno Setup by hand.
			<screen>
DISTFILES=&lt;path to the directory with packages&gt; \
./build.sh</screen>
		</para>
	</section>
</section>