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.
20 If you get your code off a git repository, see the GIT-INFO file in the
21 root directory for specific instructions on how to proceed.
25 A normal unix installation is made in three or four steps (after you've
26 unpacked the source archive):
33 You probably need to be root when doing the last command.
35 If you have checked out the sources from the git repository, read the
36 GIT-INFO on how to proceed.
38 Get a full listing of all available configure options by invoking it like:
42 If you want to install curl in a different file hierarchy than /usr/local,
43 you need to specify that already when running configure:
45 ./configure --prefix=/path/to/curl/tree
47 If you happen to have write permission in that directory, you can do 'make
48 install' without being root. An example of this would be to make a local
49 install in your own home directory:
51 ./configure --prefix=$HOME
55 The configure script always tries to find a working SSL library unless
56 explicitly told not to. If you have OpenSSL installed in the default search
57 path for your compiler/linker, you don't need to do anything special. If
58 you have OpenSSL installed in /usr/local/ssl, you can run configure like:
60 ./configure --with-ssl
62 If you have OpenSSL installed somewhere else (for example, /opt/OpenSSL)
63 and you have pkg-config installed, set the pkg-config path first, like this:
65 env PKG_CONFIG_PATH=/opt/OpenSSL/lib/pkgconfig ./configure --with-ssl
67 Without pkg-config installed, use this:
69 ./configure --with-ssl=/opt/OpenSSL
71 If you insist on forcing a build without SSL support, even though you may
72 have OpenSSL installed in your system, you can run configure like this:
74 ./configure --without-ssl
76 If you have OpenSSL installed, but with the libraries in one place and the
77 header files somewhere else, you have to set the LDFLAGS and CPPFLAGS
78 environment variables prior to running configure. Something like this
81 (with the Bourne shell and its clones):
83 CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \
86 (with csh, tcsh and their clones):
88 env CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \
91 If you have shared SSL libs installed in a directory where your run-time
92 linker doesn't find them (which usually causes configure failures), you can
93 provide the -R option to ld on some operating systems to set a hard-coded
94 path to the run-time linker:
96 env LDFLAGS=-R/usr/local/ssl/lib ./configure --with-ssl
101 To force configure to use the standard cc compiler if both cc and gcc are
102 present, run configure like
106 env CC=cc ./configure
108 To force a static library compile, disable the shared library creation
109 by running configure like:
111 ./configure --disable-shared
113 To tell the configure script to skip searching for thread-safe functions,
116 ./configure --disable-thread
118 If you're a curl developer and use gcc, you might want to enable more
119 debug options with the --enable-debug option.
121 curl can be built to use a whole range of libraries to provide various
122 useful services, and configure will try to auto-detect a decent
123 default. But if you want to alter it, you can select how to deal with
124 each individual library.
126 To build with GnuTLS for SSL/TLS, use both --without-ssl and
129 To build with Cyassl for SSL/TLS, use both --without-ssl and
132 To build with NSS for SSL/TLS, use both --without-ssl and --with-nss.
134 To build with PolarSSL for SSL/TLS, use both --without-ssl and
137 To build with axTLS for SSL/TLS, use both --without-ssl and --with-axtls.
139 To get GSSAPI support, build with --with-gssapi and have the MIT or
140 Heimdal Kerberos 5 packages installed.
142 To get support for SCP and SFTP, build with --with-libssh2 and have
143 libssh2 0.16 or later installed.
145 To get Metalink support, build with --with-libmetalink and have the
146 libmetalink packages 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.
188 If you get linkage errors read section 5.7 of the FAQ document.
194 Make sure that MinGW32's bin dir is in the search path, for example:
196 set PATH=c:\mingw32\bin;%PATH%
198 then run 'mingw32-make mingw32' in the root dir. There are other
199 make targets available to build libcurl with more features, use:
200 'mingw32-make mingw32-zlib' to build with Zlib support;
201 'mingw32-make mingw32-ssl-zlib' to build with SSL and Zlib enabled;
202 'mingw32-make mingw32-ssh2-ssl-zlib' to build with SSH2, SSL, Zlib;
203 'mingw32-make mingw32-ssh2-ssl-sspi-zlib' to build with SSH2, SSL, Zlib
206 If you have any problems linking libraries or finding header files, be sure
207 to verify that the provided "Makefile.m32" files use the proper paths, and
208 adjust as necessary. It is also possible to override these paths with
209 environment variables, for example:
211 set ZLIB_PATH=c:\zlib-1.2.8
212 set OPENSSL_PATH=c:\openssl-0.9.8y
213 set LIBSSH2_PATH=c:\libssh2-1.4.3
215 ATTENTION: if you want to build with libssh2 support you have to use latest
216 version 0.17 - previous versions will NOT work with 7.17.0 and later!
217 Use 'mingw32-make mingw32-ssh2-ssl-zlib' to build with SSH2 and SSL enabled.
219 It is now also possible to build with other LDAP SDKs than MS LDAP;
220 currently it is possible to build with native Win32 OpenLDAP, or with the
221 Novell CLDAP SDK. If you want to use these you need to set these vars:
223 set LDAP_SDK=c:\openldap
224 set USE_LDAP_OPENLDAP=1
226 or for using the Novell SDK:
228 set USE_LDAP_NOVELL=1
230 If you want to enable LDAPS support then set LDAPS=1.
232 - optional MingW32-built OpenLDAP SDK available from:
233 http://www.gknw.net/mirror/openldap/
234 - optional recent Novell CLDAP SDK available from:
235 http://developer.novell.com/ndk/cldap.htm
241 Almost identical to the unix installation. Run the configure script in the
242 curl root with 'sh configure'. Make sure you have the sh executable in
243 /bin/ or you'll see the configure fail toward the end.
250 See the separate INSTALL.devcpp file for details.
255 If you use MSVC 6 it is required that you use the February 2003 edition of
256 the 'Platform SDK' which can be downloaded from:
258 http://www.microsoft.com/en-us/download/details.aspx?id=12261
260 Building any software with MSVC 6 without having PSDK installed is just
261 asking for trouble down the road once you have released it, you might notice
262 the problems in the first corner or ten miles ahead, depending mostly on your
263 choice of static vs dynamic runtime and third party libraries. Anyone using
264 software built in such way will at some point regret having done so.
266 If the compiler has been updated with the installation of a service pack as
267 those mentioned in http://support.microsoft.com/kb/194022 the compiler can be
268 safely used to read source code, translate and make it object code.
270 But, even with the service packs mentioned above installed, the resulting
271 software generated in such an environment will be using outdated system
272 header files and libraries with bugs and security issues which have already
273 been addressed and fixed long time ago.
275 So, building curl and libcurl with MSVC 6 without PSDK is absolutely
276 discouraged for the benefit of anyone using software built in such
277 environment. And it will not be supported in any way, as we could just
278 be hunting bugs which have already been fixed way back in 2003.
280 When building with MSVC 6 we attempt to detect if PSDK is not being used,
281 and if this is the case the build process will fail hard with an error
282 message stating that the February 2003 PSDK is required. This is done to
283 protect the unsuspecting and avoid PEBKAC issues.
285 Additionally it might happen that a die hard MSVC hacker still wants to
286 build curl and libcurl with MSVC 6 without PSDK installed, even knowing
287 that this is a highly discouraged and unsupported build environment. In
288 this case the brave of heart will be able to build in such an environment
289 with the requisite of defining preprocessor symbol ALLOW_MSVC6_WITHOUT_PSDK
290 in lib/config-win32.h and knowing that LDAP and IPv6 support will be missing.
292 MSVC from command line
293 ----------------------
295 Run the 'vcvars32.bat' file to get a proper environment. The
296 vcvars32.bat file is part of the Microsoft development environment and
297 you may find it in 'C:\Program Files\Microsoft Visual Studio\vc98\bin'
298 provided that you installed Visual C/C++ 6 in the default directory.
300 Then run 'nmake vc' in curl's root directory.
302 If you want to compile with zlib support, you will need to build
303 zlib (http://www.gzip.org/zlib/) as well. Please read the zlib
304 documentation on how to compile zlib. Define the ZLIB_PATH environment
305 variable to the location of zlib.h and zlib.lib, for example:
307 set ZLIB_PATH=c:\zlib-1.2.8
309 Then run 'nmake vc-zlib' in curl's root directory.
311 If you want to compile with SSL support you need the OpenSSL package.
312 Please read the OpenSSL documentation on how to compile and install
313 the OpenSSL libraries. The build process of OpenSSL generates the
314 libeay32.dll and ssleay32.dll files in the out32dll subdirectory in
315 the OpenSSL home directory. OpenSSL static libraries (libeay32.lib,
316 ssleay32.lib, RSAglue.lib) are created in the out32 subdirectory.
318 Before running nmake define the OPENSSL_PATH environment variable with
319 the root/base directory of OpenSSL, for example:
321 set OPENSSL_PATH=c:\openssl-0.9.8y
323 Then run 'nmake vc-ssl' or 'nmake vc-ssl-dll' in curl's root
324 directory. 'nmake vc-ssl' will create a libcurl static and dynamic
325 libraries in the lib subdirectory, as well as a statically linked
326 version of curl.exe in the src subdirectory. This statically linked
327 version is a standalone executable not requiring any DLL at
328 runtime. This make method requires that you have the static OpenSSL
329 libraries available in OpenSSL's out32 subdirectory.
330 'nmake vc-ssl-dll' creates the libcurl dynamic library and
331 links curl.exe against libcurl and OpenSSL dynamically.
332 This executable requires libcurl.dll and the OpenSSL DLLs
334 Run 'nmake vc-ssl-zlib' to build with both ssl and zlib support.
339 A fairly comprehensive set of Visual Studio project files are available for
340 v6.0 through v12.0 and are located in the projects folder to allow proper
341 building of both the libcurl library as well as the curl tool.
343 For more information about these projects and building via Visual Studio
344 please see the README file located in the projects folder.
349 Ensure that your build environment is properly set up to use the compiler
350 and associated tools. PATH environment variable must include the path to
351 bin subdirectory of your compiler installation, eg: c:\Borland\BCC55\bin
353 It is advisable to set environment variable BCCDIR to the base path of
354 the compiler installation.
356 set BCCDIR=c:\Borland\BCC55
358 In order to build a plain vanilla version of curl and libcurl run the
359 following command from curl's root directory:
363 To build curl and libcurl with zlib and OpenSSL support set environment
364 variables ZLIB_PATH and OPENSSL_PATH to the base subdirectories of the
365 already built zlib and OpenSSL libraries and from curl's root directory
368 make borland-ssl-zlib
370 libcurl library will be built in 'lib' subdirectory while curl tool
371 is built in 'src' subdirectory. In order to use libcurl library it is
372 advisable to modify compiler's configuration file bcc32.cfg located
373 in c:\Borland\BCC55\bin to reflect the location of libraries include
374 paths for example the '-I' line could result in something like:
376 -I"c:\Borland\BCC55\include;c:\curl\include;c:\openssl\inc32"
378 bcc3.cfg '-L' line could also be modified to reflect the location of
379 of libcurl library resulting for example:
381 -L"c:\Borland\BCC55\lib;c:\curl\lib;c:\openssl\out32"
383 In order to build sample program 'simple.c' from the docs\examples
384 subdirectory run following command from mentioned subdirectory:
386 bcc32 simple.c libcurl.lib cw32mt.lib
388 In order to build sample program simplessl.c an SSL enabled libcurl
389 is required, as well as the OpenSSL libeay32.lib and ssleay32.lib
396 If you use VC++, Borland or similar compilers. Include all lib source
397 files in a static lib "project" (all .c and .h files that is).
398 (you should name it libcurl or similar)
400 Make the sources in the src/ drawer be a "win32 console application"
401 project. Name it curl.
404 Disabling Specific Protocols in Win32 builds
405 --------------------------------------------
407 The configure utility, unfortunately, is not available for the Windows
408 environment, therefore, you cannot use the various disable-protocol
409 options of the configure utility on this platform.
411 However, you can use the following defines to disable specific
414 HTTP_ONLY disables all protocols except HTTP
415 CURL_DISABLE_FTP disables FTP
416 CURL_DISABLE_LDAP disables LDAP
417 CURL_DISABLE_TELNET disables TELNET
418 CURL_DISABLE_DICT disables DICT
419 CURL_DISABLE_FILE disables FILE
420 CURL_DISABLE_TFTP disables TFTP
421 CURL_DISABLE_HTTP disables HTTP
423 If you want to set any of these defines you have the following
426 - Modify lib/config-win32.h
427 - Modify lib/curl_setup.h
428 - Modify lib/Makefile.vc6
429 - Add defines to Project/Settings/C/C++/General/Preprocessor Definitions
430 in the vc6libcurl.dsw/vc6libcurl.dsp Visual C++ 6 IDE project.
433 Using BSD-style lwIP instead of Winsock TCP/IP stack in Win32 builds
434 --------------------------------------------------------------------
436 In order to compile libcurl and curl using BSD-style lwIP TCP/IP stack
437 it is necessary to make definition of preprocessor symbol USE_LWIPSOCK
438 visible to libcurl and curl compilation processes. To set this definition
439 you have the following alternatives:
441 - Modify lib/config-win32.h and src/config-win32.h
442 - Modify lib/Makefile.vc6
443 - Add definition to Project/Settings/C/C++/General/Preprocessor Definitions
444 in the vc6libcurl.dsw/vc6libcurl.dsp Visual C++ 6 IDE project.
446 Once that libcurl has been built with BSD-style lwIP TCP/IP stack support,
447 in order to use it with your program it is mandatory that your program
448 includes lwIP header file <lwip/opt.h> (or another lwIP header that includes
449 this) before including any libcurl header. Your program does not need the
450 USE_LWIPSOCK preprocessor definition which is for libcurl internals only.
452 Compilation has been verified with lwIP 1.4.0 and contrib-1.4.0 from:
454 http://download.savannah.gnu.org/releases/lwip/lwip-1.4.0.zip
455 http://download.savannah.gnu.org/releases/lwip/contrib-1.4.0.zip
457 This BSD-style lwIP TCP/IP stack support must be considered experimental
458 given that it has been verified that lwIP 1.4.0 still needs some polish,
459 and libcurl might yet need some additional adjustment, caveat emptor.
461 Important static libcurl usage note
462 -----------------------------------
464 When building an application that uses the static libcurl library, you must
465 add '-DCURL_STATICLIB' to your CFLAGS. Otherwise the linker will look for
466 dynamic import symbols.
469 Apple iOS and Mac OS X
470 ======================
471 On recent Apple operating systems, curl can be built to use Apple's
472 SSL/TLS implementation, Secure Transport, instead of OpenSSL. To build with
473 Secure Transport for SSL/TLS, use the configure option --with-darwinssl. (It
474 is not necessary to use the option --without-ssl.) This feature requires iOS
475 5.0 or later, or OS X 10.5 ("Leopard") or later.
477 When Secure Transport is in use, the curl options --cacert and --capath and
478 their libcurl equivalents, will be ignored, because Secure Transport uses
479 the certificates stored in the Keychain to evaluate whether or not to trust
480 the server. This, of course, includes the root certificates that ship with
481 the OS. The --cert and --engine options, and their libcurl equivalents, are
482 currently unimplemented in curl with Secure Transport.
484 For OS X users: In OS X 10.8 ("Mountain Lion"), Apple made a major
485 overhaul to the Secure Transport API that, among other things, added
486 support for the newer TLS 1.1 and 1.2 protocols. To get curl to support
487 TLS 1.1 and 1.2, you must build curl on Mountain Lion or later, or by
488 using the equivalent SDK. If you set the MACOSX_DEPLOYMENT_TARGET
489 environmental variable to an earlier version of OS X prior to building curl,
490 then curl will use the new Secure Transport API on Mountain Lion and later,
491 and fall back on the older API when the same curl binary is executed on
492 older cats. For example, running these commands in curl's directory in the
493 shell will build the code such that it will run on cats as old as OS X 10.6
494 ("Snow Leopard") (using bash):
496 export MACOSX_DEPLOYMENT_TARGET="10.6"
497 ./configure --with-darwinssl
503 Building under OS/2 is not much different from building under unix.
515 If you want to build with OpenSSL or OpenLDAP support, you'll need to
516 download those libraries, too. Dirk Ohme has done some work to port SSL
517 libraries under OS/2, but it looks like he doesn't care about emx. You'll
518 find his patches on: http://come.to/Dirk_Ohme
520 If during the linking you get an error about _errno being an undefined
521 symbol referenced from the text segment, you need to add -D__ST_MT_ERRNO__
524 If everything seems to work fine but there's no curl.exe, you need to add
525 -Zexe to your linker flags.
527 If you're getting huge binaries, probably your makefiles have the -g in
533 (The VMS section is in whole contributed by the friendly Nico Baggus)
535 Curl seems to work with FTP & HTTP other protocols are not tested. (the
536 perl http/ftp testing server supplied as testing too cannot work on VMS
537 because vms has no concept of fork(). [ I tried to give it a whack, but
540 SSL stuff has not been ported.
542 Telnet has about the same issues as for Win32. When the changes for Win32
543 are clear maybe they'll work for VMS too. The basic problem is that select
544 ONLY works for sockets.
546 Marked instances of fopen/[f]stat that might become a problem, especially
547 for non stream files. In this regard, the files opened for writing will be
548 created stream/lf and will thus be safe. Just keep in mind that non-binary
549 read/wring from/to files will have a records size limit of 32767 bytes
552 Stat to get the size of the files is again only safe for stream files &
553 fixed record files without implied CC.
555 -- My guess is that only allowing access to stream files is the quickest
556 way to get around the most issues. Therefore all files need to to be
557 checked to be sure they will be stream/lf before processing them. This is
558 the easiest way out, I know. The reason for this is that code that needs to
559 report the filesize will become a pain in the ass otherwise.
561 Exit status.... Well we needed something done here,
563 VMS has a structured exist status:
565 |1098|765432109876|5432109876543|210|
566 +----+------------+-------------+---+
567 |Ctrl| Facility | Error code |sev|
568 +----+------------+-------------+---+
570 With the Ctrl-bits an application can tell if part or the whole message has
571 already been printed from the program, DCL doesn't need to print it again.
573 Facility - basically the program ID. A code assigned to the program
574 the name can be fetched from external or internal message libraries
575 Error code - the err codes assigned by the application
576 Sev. - severity: Even = error, off = non error
584 This all presents itself with:
585 %<FACILITY>-<Sev>-<Errorname>, <Error message>
587 See also the src/curlmsg.msg file, it has the source for the messages In
588 src/main.c a section is devoted to message status values, the globalvalues
589 create symbols with certain values, referenced from a compiled message
590 file. Have all exit function use a exit status derived from a translation
591 table with the compiled message codes.
593 This was all compiled with:
595 Compaq C V6.2-003 on OpenVMS Alpha V7.1-1H2
597 So far for porting notes as of:
604 (This section was graciously brought to us by David Bentham)
606 As QNX is targeted for resource constrained environments, the QNX headers
607 set conservative limits. This includes the FD_SETSIZE macro, set by default
608 to 32. Socket descriptors returned within the CURL library may exceed this,
609 resulting in memory faults/SIGSEGV crashes when passed into select(..)
610 calls using fd_set macros.
612 A good all-round solution to this is to override the default when building
613 libcurl, by overriding CFLAGS during configure, example
614 # configure CFLAGS='-DFD_SETSIZE=64 -g -O2'
619 The library can be cross-compiled using gccsdk as follows:
621 CC=riscos-gcc AR=riscos-ar RANLIB='riscos-ar -s' ./configure \
622 --host=arm-riscos-aof --without-random --disable-shared
625 where riscos-gcc and riscos-ar are links to the gccsdk tools.
626 You can then link your program with curl/lib/.libs/libcurl.a
631 (This section was graciously brought to us by Diego Casorran)
633 To build cURL/libcurl on AmigaOS just type 'make amiga' ...
635 What you need is: (not tested with others versions)
637 GeekGadgets / gcc 2.95.3 (http://www.geekgadgets.org/)
639 AmiTCP SDK v4.3 (http://www.aminet.net/comm/tcp/AmiTCP-SDK-4.3.lha)
641 Native Developer Kit (http://www.amiga.com/3.9/download/NDK3.9.lha)
643 As no ixemul.library is required you will be able to build it for
644 WarpOS/PowerPC (not tested by me), as well a MorphOS version should be
645 possible with no problems.
647 To enable SSL support, you need a OpenSSL native version (without ixemul),
648 you can find a precompiled package at http://amiga.sourceforge.net/OpenSSL/
653 To compile curl.nlm / libcurl.nlm you need:
654 - either any gcc / nlmconv, or CodeWarrior 7 PDK 4 or later.
655 - gnu make and awk running on the platform you compile on;
656 native Win32 versions can be downloaded from:
657 http://www.gknw.net/development/prgtools/
658 - recent Novell LibC SDK available from:
659 http://developer.novell.com/ndk/libc.htm
660 - or recent Novell CLib SDK available from:
661 http://developer.novell.com/ndk/clib.htm
662 - optional recent Novell CLDAP SDK available from:
663 http://developer.novell.com/ndk/cldap.htm
664 - optional zlib sources (static or dynamic linking with zlib.imp);
665 sources with NetWare Makefile can be obtained from:
666 http://www.gknw.net/mirror/zlib/
667 - optional OpenSSL sources (version 0.9.8 or later build with BSD sockets);
668 you can find precompiled packages at:
669 http://www.gknw.net/development/ossl/netware/
670 for CLIB-based builds OpenSSL 0.9.8h or later is required - earlier versions
671 don't support building with CLIB BSD sockets.
672 - optional SSH2 sources (version 0.17 or later);
674 Set a search path to your compiler, linker and tools; on Linux make
675 sure that the var OSTYPE contains the string 'linux'; set the var
676 NDKBASE to point to the base of your Novell NDK; and then type
677 'make netware' from the top source directory; other targets available
678 are 'netware-ssl', 'netware-ssl-zlib', 'netware-zlib' and 'netware-ares';
679 if you need other combinations you can control the build with the
680 environment variables WITH_SSL, WITH_ZLIB, WITH_ARES, WITH_SSH2, and
681 ENABLE_IPV6; you can set LINK_STATIC=1 to link curl.nlm statically.
682 By default LDAP support is enabled, however currently you will need a patch
683 in order to use the CLDAP NDK with BSD sockets (Novell Bug 300237):
684 http://www.gknw.net/test/curl/cldap_ndk/ldap_ndk.diff
685 I found on some Linux systems (RH9) that OS detection didn't work although
686 a 'set | grep OSTYPE' shows the var present and set; I simply overwrote it
687 with 'OSTYPE=linux-rh9-gnu' and the detection in the Makefile worked...
688 Any help in testing appreciated!
689 Builds automatically created 8 times a day from current git are here:
690 http://www.gknw.net/mirror/curl/autobuilds/
691 the status of these builds can be viewed at the autobuild table:
692 http://curl.haxx.se/dev/builds.html
697 curl does not use the eCos build system, so you must first build eCos
698 separately, then link curl to the resulting eCos library. Here's a sample
699 configure line to do so on an x86 Linux box targeting x86:
701 GCCLIB=`gcc -print-libgcc-file-name` && \
702 CFLAGS="-D__ECOS=1 -nostdinc -I$ECOS_INSTALL/include \
703 -I`dirname $GCCLIB`/include" \
704 LDFLAGS="-nostdlib -Wl,--gc-sections -Wl,-static \
705 -L$ECOS_INSTALL/lib -Ttarget.ld -ltarget" \
706 ./configure --host=i386 --disable-shared \
707 --without-ssl --without-zlib --disable-manual --disable-ldap
709 In most cases, eCos users will be using libcurl from within a custom
710 embedded application. Using the standard 'curl' executable from
711 within eCos means facing the limitation of the standard eCos C
712 startup code which does not allow passing arguments in main(). To
713 run 'curl' from eCos and have it do something useful, you will need
714 to either modify the eCos startup code to pass in some arguments, or
715 modify the curl application itself to retrieve its arguments from
716 some location set by the bootloader or hard-code them.
718 Something like the following patch could be used to hard-code some
719 arguments. The MTAB_ENTRY line mounts a RAM disk as the root filesystem
720 (without mounting some kind of filesystem, eCos errors out all file
721 operations which curl does not take to well). The next section synthesizes
722 some command-line arguments for curl to use, in this case to direct curl
723 to read further arguments from a file. It then creates that file on the
724 RAM disk and places within it a URL to download: a file: URL that
725 just happens to point to the configuration file itself. The results
726 of running curl in this way is the contents of the configuration file
727 printed to the console.
729 --- src/main.c 19 Jul 2006 19:09:56 -0000 1.363
730 +++ src/main.c 24 Jul 2006 21:37:23 -0000
731 @@ -4286,11 +4286,31 @@
736 +#include <cyg/fileio/fileio.h>
737 +MTAB_ENTRY( testfs_mte1,
744 int main(int argc, char *argv[])
747 struct Configurable config;
749 + char *args[] = {"ecos-curl", "-K", "curlconf.txt"};
751 + argc = sizeof(args)/sizeof(args[0]);
754 + f = fopen("curlconf.txt", "w");
756 + fprintf(f, "--url file:curlconf.txt");
760 memset(&config, 0, sizeof(struct Configurable));
762 config.errors = stderr; /* default errors to stderr */
767 curl can be compiled on Minix 3 using gcc or ACK (starting with
768 ver. 3.1.3). Ensure that GNU gawk and bash are both installed and
769 available in the PATH.
773 Increase the heap sizes of the compiler with the command:
777 then configure and compile curl with:
779 ./configure CC=cc LD=cc AR=/usr/bin/aal GREP=grep \
780 CPPFLAGS='-D_POSIX_SOURCE=1 -I/usr/local/include'
782 chmem =256000 src/curl
786 Make sure gcc is in your PATH with the command:
788 export PATH=/usr/gnu/bin:$PATH
790 then configure and compile curl with:
792 ./configure CC=gcc AR=/usr/gnu/bin/gar GREP=grep
794 chmem =256000 src/curl
799 The Symbian OS port uses the Symbian build system to compile. From the
800 packages/Symbian/group/ directory, run:
805 to compile and install curl and libcurl using SBSv1. If your Symbian
806 SDK doesn't include support for P.I.P.S., you will need to contact
807 your SDK vendor to obtain that first.
812 Build for VxWorks is performed using cross compilation.
813 That means you build on Windows machine using VxWorks tools and
814 run the built image on the VxWorks device.
816 To build libcurl for VxWorks you need:
818 - CYGWIN (free, http://cygwin.com/)
819 - Wind River Workbench (commercial)
821 If you have CYGWIN and Workbench installed on you machine
822 follow after next steps:
824 1. Open the Command Prompt window and change directory ('cd')
825 to the libcurl 'lib' folder.
826 2. Add CYGWIN 'bin' folder to the PATH environment variable.
827 For example, type 'set PATH=C:/embedded/cygwin/bin;%PATH%'.
828 3. Adjust environment variables defined in 'Environment' section
829 of the Makefile.vxworks file to point to your software folders.
830 4. Build the libcurl by typing 'make -f ./Makefile.vxworks'
832 As a result the libcurl.a library should be created in the 'lib' folder.
833 To clean the build results type 'make -f ./Makefile.vxworks clean'.
838 Method using the static makefile:
839 - see the build notes in the packages/Android/Android.mk file.
841 Method using a configure cross-compile (tested with Android NDK r7c, r8):
842 - prepare the toolchain of the Android NDK for standalone use; this can
843 be done by invoking the script:
844 ./build/tools/make-standalone-toolchain.sh
845 which creates a usual cross-compile toolchain. Lets assume that you put
846 this toolchain below /opt then invoke configure with something like:
847 export PATH=/opt/arm-linux-androideabi-4.4.3/bin:$PATH
848 ./configure --host=arm-linux-androideabi [more configure options]
850 - if you want to compile directly from our GIT repo you might run into
851 this issue with older automake stuff:
852 checking host system type...
853 Invalid configuration `arm-linux-androideabi':
854 system `androideabi' not recognized
855 configure: error: /bin/sh ./config.sub arm-linux-androideabi failed
856 this issue can be fixed with using more recent versions of config.sub
857 and config.guess which can be obtained here:
858 http://git.savannah.gnu.org/gitweb/?p=config.git;a=tree
859 you need to replace your system-own versions which usually can be
860 found in your automake folder:
861 find /usr -name config.sub
863 Wrapper for pkg-config
864 - In order to make proper use of pkg-config so that configure is able to
865 find all dependencies you should create a wrapper script for pkg-config;
866 file /opt/arm-linux-androideabi-4.4.3/bin/arm-linux-androideabi-pkg-config:
869 SYSROOT=$(dirname ${0%/*})/sysroot
870 export PKG_CONFIG_DIR=
871 export PKG_CONFIG_LIBDIR=${SYSROOT}/usr/local/lib/pkgconfig:${SYSROOT}/usr/share/pkgconfig
872 export PKG_CONFIG_SYSROOT_DIR=${SYSROOT}
875 also create a copy or symlink with name arm-unknown-linux-androideabi-pkg-config.
880 (This section was graciously brought to us by Jim Duey, with additions by
883 Download and unpack the cURL package.
885 'cd' to the new directory. (e.g. cd curl-7.12.3)
887 Set environment variables to point to the cross-compile toolchain and call
888 configure with any options you need. Be sure and specify the '--host' and
889 '--build' parameters at configuration time. The following script is an
890 example of cross-compiling for the IBM 405GP PowerPC processor using the
891 toolchain from MonteVista for Hardhat Linux.
897 export PATH=$PATH:/opt/hardhat/devkit/ppc/405/bin
898 export CPPFLAGS="-I/opt/hardhat/devkit/ppc/405/target/usr/include"
902 export RANLIB=ppc_405-ranlib
903 export CC=ppc_405-gcc
906 ./configure --target=powerpc-hardhat-linux \
907 --host=powerpc-hardhat-linux \
908 --build=i586-pc-linux-gnu \
909 --prefix=/opt/hardhat/devkit/ppc/405/target/usr/local \
910 --exec-prefix=/usr/local
914 You may also need to provide a parameter like '--with-random=/dev/urandom'
915 to configure as it cannot detect the presence of a random number
916 generating device for a target system. The '--prefix' parameter
917 specifies where cURL will be installed. If 'configure' completes
918 successfully, do 'make' and 'make install' as usual.
920 In some cases, you may be able to simplify the above commands to as
923 ./configure --host=ARCH-OS
928 There are a number of configure options that can be used to reduce the
929 size of libcurl for embedded applications where binary size is an
930 important factor. First, be sure to set the CFLAGS variable when
931 configuring with any relevant compiler optimization flags to reduce the
932 size of the binary. For gcc, this would mean at minimum the -Os option,
933 and potentially the -march=X and -mdynamic-no-pic options as well, e.g.
935 ./configure CFLAGS='-Os' ...
937 Note that newer compilers often produce smaller code than older versions
938 due to improved optimization.
940 Be sure to specify as many --disable- and --without- flags on the configure
941 command-line as you can to disable all the libcurl features that you
942 know your application is not going to need. Besides specifying the
943 --disable-PROTOCOL flags for all the types of URLs your application
944 will not use, here are some other flags that can reduce the size of the
947 --disable-ares (disables support for the C-ARES DNS library)
948 --disable-cookies (disables support for HTTP cookies)
949 --disable-crypto-auth (disables HTTP cryptographic authentication)
950 --disable-ipv6 (disables support for IPv6)
951 --disable-manual (disables support for the built-in documentation)
952 --disable-proxy (disables support for HTTP and SOCKS proxies)
953 --disable-verbose (eliminates debugging strings and error code strings)
954 --enable-hidden-symbols (eliminates unneeded symbols in the shared library)
955 --without-libidn (disables support for the libidn DNS library)
956 --without-librtmp (disables support for RTMP)
957 --without-ssl (disables support for SSL/TLS)
958 --without-zlib (disables support for on-the-fly decompression)
960 The GNU compiler and linker have a number of options that can reduce the
961 size of the libcurl dynamic libraries on some platforms even further.
962 Specify them by providing appropriate CFLAGS and LDFLAGS variables on the
963 configure command-line, e.g.
964 CFLAGS="-Os -ffunction-sections -fdata-sections \
965 -fno-unwind-tables -fno-asynchronous-unwind-tables" \
966 LDFLAGS="-Wl,-s -Wl,-Bsymbolic -Wl,--gc-sections"
968 Be sure also to strip debugging symbols from your binaries after
969 compiling using 'strip' (or the appropriate variant if cross-compiling).
970 If space is really tight, you may be able to remove some unneeded
971 sections of the shared library using the -R option to objcopy (e.g. the
974 Using these techniques it is possible to create a basic HTTP-only shared
975 libcurl library for i386 Linux platforms that is only 114 KiB in size, and
976 an FTP-only library that is 115 KiB in size (as of libcurl version 7.35.0,
979 You may find that statically linking libcurl to your application will
980 result in a lower total size than dynamically linking.
982 Note that the curl test harness can detect the use of some, but not all, of
983 the --disable statements suggested above. Use will cause tests relying on
984 those features to fail. The test harness can be manually forced to skip
985 the relevant tests by specifying certain key words on the runtests.pl
986 command line. Following is a list of appropriate key words:
988 --disable-cookies !cookies
989 --disable-manual !--manual
990 --disable-proxy !HTTP\ proxy !proxytunnel !SOCKS4 !SOCKS5
995 This is a probably incomplete list of known hardware and operating systems
996 that curl has been compiled for. If you know a system curl compiles and
997 runs on, that isn't listed, please let us know!
1000 - Alpha Digital UNIX v3.2
1001 - Alpha FreeBSD 4.1, 4.5
1002 - Alpha Linux 2.2, 2.4
1003 - Alpha NetBSD 1.5.2
1005 - Alpha OpenVMS V7.1-1H2
1006 - Alpha Tru64 v5.0 5.1
1008 - ARM Android 1.5, 2.1, 2.3, 3.2, 4.x
1013 - HP-PA HP-UX 9.X 10.X 11.X
1016 - MicroBlaze uClinux
1017 - MIPS IRIX 6.2, 6.5
1020 - Pocket PC/Win CE 3.0
1021 - Power AIX 3.2.5, 4.2, 4.3.1, 4.3.2, 5.1, 5.2
1022 - PowerPC Darwin 1.0
1031 - Sparc Solaris 2.4, 2.5, 2.5.1, 2.6, 7, 8, 9, 10
1033 - StrongARM (and other ARM) RISC OS 3.1, 4.02
1034 - StrongARM/ARM7/ARM9 Linux 2.4, 2.6
1035 - StrongARM NetBSD 1.4.1
1036 - Symbian OS (P.I.P.S.) 9.x
1047 - i386 Linux 1.3, 2.0, 2.2, 2.3, 2.4, 2.6
1051 - i386 Novell NetWare
1057 - i386 Windows 95, 98, ME, NT, 2000, XP, 2003
1058 - i486 ncr-sysv4.3.03 (NCR MP-RAS)
1064 - m88k dg-dgux5.4R3.00
1067 - XScale/PXA250 Linux 2.4
1073 axTLS http://axtls.sourceforge.net/
1074 c-ares http://c-ares.haxx.se/
1075 GNU GSS http://www.gnu.org/software/gss/
1076 GnuTLS http://www.gnu.org/software/gnutls/
1077 Heimdal http://www.pdc.kth.se/heimdal/
1078 libidn http://www.gnu.org/software/libidn/
1079 libmetalink https://launchpad.net/libmetalink/
1080 libssh2 http://www.libssh2.org/
1081 MIT Kerberos http://web.mit.edu/kerberos/www/dist/
1082 NSS http://www.mozilla.org/projects/security/pki/nss/
1083 OpenLDAP http://www.openldap.org/
1084 OpenSSL http://www.openssl.org/
1085 PolarSSL http://polarssl.org/
1086 yassl http://www.yassl.com/
1087 Zlib http://www.zlib.net/
1089 MingW http://www.mingw.org/
1090 MinGW-w64 http://mingw-w64.sourceforge.net/
1091 OpenWatcom http://www.openwatcom.org/