5 \___|\___/|_| \_\_____|
9 Installing Binary Packages
10 ==========================
12 Lots of people download binary distributions of curl and libcurl. This
13 document does not describe how to install curl or libcurl using such a
14 binary package. This document describes how to compile, build and install
15 curl and libcurl from source code.
19 A normal unix installation is made in three or four steps (after you've
20 unpacked the source archive):
27 You probably need to be root when doing the last command.
29 If you have checked out the sources from the CVS repository, read the
30 CVS-INFO on how to proceed.
32 Get a full listing of all available configure options by invoking it like:
36 If you want to install curl in a different file hierarchy than /usr/local,
37 you need to specify that already when running configure:
39 ./configure --prefix=/path/to/curl/tree
41 If you happen to have write permission in that directory, you can do 'make
42 install' without being root. An example of this would be to make a local
43 install in your own home directory:
45 ./configure --prefix=$HOME
49 The configure script always tries to find a working SSL library unless
50 explicitly told not to. If you have OpenSSL installed in the default search
51 path for your compiler/linker, you don't need to do anything special. If
52 you have OpenSSL installed in /usr/local/ssl, you can run configure like:
54 ./configure --with-ssl
56 If you have OpenSSL installed somewhere else (for example, /opt/OpenSSL)
57 and you have pkg-config installed, set the pkg-config path first, like this:
59 env PKG_CONFIG_PATH=/opt/OpenSSL/lib/pkgconfig ./configure --with-ssl
61 Without pkg-config installed, use this:
63 ./configure --with-ssl=/opt/OpenSSL
65 If you insist on forcing a build without SSL support, even though you may
66 have OpenSSL installed in your system, you can run configure like this:
68 ./configure --without-ssl
70 If you have OpenSSL installed, but with the libraries in one place and the
71 header files somewhere else, you have to set the LDFLAGS and CPPFLAGS
72 environment variables prior to running configure. Something like this
75 (with the Bourne shell and its clones):
77 CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \
80 (with csh, tcsh and their clones):
82 env CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \
85 If you have shared SSL libs installed in a directory where your run-time
86 linker doesn't find them (which usually causes configure failures), you can
87 provide the -R option to ld on some operating systems to set a hard-coded
88 path to the run-time linker:
90 env LDFLAGS=-R/usr/local/ssl/lib ./configure --with-ssl
95 To force configure to use the standard cc compiler if both cc and gcc are
96 present, run configure like
100 env CC=cc ./configure
102 To force a static library compile, disable the shared library creation
103 by running configure like:
105 ./configure --disable-shared
107 To tell the configure script to skip searching for thread-safe functions,
110 ./configure --disable-thread
112 To build curl with kerberos4 support enabled, curl requires the krb4 libs
113 and headers installed. You can then use a set of options to tell
114 configure where those are:
116 --with-krb4-includes[=DIR] Specify location of kerberos4 headers
117 --with-krb4-libs[=DIR] Specify location of kerberos4 libs
118 --with-krb4[=DIR] where to look for Kerberos4
120 In most cases, /usr/athena is the install prefix and then it works with
122 ./configure --with-krb4=/usr/athena
124 If you're a curl developer and use gcc, you might want to enable more
125 debug options with the --enable-debug option.
127 curl can be built to use a whole range of libraries to provide various
128 useful services, and configure will try to auto-detect a decent
129 default. But if you want to alter it, you can select how to deal with
130 each individual library.
132 To build with GnuTLS support instead of OpenSSL for SSL/TLS, note that
133 you need to use both --without-ssl and --with-gnutls.
135 To build with yassl support instead of OpenSSL or GnuTLS, you must build
136 yassl with its OpenSSL emulation enabled and point to that directory root
137 with configure --with-ssl.
139 To build with NSS support instead of OpenSSL for SSL/TLS, note that
140 you need to use both --without-ssl and --with-nss.
142 To get GSSAPI support, build with --with-gssapi and have the MIT or
143 Heimdal Kerberos 5 packages installed.
145 To get support for SCP and SFTP, build with --with-libssh2 and have
146 libssh2 0.16 or later installed.
150 Some versions of uClibc require configuring with CPPFLAGS=-D_GNU_SOURCE=1
151 to get correct large file support.
153 The Open Watcom C compiler on Linux requires configuring with the variables:
155 ./configure CC=owcc AR="$WATCOM/binl/wlib" AR_FLAGS=-q \
156 RANLIB=/bin/true STRIP="$WATCOM/binl/wstrip" CFLAGS=-Wextra
162 Building Windows DLLs and C run-time (CRT) linkage issues
163 ---------------------------------------------------------
165 As a general rule, building a DLL with static CRT linkage is highly
166 discouraged, and intermixing CRTs in the same app is something to
169 Reading and comprehension of Microsoft Knowledge Base articles
170 KB94248 and KB140584 is a must for any Windows developer. Especially
171 important is full understanding if you are not going to follow the
174 KB94248 - How To Use the C Run-Time
175 http://support.microsoft.com/kb/94248/en-us
177 KB140584 - How to link with the correct C Run-Time (CRT) library
178 http://support.microsoft.com/kb/140584/en-us
180 KB190799 - Potential Errors Passing CRT Objects Across DLL Boundaries
181 http://msdn.microsoft.com/en-us/library/ms235460
183 If your app is misbehaving in some strange way, or it is suffering
184 from memory corruption, before asking for further help, please try
185 first to rebuild every single library your app uses as well as your
186 app using the debug multithreaded dynamic C runtime.
191 Make sure that MinGW32's bin dir is in the search path, for example:
193 set PATH=c:\mingw32\bin;%PATH%
195 then run 'mingw32-make mingw32' in the root dir. There are other
196 make targets available to build libcurl with more features, use:
197 'mingw32-make mingw32-zlib' to build with Zlib support;
198 'mingw32-make mingw32-ssl-zlib' to build with SSL and Zlib enabled;
199 'mingw32-make mingw32-ssh2-ssl-zlib' to build with SSH2, SSL, Zlib;
200 'mingw32-make mingw32-ssh2-ssl-sspi-zlib' to build with SSH2, SSL, Zlib
203 If you have any problems linking libraries or finding header files, be sure
204 to verify that the provided "Makefile.m32" files use the proper paths, and
205 adjust as necessary. It is also possible to override these paths with
206 environment variables, for example:
208 set ZLIB_PATH=c:\zlib-1.2.3
209 set OPENSSL_PATH=c:\openssl-0.9.8g
210 set LIBSSH2_PATH=c:\libssh2-0.17
212 ATTENTION: if you want to build with libssh2 support you have to use latest
213 version 0.17 - previous versions will NOT work with 7.17.0 and later!
214 Use 'mingw32-make mingw32-ssh2-ssl-zlib' to build with SSH2 and SSL enabled.
216 It is now also possible to build with other LDAP SDKs than MS LDAP;
217 currently it is possible to build with native Win32 OpenLDAP, or with the
218 Novell CLDAP SDK. If you want to use these you need to set these vars:
220 set LDAP_SDK=c:\openldap
221 set USE_LDAP_OPENLDAP=1
223 or for using the Novell SDK:
225 set USE_LDAP_NOVELL=1
227 If you want to enable LDAPS support then set LDAPS=1.
229 - optional MingW32-built OpenlDAP SDK available from:
230 http://www.gknw.net/mirror/openldap/
231 - optional recent Novell CLDAP SDK available from:
232 http://developer.novell.com/ndk/cldap.htm
238 Almost identical to the unix installation. Run the configure script in the
239 curl root with 'sh configure'. Make sure you have the sh executable in
240 /bin/ or you'll see the configure fail toward the end.
247 See the separate INSTALL.devcpp file for details.
249 MSVC from command line
250 ----------------------
252 Run the 'vcvars32.bat' file to get a proper environment. The
253 vcvars32.bat file is part of the Microsoft development environment and
254 you may find it in 'C:\Program Files\Microsoft Visual Studio\vc98\bin'
255 provided that you installed Visual C/C++ 6 in the default directory.
257 Then run 'nmake vc' in curl's root directory.
259 If you want to compile with zlib support, you will need to build
260 zlib (http://www.gzip.org/zlib/) as well. Please read the zlib
261 documentation on how to compile zlib. Define the ZLIB_PATH environment
262 variable to the location of zlib.h and zlib.lib, for example:
264 set ZLIB_PATH=c:\zlib-1.2.3
266 Then run 'nmake vc-zlib' in curl's root directory.
268 If you want to compile with SSL support you need the OpenSSL package.
269 Please read the OpenSSL documentation on how to compile and install
270 the OpenSSL libraries. The build process of OpenSSL generates the
271 libeay32.dll and ssleay32.dll files in the out32dll subdirectory in
272 the OpenSSL home directory. OpenSSL static libraries (libeay32.lib,
273 ssleay32.lib, RSAglue.lib) are created in the out32 subdirectory.
275 Before running nmake define the OPENSSL_PATH environment variable with
276 the root/base directory of OpenSSL, for example:
278 set OPENSSL_PATH=c:\openssl-0.9.8g
280 Then run 'nmake vc-ssl' or 'nmake vc-ssl-dll' in curl's root
281 directory. 'nmake vc-ssl' will create a libcurl static and dynamic
282 libraries in the lib subdirectory, as well as a statically linked
283 version of curl.exe in the src subdirectory. This statically linked
284 version is a standalone executable not requiring any DLL at
285 runtime. This make method requires that you have the static OpenSSL
286 libraries available in OpenSSL's out32 subdirectory.
287 'nmake vc-ssl-dll' creates the libcurl dynamic library and
288 links curl.exe against libcurl and OpenSSL dynamically.
289 This executable requires libcurl.dll and the OpenSSL DLLs
291 Run 'nmake vc-ssl-zlib' to build with both ssl and zlib support.
296 A minimal VC++ 6.0 reference workspace (vc6curl.dsw) is available with the
297 source distribution archive to allow proper building of the two included
298 projects, the libcurl library and the curl tool.
300 1) Open the vc6curl.dsw workspace with MSVC6's IDE.
301 2) Select 'Build' from top menu.
302 3) Select 'Batch Build' from dropdown menu.
303 4) Make sure that the eight project configurations are 'checked'.
304 5) Click on the 'Build' button.
305 6) Once the eight project configurations are built you are done.
307 Dynamic and static libcurl libraries are built in debug and release flavours,
308 and can be located each one in its own subdirectory, DLL-Debug, DLL-Release,
309 LIB-Debug and LIB-Release, all of them below the 'lib' subdirectory.
311 In the same way four curl executables are created, each using its respective
312 library. The resulting curl executables are located in its own subdirectory,
313 DLL-Debug, DLL-Release, LIB-Debug and LIB-Release, below the 'src' subdir.
315 These reference VC++ 6.0 configurations are generated using the dynamic CRT.
317 Intentionally, these reference VC++ 6.0 projects and configurations don't use
318 third party libraries, such as OpenSSL or Zlib, to allow proper compilation
319 and configuration for all new users without further requirements.
321 If you need something more 'involved' you might adjust them for your own use,
322 or explore the world of makefiles described above 'MSVC from command line'.
325 ---------------------
329 Make sure you include the paths to curl/include and openssl/inc32 in
332 eg : -I"c:\Bcc55\include;c:\path_curl\include;c:\path_openssl\inc32"
334 Check to make sure that all of the sources listed in lib/Makefile.b32
335 are present in the /path_to_curl/lib directory. (Check the src
336 directory for missing ones.)
338 Make sure the environment variable "BCCDIR" is set to the install
339 location for the compiler eg : c:\Borland\BCC55
342 make -f /path_to_curl/lib/Makefile-ssl.b32
344 compile simplessl.c with appropriate links
346 c:\curl\docs\examples\> bcc32 -L c:\path_to_curl\lib\libcurl.lib
347 -L c:\borland\bcc55\lib\psdk\ws2_32.lib
348 -L c:\openssl\out32\libeay32.lib
349 -L c:\openssl\out32\ssleay32.lib
355 If you use VC++, Borland or similar compilers. Include all lib source
356 files in a static lib "project" (all .c and .h files that is).
357 (you should name it libcurl or similar)
359 Make the sources in the src/ drawer be a "win32 console application"
360 project. Name it curl.
363 Disabling Specific Protocols in Win32 builds
364 --------------------------------------------
366 The configure utility, unfortunately, is not available for the Windows
367 environment, therefore, you cannot use the various disable-protocol
368 options of the configure utility on this platform.
370 However, you can use the following defines to disable specific
373 HTTP_ONLY disables all protocols except HTTP
374 CURL_DISABLE_FTP disables FTP
375 CURL_DISABLE_LDAP disables LDAP
376 CURL_DISABLE_TELNET disables TELNET
377 CURL_DISABLE_DICT disables DICT
378 CURL_DISABLE_FILE disables FILE
379 CURL_DISABLE_TFTP disables TFTP
380 CURL_DISABLE_HTTP disables HTTP
382 If you want to set any of these defines you have the following
385 - Modify lib/config-win32.h
387 - Modify lib/Makefile.vc6
388 - Add defines to Project/Settings/C/C++/General/Preprocessor Definitions
389 in the vc6libcurl.dsw/vc6libcurl.dsp Visual C++ 6 IDE project.
392 Important static libcurl usage note
393 -----------------------------------
395 When building an application that uses the static libcurl library, you must
396 add '-DCURL_STATICLIB' to your CFLAGS. Otherwise the linker will look for
397 dynamic import symbols.
402 Building under OS/2 is not much different from building under unix.
414 If you want to build with OpenSSL or OpenLDAP support, you'll need to
415 download those libraries, too. Dirk Ohme has done some work to port SSL
416 libraries under OS/2, but it looks like he doesn't care about emx. You'll
417 find his patches on: http://come.to/Dirk_Ohme
419 If during the linking you get an error about _errno being an undefined
420 symbol referenced from the text segment, you need to add -D__ST_MT_ERRNO__
423 If everything seems to work fine but there's no curl.exe, you need to add
424 -Zexe to your linker flags.
426 If you're getting huge binaries, probably your makefiles have the -g in
432 (The VMS section is in whole contributed by the friendly Nico Baggus)
434 Curl seems to work with FTP & HTTP other protocols are not tested. (the
435 perl http/ftp testing server supplied as testing too cannot work on VMS
436 because vms has no concept of fork(). [ I tried to give it a whack, but
439 SSL stuff has not been ported.
441 Telnet has about the same issues as for Win32. When the changes for Win32
442 are clear maybe they'll work for VMS too. The basic problem is that select
443 ONLY works for sockets.
445 Marked instances of fopen/[f]stat that might become a problem, especially
446 for non stream files. In this regard, the files opened for writing will be
447 created stream/lf and will thus be safe. Just keep in mind that non-binary
448 read/wring from/to files will have a records size limit of 32767 bytes
451 Stat to get the size of the files is again only safe for stream files &
452 fixed record files without implied CC.
454 -- My guess is that only allowing access to stream files is the quickest
455 way to get around the most issues. Therefore all files need to to be
456 checked to be sure they will be stream/lf before processing them. This is
457 the easiest way out, I know. The reason for this is that code that needs to
458 report the filesize will become a pain in the ass otherwise.
460 Exit status.... Well we needed something done here,
462 VMS has a structured exist status:
464 |1098|765432109876|5432109876543|210|
465 +----+------------+-------------+---+
466 |Ctrl| Facility | Error code |sev|
467 +----+------------+-------------+---+
469 With the Ctrl-bits an application can tell if part or the whole message has
470 already been printed from the program, DCL doesn't need to print it again.
472 Facility - basically the program ID. A code assigned to the program
473 the name can be fetched from external or internal message libraries
474 Error code - the err codes assigned by the application
475 Sev. - severity: Even = error, off = non error
483 This all presents itself with:
484 %<FACILITY>-<Sev>-<Errorname>, <Error message>
486 See also the src/curlmsg.msg file, it has the source for the messages In
487 src/main.c a section is devoted to message status values, the globalvalues
488 create symbols with certain values, referenced from a compiled message
489 file. Have all exit function use a exit status derived from a translation
490 table with the compiled message codes.
492 This was all compiled with:
494 Compaq C V6.2-003 on OpenVMS Alpha V7.1-1H2
496 So far for porting notes as of:
503 (This section was graciously brought to us by David Bentham)
505 As QNX is targeted for resource constrained environments, the QNX headers
506 set conservative limits. This includes the FD_SETSIZE macro, set by default
507 to 32. Socket descriptors returned within the CURL library may exceed this,
508 resulting in memory faults/SIGSEGV crashes when passed into select(..)
509 calls using fd_set macros.
511 A good all-round solution to this is to override the default when building
512 libcurl, by overriding CFLAGS during configure, example
513 # configure CFLAGS='-DFD_SETSIZE=64 -g -O2'
518 The library can be cross-compiled using gccsdk as follows:
520 CC=riscos-gcc AR=riscos-ar RANLIB='riscos-ar -s' ./configure \
521 --host=arm-riscos-aof --without-random --disable-shared
524 where riscos-gcc and riscos-ar are links to the gccsdk tools.
525 You can then link your program with curl/lib/.libs/libcurl.a
530 (This section was graciously brought to us by Diego Casorran)
532 To build cURL/libcurl on AmigaOS just type 'make amiga' ...
534 What you need is: (not tested with others versions)
536 GeekGadgets / gcc 2.95.3 (http://www.geekgadgets.org/)
538 AmiTCP SDK v4.3 (http://www.aminet.net/comm/tcp/AmiTCP-SDK-4.3.lha)
540 Native Developer Kit (http://www.amiga.com/3.9/download/NDK3.9.lha)
542 As no ixemul.library is required you will be able to build it for
543 WarpOS/PowerPC (not tested by me), as well a MorphOS version should be
544 possible with no problems.
546 To enable SSL support, you need a OpenSSL native version (without ixemul),
547 you can find a precompiled package at http://amiga.sourceforge.net/OpenSSL/
552 To compile curl.nlm / libcurl.nlm you need:
553 - either any gcc / nlmconv, or CodeWarrior 7 PDK 4 or later.
554 - gnu make and awk running on the platform you compile on;
555 native Win32 versions can be downloaded from:
556 http://www.gknw.net/development/prgtools/
557 - recent Novell LibC SDK available from:
558 http://developer.novell.com/ndk/libc.htm
559 - or recent Novell CLib SDK available from:
560 http://developer.novell.com/ndk/clib.htm
561 - optional recent Novell CLDAP SDK available from:
562 http://developer.novell.com/ndk/cldap.htm
563 - optional zlib sources (static or dynamic linking with zlib.imp);
564 sources with NetWare Makefile can be obtained from:
565 http://www.gknw.net/mirror/zlib/
566 - optional OpenSSL sources (version 0.9.8 or later build with BSD sockets);
567 you can find precompiled packages at:
568 http://www.gknw.net/development/ossl/netware/
569 for CLIB-based builds OpenSSL needs to be patched to build with BSD
570 sockets (currently only a winsock-based CLIB build is supported):
571 http://www.gknw.net/development/ossl/netware/patches/v_0.9.8g/openssl-0.9.8g.diff
572 - optional SSH2 sources (version 0.17 or later);
574 Set a search path to your compiler, linker and tools; on Linux make
575 sure that the var OSTYPE contains the string 'linux'; set the var
576 NDKBASE to point to the base of your Novell NDK; and then type
577 'make netware' from the top source directory; other targets available
578 are 'netware-ssl', 'netware-ssl-zlib', 'netware-zlib' and 'netware-ares';
579 if you need other combinations you can control the build with the
580 environment variables WITH_SSL, WITH_ZLIB, WITH_ARES, WITH_SSH2, and
581 ENABLE_IPV6; you can set LINK_STATIC=1 to link curl.nlm statically.
582 By default LDAP support is enabled, however currently you will need a patch
583 in order to use the CLDAP NDK with BSD sockets (Novell Bug 300237):
584 http://www.gknw.net/test/curl/cldap_ndk/ldap_ndk.diff
585 I found on some Linux systems (RH9) that OS detection didn't work although
586 a 'set | grep OSTYPE' shows the var present and set; I simply overwrote it
587 with 'OSTYPE=linux-rh9-gnu' and the detection in the Makefile worked...
588 Any help in testing appreciated!
589 Builds automatically created 8 times a day from current CVS are here:
590 http://www.gknw.net/mirror/curl/autobuilds/
591 the status of these builds can be viewed at the autobuild table:
592 http://curl.haxx.se/auto/
597 curl does not use the eCos build system, so you must first build eCos
598 separately, then link curl to the resulting eCos library. Here's a sample
599 configure line to do so on an x86 Linux box targeting x86:
601 GCCLIB=`gcc -print-libgcc-file-name` && \
602 CFLAGS="-D__ECOS=1 -nostdinc -I$ECOS_INSTALL/include \
603 -I`dirname $GCCLIB`/include" \
604 LDFLAGS="-nostdlib -Wl,--gc-sections -Wl,-static \
605 -L$ECOS_INSTALL/lib -Ttarget.ld -ltarget" \
606 ./configure --host=i386 --disable-shared \
607 --without-ssl --without-zlib --disable-manual --disable-ldap
609 In most cases, eCos users will be using libcurl from within a custom
610 embedded application. Using the standard 'curl' executable from
611 within eCos means facing the limitation of the standard eCos C
612 startup code which does not allow passing arguments in main(). To
613 run 'curl' from eCos and have it do something useful, you will need
614 to either modify the eCos startup code to pass in some arguments, or
615 modify the curl application itself to retrieve its arguments from
616 some location set by the bootloader or hard-code them.
618 Something like the following patch could be used to hard-code some
619 arguments. The MTAB_ENTRY line mounts a RAM disk as the root filesystem
620 (without mounting some kind of filesystem, eCos errors out all file
621 operations which curl does not take to well). The next section synthesizes
622 some command-line arguments for curl to use, in this case to direct curl
623 to read further arguments from a file. It then creates that file on the
624 RAM disk and places within it a URL to download: a file: URL that
625 just happens to point to the configuration file itself. The results
626 of running curl in this way is the contents of the configuration file
627 printed to the console.
629 --- src/main.c 19 Jul 2006 19:09:56 -0000 1.363
630 +++ src/main.c 24 Jul 2006 21:37:23 -0000
631 @@ -4286,11 +4286,31 @@
636 +#include <cyg/fileio/fileio.h>
637 +MTAB_ENTRY( testfs_mte1,
644 int main(int argc, char *argv[])
647 struct Configurable config;
649 + char *args[] = {"ecos-curl", "-K", "curlconf.txt"};
651 + argc = sizeof(args)/sizeof(args[0]);
654 + f = fopen("curlconf.txt", "w");
656 + fprintf(f, "--url file:curlconf.txt");
660 memset(&config, 0, sizeof(struct Configurable));
662 config.errors = stderr; /* default errors to stderr */
667 curl can be compiled on Minix 3 using gcc or ACK (starting with
672 Increase the heap sizes of the compiler with the command:
676 Configure and compile with:
678 ./configure CONFIG_SHELL=/bin/bigsh CC=cc LD=cc AR=/usr/bin/aal \
679 GREP=grep CPPFLAGS='-D_POSIX_SOURCE=1 -I/usr/local/include'
681 chmem =256000 src/curl
685 Make sure gcc is in your PATH with the command:
687 export PATH=/usr/gnu/bin:$PATH
689 then configure and compile curl with:
691 ./configure CONFIG_SHELL=/bin/bigsh CC=gcc AR=/usr/gnu/bin/gar GREP=grep
693 chmem =256000 src/curl
698 The Symbian OS port uses the Symbian build system to compile. From the
699 packages/Symbian/group/ directory, run:
704 to compile and install curl and libcurl. If your Symbian SDK doesn't
705 include support for P.I.P.S., you will need to contact your SDK vendor
706 to obtain that first.
711 (This section was graciously brought to us by Jim Duey, with additions by
714 Download and unpack the cURL package.
716 'cd' to the new directory. (e.g. cd curl-7.12.3)
718 Set environment variables to point to the cross-compile toolchain and call
719 configure with any options you need. Be sure and specify the '--host' and
720 '--build' parameters at configuration time. The following script is an
721 example of cross-compiling for the IBM 405GP PowerPC processor using the
722 toolchain from MonteVista for Hardhat Linux.
728 export PATH=$PATH:/opt/hardhat/devkit/ppc/405/bin
729 export CPPFLAGS="-I/opt/hardhat/devkit/ppc/405/target/usr/include"
733 export RANLIB=ppc_405-ranlib
734 export CC=ppc_405-gcc
737 ./configure --target=powerpc-hardhat-linux \
738 --host=powerpc-hardhat-linux \
739 --build=i586-pc-linux-gnu \
740 --prefix=/opt/hardhat/devkit/ppc/405/target/usr/local \
741 --exec-prefix=/usr/local
745 You may also need to provide a parameter like '--with-random=/dev/urandom'
746 to configure as it cannot detect the presence of a random number
747 generating device for a target system. The '--prefix' parameter
748 specifies where cURL will be installed. If 'configure' completes
749 successfully, do 'make' and 'make install' as usual.
751 In some cases, you may be able to simplify the above commands to as
754 ./configure --host=ARCH-OS
759 There are a number of configure options that can be used to reduce the
760 size of libcurl for embedded applications where binary size is an
761 important factor. First, be sure to set the CFLAGS variable when
762 configuring with any relevant compiler optimization flags to reduce the
763 size of the binary. For gcc, this would mean at minimum the -Os option,
764 and potentially the -march=X and -mdynamic-no-pic options as well, e.g.
766 ./configure CFLAGS='-Os' ...
768 Note that newer compilers often produce smaller code than older versions
769 due to improved optimization.
771 Be sure to specify as many --disable- and --without- flags on the configure
772 command-line as you can to disable all the libcurl features that you
773 know your application is not going to need. Besides specifying the
774 --disable-PROTOCOL flags for all the types of URLs your application
775 will not use, here are some other flags that can reduce the size of the
778 --disable-ares (disables support for the C-ARES DNS library)
779 --disable-cookies (disables support for HTTP cookies)
780 --disable-crypto-auth (disables HTTP cryptographic authentication)
781 --disable-ipv6 (disables support for IPv6)
782 --disable-manual (disables support for the built-in documentation)
783 --disable-proxy (disables support for HTTP and SOCKS proxies)
784 --disable-verbose (eliminates debugging strings and error code strings)
785 --enable-hidden-symbols (eliminates unneeded symbols in the shared library)
786 --without-libidn (disables support for the libidn DNS library)
787 --without-ssl (disables support for SSL/TLS)
788 --without-zlib (disables support for on-the-fly decompression)
790 The GNU compiler and linker have a number of options that can reduce the
791 size of the libcurl dynamic libraries on some platforms even further.
792 Specify them by providing appropriate CFLAGS and LDFLAGS variables on the
793 configure command-line:
794 CFLAGS="-ffunction-sections -fdata-sections" \
795 LDFLAGS="-Wl,-s -Wl,-Bsymbolic -Wl,--gc-sections"
797 Be sure also to strip debugging symbols from your binaries after
798 compiling using 'strip' (or the appropriate variant if cross-compiling).
799 If space is really tight, you may be able to remove some unneeded
800 sections of the shared library using the -R option to objcopy (e.g. the
803 Using these techniques it is possible to create a basic HTTP-only shared
804 libcurl library for i386 Linux platforms that is only 94 KiB in size, and
805 an FTP-only library that is 87 KiB in size (as of libcurl version 7.19.1,
808 You may find that statically linking libcurl to your application will
809 result in a lower total size than dynamically linking.
811 Note that the curl test harness can detect the use of some, but not all, of
812 the --disable statements suggested above. Use will cause tests relying on
813 those features to fail. The test harness can be manually forced to skip
814 the relevant tests by specifying certain key words on the runtests.pl
815 command line. Following is a list of appropriate key words:
817 --disable-cookies !cookies
818 --disable-crypto-auth !HTTP\ Digest\ auth !HTTP\ proxy\ Digest\ auth
819 --disable-manual !--manual
820 --disable-proxy !HTTP\ proxy !proxytunnel !SOCKS4 !SOCKS5
825 This is a probably incomplete list of known hardware and operating systems
826 that curl has been compiled for. If you know a system curl compiles and
827 runs on, that isn't listed, please let us know!
830 - Alpha Digital UNIX v3.2
831 - Alpha FreeBSD 4.1, 4.5
832 - Alpha Linux 2.2, 2.4
835 - Alpha OpenVMS V7.1-1H2
836 - Alpha Tru64 v5.0 5.1
842 - HP-PA HP-UX 9.X 10.X 11.X
849 - Pocket PC/Win CE 3.0
850 - Power AIX 3.2.5, 4.2, 4.3.1, 4.3.2, 5.1, 5.2
860 - Sparc Solaris 2.4, 2.5, 2.5.1, 2.6, 7, 8, 9, 10
862 - StrongARM (and other ARM) RISC OS 3.1, 4.02
863 - StrongARM/ARM7/ARM9 Linux 2.4, 2.6
864 - StrongARM NetBSD 1.4.1
865 - Symbian OS (P.I.P.S.) 9.x
876 - i386 Linux 1.3, 2.0, 2.2, 2.3, 2.4, 2.6
879 - i386 Novell NetWare
885 - i386 Windows 95, 98, ME, NT, 2000, XP, 2003
886 - i486 ncr-sysv4.3.03 (NCR MP-RAS)
892 - m88k dg-dgux5.4R3.00
895 - XScale/PXA250 Linux 2.4
901 OpenSSL http://www.openssl.org
902 MingW http://www.mingw.org
903 OpenLDAP http://www.openldap.org
904 Zlib http://www.gzip.org/zlib/
905 libssh2 http://www.libssh2.org