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 PSDK:
256 http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm
258 Building any software with MSVC 6 without having PSDK installed is just
259 asking for trouble down the road once you have released it, you might notice
260 the problems in the first corner or ten miles ahead, depending mostly on your
261 choice of static vs dynamic runtime and third party libraries. Anyone using
262 software built in such way will at some point regret having done so.
264 When someone uses MSVC 6 without PSDK he is using a compiler back from 1998.
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 In order to make use of the updated system headers and fixed libraries
276 for MSVC 6, it is required that 'Platform SDK', PSDK from now onwards,
277 is installed. The specific PSDK that must be installed for MSVC 6 is the
278 February 2003 edition, which is the latest one supporting the MSVC 6 compiler,
279 this PSDK is also known as 'Windows Server 2003 PSDK' and can be downloaded
280 from http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm
282 So, building curl and libcurl with MSVC 6 without PSDK is absolutely
283 discouraged for the benefit of anyone using software built in such
284 environment. And it will not be supported in any way, as we could just
285 be hunting bugs which have already been fixed way back in 2003.
287 When building with MSVC 6 we attempt to detect if PSDK is not being used,
288 and if this is the case the build process will fail hard with an error
289 message stating that the February 2003 PSDK is required. This is done to
290 protect the unsuspecting and avoid PEBKAC issues.
292 Additionally it might happen that a die hard MSVC hacker still wants to
293 build curl and libcurl with MSVC 6 without PSDK installed, even knowing
294 that this is a highly discouraged and unsupported build environment. In
295 this case the brave of heart will be able to build in such an environment
296 with the requisite of defining preprocessor symbol ALLOW_MSVC6_WITHOUT_PSDK
297 in lib/config-win32.h and knowing that LDAP and IPv6 support will be missing.
299 MSVC from command line
300 ----------------------
302 Run the 'vcvars32.bat' file to get a proper environment. The
303 vcvars32.bat file is part of the Microsoft development environment and
304 you may find it in 'C:\Program Files\Microsoft Visual Studio\vc98\bin'
305 provided that you installed Visual C/C++ 6 in the default directory.
307 Then run 'nmake vc' in curl's root directory.
309 If you want to compile with zlib support, you will need to build
310 zlib (http://www.gzip.org/zlib/) as well. Please read the zlib
311 documentation on how to compile zlib. Define the ZLIB_PATH environment
312 variable to the location of zlib.h and zlib.lib, for example:
314 set ZLIB_PATH=c:\zlib-1.2.8
316 Then run 'nmake vc-zlib' in curl's root directory.
318 If you want to compile with SSL support you need the OpenSSL package.
319 Please read the OpenSSL documentation on how to compile and install
320 the OpenSSL libraries. The build process of OpenSSL generates the
321 libeay32.dll and ssleay32.dll files in the out32dll subdirectory in
322 the OpenSSL home directory. OpenSSL static libraries (libeay32.lib,
323 ssleay32.lib, RSAglue.lib) are created in the out32 subdirectory.
325 Before running nmake define the OPENSSL_PATH environment variable with
326 the root/base directory of OpenSSL, for example:
328 set OPENSSL_PATH=c:\openssl-0.9.8y
330 Then run 'nmake vc-ssl' or 'nmake vc-ssl-dll' in curl's root
331 directory. 'nmake vc-ssl' will create a libcurl static and dynamic
332 libraries in the lib subdirectory, as well as a statically linked
333 version of curl.exe in the src subdirectory. This statically linked
334 version is a standalone executable not requiring any DLL at
335 runtime. This make method requires that you have the static OpenSSL
336 libraries available in OpenSSL's out32 subdirectory.
337 'nmake vc-ssl-dll' creates the libcurl dynamic library and
338 links curl.exe against libcurl and OpenSSL dynamically.
339 This executable requires libcurl.dll and the OpenSSL DLLs
341 Run 'nmake vc-ssl-zlib' to build with both ssl and zlib support.
346 A fairly comprehensive set of Visual Studio project files are available for
347 v6.0 through v12.0 and are located in the projects folder to allow proper
348 building of both the libcurl library as well as the curl tool.
350 For more information about these projects and building via Visual Studio
351 please see the README file located in the projects folder.
356 Ensure that your build environment is properly set up to use the compiler
357 and associated tools. PATH environment variable must include the path to
358 bin subdirectory of your compiler installation, eg: c:\Borland\BCC55\bin
360 It is advisable to set environment variable BCCDIR to the base path of
361 the compiler installation.
363 set BCCDIR=c:\Borland\BCC55
365 In order to build a plain vanilla version of curl and libcurl run the
366 following command from curl's root directory:
370 To build curl and libcurl with zlib and OpenSSL support set environment
371 variables ZLIB_PATH and OPENSSL_PATH to the base subdirectories of the
372 already built zlib and OpenSSL libraries and from curl's root directory
375 make borland-ssl-zlib
377 libcurl library will be built in 'lib' subdirectory while curl tool
378 is built in 'src' subdirectory. In order to use libcurl library it is
379 advisable to modify compiler's configuration file bcc32.cfg located
380 in c:\Borland\BCC55\bin to reflect the location of libraries include
381 paths for example the '-I' line could result in something like:
383 -I"c:\Borland\BCC55\include;c:\curl\include;c:\openssl\inc32"
385 bcc3.cfg '-L' line could also be modified to reflect the location of
386 of libcurl library resulting for example:
388 -L"c:\Borland\BCC55\lib;c:\curl\lib;c:\openssl\out32"
390 In order to build sample program 'simple.c' from the docs\examples
391 subdirectory run following command from mentioned subdirectory:
393 bcc32 simple.c libcurl.lib cw32mt.lib
395 In order to build sample program simplessl.c an SSL enabled libcurl
396 is required, as well as the OpenSSL libeay32.lib and ssleay32.lib
403 If you use VC++, Borland or similar compilers. Include all lib source
404 files in a static lib "project" (all .c and .h files that is).
405 (you should name it libcurl or similar)
407 Make the sources in the src/ drawer be a "win32 console application"
408 project. Name it curl.
411 Disabling Specific Protocols in Win32 builds
412 --------------------------------------------
414 The configure utility, unfortunately, is not available for the Windows
415 environment, therefore, you cannot use the various disable-protocol
416 options of the configure utility on this platform.
418 However, you can use the following defines to disable specific
421 HTTP_ONLY disables all protocols except HTTP
422 CURL_DISABLE_FTP disables FTP
423 CURL_DISABLE_LDAP disables LDAP
424 CURL_DISABLE_TELNET disables TELNET
425 CURL_DISABLE_DICT disables DICT
426 CURL_DISABLE_FILE disables FILE
427 CURL_DISABLE_TFTP disables TFTP
428 CURL_DISABLE_HTTP disables HTTP
430 If you want to set any of these defines you have the following
433 - Modify lib/config-win32.h
434 - Modify lib/curl_setup.h
435 - Modify lib/Makefile.vc6
436 - Add defines to Project/Settings/C/C++/General/Preprocessor Definitions
437 in the vc6libcurl.dsw/vc6libcurl.dsp Visual C++ 6 IDE project.
440 Using BSD-style lwIP instead of Winsock TCP/IP stack in Win32 builds
441 --------------------------------------------------------------------
443 In order to compile libcurl and curl using BSD-style lwIP TCP/IP stack
444 it is necessary to make definition of preprocessor symbol USE_LWIPSOCK
445 visible to libcurl and curl compilation processes. To set this definition
446 you have the following alternatives:
448 - Modify lib/config-win32.h and src/config-win32.h
449 - Modify lib/Makefile.vc6
450 - Add definition to Project/Settings/C/C++/General/Preprocessor Definitions
451 in the vc6libcurl.dsw/vc6libcurl.dsp Visual C++ 6 IDE project.
453 Once that libcurl has been built with BSD-style lwIP TCP/IP stack support,
454 in order to use it with your program it is mandatory that your program
455 includes lwIP header file <lwip/opt.h> (or another lwIP header that includes
456 this) before including any libcurl header. Your program does not need the
457 USE_LWIPSOCK preprocessor definition which is for libcurl internals only.
459 Compilation has been verified with lwIP 1.4.0 and contrib-1.4.0 from:
461 http://download.savannah.gnu.org/releases/lwip/lwip-1.4.0.zip
462 http://download.savannah.gnu.org/releases/lwip/contrib-1.4.0.zip
464 This BSD-style lwIP TCP/IP stack support must be considered experimental
465 given that it has been verified that lwIP 1.4.0 still needs some polish,
466 and libcurl might yet need some additional adjustment, caveat emptor.
468 Important static libcurl usage note
469 -----------------------------------
471 When building an application that uses the static libcurl library, you must
472 add '-DCURL_STATICLIB' to your CFLAGS. Otherwise the linker will look for
473 dynamic import symbols.
476 Apple iOS and Mac OS X
477 ======================
478 On recent Apple operating systems, curl can be built to use Apple's
479 SSL/TLS implementation, Secure Transport, instead of OpenSSL. To build with
480 Secure Transport for SSL/TLS, use the configure option --with-darwinssl. (It
481 is not necessary to use the option --without-ssl.) This feature requires iOS
482 5.0 or later, or OS X 10.5 ("Leopard") or later.
484 When Secure Transport is in use, the curl options --cacert and --capath and
485 their libcurl equivalents, will be ignored, because Secure Transport uses
486 the certificates stored in the Keychain to evaluate whether or not to trust
487 the server. This, of course, includes the root certificates that ship with
488 the OS. The --cert and --engine options, and their libcurl equivalents, are
489 currently unimplemented in curl with Secure Transport.
491 For OS X users: In OS X 10.8 ("Mountain Lion"), Apple made a major
492 overhaul to the Secure Transport API that, among other things, added
493 support for the newer TLS 1.1 and 1.2 protocols. To get curl to support
494 TLS 1.1 and 1.2, you must build curl on Mountain Lion or later, or by
495 using the equivalent SDK. If you set the MACOSX_DEPLOYMENT_TARGET
496 environmental variable to an earlier version of OS X prior to building curl,
497 then curl will use the new Secure Transport API on Mountain Lion and later,
498 and fall back on the older API when the same curl binary is executed on
499 older cats. For example, running these commands in curl's directory in the
500 shell will build the code such that it will run on cats as old as OS X 10.6
501 ("Snow Leopard") (using bash):
503 export MACOSX_DEPLOYMENT_TARGET="10.6"
504 ./configure --with-darwinssl
510 Building under OS/2 is not much different from building under unix.
522 If you want to build with OpenSSL or OpenLDAP support, you'll need to
523 download those libraries, too. Dirk Ohme has done some work to port SSL
524 libraries under OS/2, but it looks like he doesn't care about emx. You'll
525 find his patches on: http://come.to/Dirk_Ohme
527 If during the linking you get an error about _errno being an undefined
528 symbol referenced from the text segment, you need to add -D__ST_MT_ERRNO__
531 If everything seems to work fine but there's no curl.exe, you need to add
532 -Zexe to your linker flags.
534 If you're getting huge binaries, probably your makefiles have the -g in
540 (The VMS section is in whole contributed by the friendly Nico Baggus)
542 Curl seems to work with FTP & HTTP other protocols are not tested. (the
543 perl http/ftp testing server supplied as testing too cannot work on VMS
544 because vms has no concept of fork(). [ I tried to give it a whack, but
547 SSL stuff has not been ported.
549 Telnet has about the same issues as for Win32. When the changes for Win32
550 are clear maybe they'll work for VMS too. The basic problem is that select
551 ONLY works for sockets.
553 Marked instances of fopen/[f]stat that might become a problem, especially
554 for non stream files. In this regard, the files opened for writing will be
555 created stream/lf and will thus be safe. Just keep in mind that non-binary
556 read/wring from/to files will have a records size limit of 32767 bytes
559 Stat to get the size of the files is again only safe for stream files &
560 fixed record files without implied CC.
562 -- My guess is that only allowing access to stream files is the quickest
563 way to get around the most issues. Therefore all files need to to be
564 checked to be sure they will be stream/lf before processing them. This is
565 the easiest way out, I know. The reason for this is that code that needs to
566 report the filesize will become a pain in the ass otherwise.
568 Exit status.... Well we needed something done here,
570 VMS has a structured exist status:
572 |1098|765432109876|5432109876543|210|
573 +----+------------+-------------+---+
574 |Ctrl| Facility | Error code |sev|
575 +----+------------+-------------+---+
577 With the Ctrl-bits an application can tell if part or the whole message has
578 already been printed from the program, DCL doesn't need to print it again.
580 Facility - basically the program ID. A code assigned to the program
581 the name can be fetched from external or internal message libraries
582 Error code - the err codes assigned by the application
583 Sev. - severity: Even = error, off = non error
591 This all presents itself with:
592 %<FACILITY>-<Sev>-<Errorname>, <Error message>
594 See also the src/curlmsg.msg file, it has the source for the messages In
595 src/main.c a section is devoted to message status values, the globalvalues
596 create symbols with certain values, referenced from a compiled message
597 file. Have all exit function use a exit status derived from a translation
598 table with the compiled message codes.
600 This was all compiled with:
602 Compaq C V6.2-003 on OpenVMS Alpha V7.1-1H2
604 So far for porting notes as of:
611 (This section was graciously brought to us by David Bentham)
613 As QNX is targeted for resource constrained environments, the QNX headers
614 set conservative limits. This includes the FD_SETSIZE macro, set by default
615 to 32. Socket descriptors returned within the CURL library may exceed this,
616 resulting in memory faults/SIGSEGV crashes when passed into select(..)
617 calls using fd_set macros.
619 A good all-round solution to this is to override the default when building
620 libcurl, by overriding CFLAGS during configure, example
621 # configure CFLAGS='-DFD_SETSIZE=64 -g -O2'
626 The library can be cross-compiled using gccsdk as follows:
628 CC=riscos-gcc AR=riscos-ar RANLIB='riscos-ar -s' ./configure \
629 --host=arm-riscos-aof --without-random --disable-shared
632 where riscos-gcc and riscos-ar are links to the gccsdk tools.
633 You can then link your program with curl/lib/.libs/libcurl.a
638 (This section was graciously brought to us by Diego Casorran)
640 To build cURL/libcurl on AmigaOS just type 'make amiga' ...
642 What you need is: (not tested with others versions)
644 GeekGadgets / gcc 2.95.3 (http://www.geekgadgets.org/)
646 AmiTCP SDK v4.3 (http://www.aminet.net/comm/tcp/AmiTCP-SDK-4.3.lha)
648 Native Developer Kit (http://www.amiga.com/3.9/download/NDK3.9.lha)
650 As no ixemul.library is required you will be able to build it for
651 WarpOS/PowerPC (not tested by me), as well a MorphOS version should be
652 possible with no problems.
654 To enable SSL support, you need a OpenSSL native version (without ixemul),
655 you can find a precompiled package at http://amiga.sourceforge.net/OpenSSL/
660 To compile curl.nlm / libcurl.nlm you need:
661 - either any gcc / nlmconv, or CodeWarrior 7 PDK 4 or later.
662 - gnu make and awk running on the platform you compile on;
663 native Win32 versions can be downloaded from:
664 http://www.gknw.net/development/prgtools/
665 - recent Novell LibC SDK available from:
666 http://developer.novell.com/ndk/libc.htm
667 - or recent Novell CLib SDK available from:
668 http://developer.novell.com/ndk/clib.htm
669 - optional recent Novell CLDAP SDK available from:
670 http://developer.novell.com/ndk/cldap.htm
671 - optional zlib sources (static or dynamic linking with zlib.imp);
672 sources with NetWare Makefile can be obtained from:
673 http://www.gknw.net/mirror/zlib/
674 - optional OpenSSL sources (version 0.9.8 or later build with BSD sockets);
675 you can find precompiled packages at:
676 http://www.gknw.net/development/ossl/netware/
677 for CLIB-based builds OpenSSL 0.9.8h or later is required - earlier versions
678 don't support building with CLIB BSD sockets.
679 - optional SSH2 sources (version 0.17 or later);
681 Set a search path to your compiler, linker and tools; on Linux make
682 sure that the var OSTYPE contains the string 'linux'; set the var
683 NDKBASE to point to the base of your Novell NDK; and then type
684 'make netware' from the top source directory; other targets available
685 are 'netware-ssl', 'netware-ssl-zlib', 'netware-zlib' and 'netware-ares';
686 if you need other combinations you can control the build with the
687 environment variables WITH_SSL, WITH_ZLIB, WITH_ARES, WITH_SSH2, and
688 ENABLE_IPV6; you can set LINK_STATIC=1 to link curl.nlm statically.
689 By default LDAP support is enabled, however currently you will need a patch
690 in order to use the CLDAP NDK with BSD sockets (Novell Bug 300237):
691 http://www.gknw.net/test/curl/cldap_ndk/ldap_ndk.diff
692 I found on some Linux systems (RH9) that OS detection didn't work although
693 a 'set | grep OSTYPE' shows the var present and set; I simply overwrote it
694 with 'OSTYPE=linux-rh9-gnu' and the detection in the Makefile worked...
695 Any help in testing appreciated!
696 Builds automatically created 8 times a day from current git are here:
697 http://www.gknw.net/mirror/curl/autobuilds/
698 the status of these builds can be viewed at the autobuild table:
699 http://curl.haxx.se/dev/builds.html
704 curl does not use the eCos build system, so you must first build eCos
705 separately, then link curl to the resulting eCos library. Here's a sample
706 configure line to do so on an x86 Linux box targeting x86:
708 GCCLIB=`gcc -print-libgcc-file-name` && \
709 CFLAGS="-D__ECOS=1 -nostdinc -I$ECOS_INSTALL/include \
710 -I`dirname $GCCLIB`/include" \
711 LDFLAGS="-nostdlib -Wl,--gc-sections -Wl,-static \
712 -L$ECOS_INSTALL/lib -Ttarget.ld -ltarget" \
713 ./configure --host=i386 --disable-shared \
714 --without-ssl --without-zlib --disable-manual --disable-ldap
716 In most cases, eCos users will be using libcurl from within a custom
717 embedded application. Using the standard 'curl' executable from
718 within eCos means facing the limitation of the standard eCos C
719 startup code which does not allow passing arguments in main(). To
720 run 'curl' from eCos and have it do something useful, you will need
721 to either modify the eCos startup code to pass in some arguments, or
722 modify the curl application itself to retrieve its arguments from
723 some location set by the bootloader or hard-code them.
725 Something like the following patch could be used to hard-code some
726 arguments. The MTAB_ENTRY line mounts a RAM disk as the root filesystem
727 (without mounting some kind of filesystem, eCos errors out all file
728 operations which curl does not take to well). The next section synthesizes
729 some command-line arguments for curl to use, in this case to direct curl
730 to read further arguments from a file. It then creates that file on the
731 RAM disk and places within it a URL to download: a file: URL that
732 just happens to point to the configuration file itself. The results
733 of running curl in this way is the contents of the configuration file
734 printed to the console.
736 --- src/main.c 19 Jul 2006 19:09:56 -0000 1.363
737 +++ src/main.c 24 Jul 2006 21:37:23 -0000
738 @@ -4286,11 +4286,31 @@
743 +#include <cyg/fileio/fileio.h>
744 +MTAB_ENTRY( testfs_mte1,
751 int main(int argc, char *argv[])
754 struct Configurable config;
756 + char *args[] = {"ecos-curl", "-K", "curlconf.txt"};
758 + argc = sizeof(args)/sizeof(args[0]);
761 + f = fopen("curlconf.txt", "w");
763 + fprintf(f, "--url file:curlconf.txt");
767 memset(&config, 0, sizeof(struct Configurable));
769 config.errors = stderr; /* default errors to stderr */
774 curl can be compiled on Minix 3 using gcc or ACK (starting with
775 ver. 3.1.3). Ensure that GNU gawk and bash are both installed and
776 available in the PATH.
780 Increase the heap sizes of the compiler with the command:
784 then configure and compile curl with:
786 ./configure CC=cc LD=cc AR=/usr/bin/aal GREP=grep \
787 CPPFLAGS='-D_POSIX_SOURCE=1 -I/usr/local/include'
789 chmem =256000 src/curl
793 Make sure gcc is in your PATH with the command:
795 export PATH=/usr/gnu/bin:$PATH
797 then configure and compile curl with:
799 ./configure CC=gcc AR=/usr/gnu/bin/gar GREP=grep
801 chmem =256000 src/curl
806 The Symbian OS port uses the Symbian build system to compile. From the
807 packages/Symbian/group/ directory, run:
812 to compile and install curl and libcurl using SBSv1. If your Symbian
813 SDK doesn't include support for P.I.P.S., you will need to contact
814 your SDK vendor to obtain that first.
819 Build for VxWorks is performed using cross compilation.
820 That means you build on Windows machine using VxWorks tools and
821 run the built image on the VxWorks device.
823 To build libcurl for VxWorks you need:
825 - CYGWIN (free, http://cygwin.com/)
826 - Wind River Workbench (commercial)
828 If you have CYGWIN and Workbench installed on you machine
829 follow after next steps:
831 1. Open the Command Prompt window and change directory ('cd')
832 to the libcurl 'lib' folder.
833 2. Add CYGWIN 'bin' folder to the PATH environment variable.
834 For example, type 'set PATH=C:/embedded/cygwin/bin;%PATH%'.
835 3. Adjust environment variables defined in 'Environment' section
836 of the Makefile.vxworks file to point to your software folders.
837 4. Build the libcurl by typing 'make -f ./Makefile.vxworks'
839 As a result the libcurl.a library should be created in the 'lib' folder.
840 To clean the build results type 'make -f ./Makefile.vxworks clean'.
845 Method using the static makefile:
846 - see the build notes in the packages/Android/Android.mk file.
848 Method using a configure cross-compile (tested with Android NDK r7c, r8):
849 - prepare the toolchain of the Android NDK for standalone use; this can
850 be done by invoking the script:
851 ./build/tools/make-standalone-toolchain.sh
852 which creates a usual cross-compile toolchain. Lets assume that you put
853 this toolchain below /opt then invoke configure with something like:
854 export PATH=/opt/arm-linux-androideabi-4.4.3/bin:$PATH
855 ./configure --host=arm-linux-androideabi [more configure options]
857 - if you want to compile directly from our GIT repo you might run into
858 this issue with older automake stuff:
859 checking host system type...
860 Invalid configuration `arm-linux-androideabi':
861 system `androideabi' not recognized
862 configure: error: /bin/sh ./config.sub arm-linux-androideabi failed
863 this issue can be fixed with using more recent versions of config.sub
864 and config.guess which can be obtained here:
865 http://git.savannah.gnu.org/gitweb/?p=config.git;a=tree
866 you need to replace your system-own versions which usually can be
867 found in your automake folder:
868 find /usr -name config.sub
870 Wrapper for pkg-config
871 - In order to make proper use of pkg-config so that configure is able to
872 find all dependencies you should create a wrapper script for pkg-config;
873 file /opt/arm-linux-androideabi-4.4.3/bin/arm-linux-androideabi-pkg-config:
876 SYSROOT=$(dirname ${0%/*})/sysroot
877 export PKG_CONFIG_DIR=
878 export PKG_CONFIG_LIBDIR=${SYSROOT}/usr/local/lib/pkgconfig:${SYSROOT}/usr/share/pkgconfig
879 export PKG_CONFIG_SYSROOT_DIR=${SYSROOT}
882 also create a copy or symlink with name arm-unknown-linux-androideabi-pkg-config.
887 (This section was graciously brought to us by Jim Duey, with additions by
890 Download and unpack the cURL package.
892 'cd' to the new directory. (e.g. cd curl-7.12.3)
894 Set environment variables to point to the cross-compile toolchain and call
895 configure with any options you need. Be sure and specify the '--host' and
896 '--build' parameters at configuration time. The following script is an
897 example of cross-compiling for the IBM 405GP PowerPC processor using the
898 toolchain from MonteVista for Hardhat Linux.
904 export PATH=$PATH:/opt/hardhat/devkit/ppc/405/bin
905 export CPPFLAGS="-I/opt/hardhat/devkit/ppc/405/target/usr/include"
909 export RANLIB=ppc_405-ranlib
910 export CC=ppc_405-gcc
913 ./configure --target=powerpc-hardhat-linux \
914 --host=powerpc-hardhat-linux \
915 --build=i586-pc-linux-gnu \
916 --prefix=/opt/hardhat/devkit/ppc/405/target/usr/local \
917 --exec-prefix=/usr/local
921 You may also need to provide a parameter like '--with-random=/dev/urandom'
922 to configure as it cannot detect the presence of a random number
923 generating device for a target system. The '--prefix' parameter
924 specifies where cURL will be installed. If 'configure' completes
925 successfully, do 'make' and 'make install' as usual.
927 In some cases, you may be able to simplify the above commands to as
930 ./configure --host=ARCH-OS
935 There are a number of configure options that can be used to reduce the
936 size of libcurl for embedded applications where binary size is an
937 important factor. First, be sure to set the CFLAGS variable when
938 configuring with any relevant compiler optimization flags to reduce the
939 size of the binary. For gcc, this would mean at minimum the -Os option,
940 and potentially the -march=X and -mdynamic-no-pic options as well, e.g.
942 ./configure CFLAGS='-Os' ...
944 Note that newer compilers often produce smaller code than older versions
945 due to improved optimization.
947 Be sure to specify as many --disable- and --without- flags on the configure
948 command-line as you can to disable all the libcurl features that you
949 know your application is not going to need. Besides specifying the
950 --disable-PROTOCOL flags for all the types of URLs your application
951 will not use, here are some other flags that can reduce the size of the
954 --disable-ares (disables support for the C-ARES DNS library)
955 --disable-cookies (disables support for HTTP cookies)
956 --disable-crypto-auth (disables HTTP cryptographic authentication)
957 --disable-ipv6 (disables support for IPv6)
958 --disable-manual (disables support for the built-in documentation)
959 --disable-proxy (disables support for HTTP and SOCKS proxies)
960 --disable-verbose (eliminates debugging strings and error code strings)
961 --enable-hidden-symbols (eliminates unneeded symbols in the shared library)
962 --without-libidn (disables support for the libidn DNS library)
963 --without-librtmp (disables support for RTMP)
964 --without-ssl (disables support for SSL/TLS)
965 --without-zlib (disables support for on-the-fly decompression)
967 The GNU compiler and linker have a number of options that can reduce the
968 size of the libcurl dynamic libraries on some platforms even further.
969 Specify them by providing appropriate CFLAGS and LDFLAGS variables on the
970 configure command-line, e.g.
971 CFLAGS="-Os -ffunction-sections -fdata-sections \
972 -fno-unwind-tables -fno-asynchronous-unwind-tables" \
973 LDFLAGS="-Wl,-s -Wl,-Bsymbolic -Wl,--gc-sections"
975 Be sure also to strip debugging symbols from your binaries after
976 compiling using 'strip' (or the appropriate variant if cross-compiling).
977 If space is really tight, you may be able to remove some unneeded
978 sections of the shared library using the -R option to objcopy (e.g. the
981 Using these techniques it is possible to create a basic HTTP-only shared
982 libcurl library for i386 Linux platforms that is only 114 KiB in size, and
983 an FTP-only library that is 115 KiB in size (as of libcurl version 7.35.0,
986 You may find that statically linking libcurl to your application will
987 result in a lower total size than dynamically linking.
989 Note that the curl test harness can detect the use of some, but not all, of
990 the --disable statements suggested above. Use will cause tests relying on
991 those features to fail. The test harness can be manually forced to skip
992 the relevant tests by specifying certain key words on the runtests.pl
993 command line. Following is a list of appropriate key words:
995 --disable-cookies !cookies
996 --disable-manual !--manual
997 --disable-proxy !HTTP\ proxy !proxytunnel !SOCKS4 !SOCKS5
1002 This is a probably incomplete list of known hardware and operating systems
1003 that curl has been compiled for. If you know a system curl compiles and
1004 runs on, that isn't listed, please let us know!
1007 - Alpha Digital UNIX v3.2
1008 - Alpha FreeBSD 4.1, 4.5
1009 - Alpha Linux 2.2, 2.4
1010 - Alpha NetBSD 1.5.2
1012 - Alpha OpenVMS V7.1-1H2
1013 - Alpha Tru64 v5.0 5.1
1015 - ARM Android 1.5, 2.1, 2.3, 3.2, 4.x
1020 - HP-PA HP-UX 9.X 10.X 11.X
1023 - MicroBlaze uClinux
1024 - MIPS IRIX 6.2, 6.5
1027 - Pocket PC/Win CE 3.0
1028 - Power AIX 3.2.5, 4.2, 4.3.1, 4.3.2, 5.1, 5.2
1029 - PowerPC Darwin 1.0
1038 - Sparc Solaris 2.4, 2.5, 2.5.1, 2.6, 7, 8, 9, 10
1040 - StrongARM (and other ARM) RISC OS 3.1, 4.02
1041 - StrongARM/ARM7/ARM9 Linux 2.4, 2.6
1042 - StrongARM NetBSD 1.4.1
1043 - Symbian OS (P.I.P.S.) 9.x
1054 - i386 Linux 1.3, 2.0, 2.2, 2.3, 2.4, 2.6
1058 - i386 Novell NetWare
1064 - i386 Windows 95, 98, ME, NT, 2000, XP, 2003
1065 - i486 ncr-sysv4.3.03 (NCR MP-RAS)
1071 - m88k dg-dgux5.4R3.00
1074 - XScale/PXA250 Linux 2.4
1080 axTLS http://axtls.sourceforge.net/
1081 c-ares http://c-ares.haxx.se/
1082 GNU GSS http://www.gnu.org/software/gss/
1083 GnuTLS http://www.gnu.org/software/gnutls/
1084 Heimdal http://www.pdc.kth.se/heimdal/
1085 libidn http://www.gnu.org/software/libidn/
1086 libmetalink https://launchpad.net/libmetalink/
1087 libssh2 http://www.libssh2.org/
1088 MIT Kerberos http://web.mit.edu/kerberos/www/dist/
1089 NSS http://www.mozilla.org/projects/security/pki/nss/
1090 OpenLDAP http://www.openldap.org/
1091 OpenSSL http://www.openssl.org/
1092 PolarSSL http://polarssl.org/
1093 yassl http://www.yassl.com/
1094 Zlib http://www.zlib.net/
1096 MingW http://www.mingw.org/
1097 MinGW-w64 http://mingw-w64.sourceforge.net/
1098 OpenWatcom http://www.openwatcom.org/