| README (253895) | README (262324) |
|---|---|
| 1Welcome to serf, a high-performance asynchronous HTTP client library. 2 3The serf library is a C-based HTTP client library built upon the Apache 4Portable Runtime (APR) library. It multiplexes connections, running the 5read/write communication asynchronously. Memory copies and transformations are 6kept to a minimum to provide high performance operation. 7 8 * Status: http://code.google.com/p/serf/wiki/ --- 4 unchanged lines hidden (view full) --- 13 * People: Justin Erenkrantz, Greg Stein 14 15---- 16 171. INSTALL 18 191.1. SCons build system 20 | 1Welcome to serf, a high-performance asynchronous HTTP client library. 2 3The serf library is a C-based HTTP client library built upon the Apache 4Portable Runtime (APR) library. It multiplexes connections, running the 5read/write communication asynchronously. Memory copies and transformations are 6kept to a minimum to provide high performance operation. 7 8 * Status: http://code.google.com/p/serf/wiki/ --- 4 unchanged lines hidden (view full) --- 13 * People: Justin Erenkrantz, Greg Stein 14 15---- 16 171. INSTALL 18 191.1. SCons build system 20 |
| 21serf uses SCons 2.x for its build system. If it is not installed on | 21serf uses SCons 2.3 for its build system. If it is not installed on |
| 22your system, then you can install it onto your system. If you do not 23have permissions, then you can download and install the "local" 24version into your home directory. When installed privately, simply 25create a symlink for 'scons' in your PATH to /path/to/scons/scons.py. 26 27Fetch the scons-local package: | 22your system, then you can install it onto your system. If you do not 23have permissions, then you can download and install the "local" 24version into your home directory. When installed privately, simply 25create a symlink for 'scons' in your PATH to /path/to/scons/scons.py. 26 27Fetch the scons-local package: |
| 28 http://prdownloads.sourceforge.net/scons/scons-local-2.0.1.tar.gz | 28 http://prdownloads.sourceforge.net/scons/scons-local-2.3.0.tar.gz |
| 29 30 311.2 Building serf 32 33To build serf: 34 35$ scons APR=/path/to/apr APU=/path/to/apu OPENSSL=/openssl/base PREFIX=/path/to/prefix 36 --- 12 unchanged lines hidden (view full) --- 49OPENSSL should specify the root of the install (eg. /opt/local). The 50includes will be found OPENSSL/include and libraries at OPENSSL/lib. 51 52If you wish to use VPATH-style builds (where objects are created in a 53distinct directory from the source), you can use: 54 55$ scons -Y /path/to/serf/source 56 | 29 30 311.2 Building serf 32 33To build serf: 34 35$ scons APR=/path/to/apr APU=/path/to/apu OPENSSL=/openssl/base PREFIX=/path/to/prefix 36 --- 12 unchanged lines hidden (view full) --- 49OPENSSL should specify the root of the install (eg. /opt/local). The 50includes will be found OPENSSL/include and libraries at OPENSSL/lib. 51 52If you wish to use VPATH-style builds (where objects are created in a 53distinct directory from the source), you can use: 54 55$ scons -Y /path/to/serf/source 56 |
| 57If you plan to install the library on a system that uses different 58paths for architecture dependent files, specify LIBDIR. LIBDIR defaults 59to /usr/local/lib otherwise. Example for a 64 bit GNU/Linux system: 60 61$ scons PREFIX=/usr/ LIBDIR=/usr/lib64 62 |
|
| 57At any point, the current settings can be examined: 58 59$ scons --help 60 61 621.3 Running the test suite 63 64$ scons check --- 4 unchanged lines hidden (view full) --- 69$ scons install 70 71Note that the PREFIX variable should have been specified in a previous 72invocation of scons (and saved into .saved_config), or it can be 73specified on the install command line: 74 75$ scons PREFIX=/some/path install 76 | 63At any point, the current settings can be examined: 64 65$ scons --help 66 67 681.3 Running the test suite 69 70$ scons check --- 4 unchanged lines hidden (view full) --- 75$ scons install 76 77Note that the PREFIX variable should have been specified in a previous 78invocation of scons (and saved into .saved_config), or it can be 79specified on the install command line: 80 81$ scons PREFIX=/some/path install 82 |
| 83Distribution package maintainers regulary install to a buildroot, and 84would normally use something like below in their build systems, with 85placeholders for the specific paths: |
|
| 77 | 86 |
| 87$ scons PREFIX=/usr/ LIBDIR=/usr/lib64 88$ scons install --install-sandbox=/path/to/buildroot 89 90 |
|
| 781.4 Cleaning up the build 79 80$ scons -c | 911.4 Cleaning up the build 92 93$ scons -c |