idolpx/fsp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

We are using SCons instead of autoconf. Change first part of INSTALL document

Browse Source
This commit is contained in:
Radim Kolar 2009-09-02 00:05:44 +02:00
parent 7243c9def9
commit cb757b635f
1 changed files with 22 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
INSTALL
View File

@ -1,25 +1,32 @@
How to run FSP:
The first step in running this fine software (:) is to get it to The first step in running this fine software (:) is to get it to
compile. Every effort on my part will be made to make this code compile. Every effort on my part will be made to make this code
compile and run on any reasonable system. The information in this compile and run on any reasonable system. The information in this
file CURRENTLY pertains only to Unix and Cygwin users. file CURRENTLY pertains only to Unix and probably to Cygwin users.
Configuration: Building:
The first step is to run the configure script provided in this FSP uses SCons software construction tool. Building was tested
directory. This will generate a good makefile and a file called with SCons 1.2.0 and Python 2.5, but older versions will probably
config.h in the include directory. These files are vital for the work fine. Prior to building FSP you need to download and install
compilation of the system. SCons from http://www.scons.org.
configure can take several optional switches. Most important SCons is replacement for configure and make utility; there is no
switch is --disable-timeout. This option switches fsp clients separate configuration step. Building with SCons is very similar
into classic infinite retry mode which is preferred by people to using make. Run 'scons' to compile and 'scons install' to
with very flaky networks. install. You can skip compile part. 'scons install' will do both
steps then.
>> By default, the configure script will set up the Makefile SCons can take several optional switches. You must supply these
>> to install the code in /usr/local/bin and the man pages under switches to BOTH phases (compile and install) of build process.
>> /usr/local/man. If you wish to change this, you MUST run Most important switch is disable-timeout=yes. This option switches
>> configure with the --prefix option. For instance, on my fsp clients into classic infinite retry mode which is preferred
by people with very flaky networks.
>> By default, the SCons will install the code in /usr/local/bin
>> and the man pages under /usr/local/man. If you wish to change this,
>> you MUST run scons with the prefix option. For instance, on my
>> machine, I install the files under /usr/jt/bin and /usr/jt/man. >> machine, I install the files under /usr/jt/bin and /usr/jt/man.
>> To do this, I type configure --prefix=/usr/jt >> To do this, I type scons prefix=/usr/jt install
Compilation: Compilation:
At this point, you should just be able to type 'make' At this point, you should just be able to type 'make'