Loading docs/FEATURES +1 −1 Original line number Original line Diff line number Diff line Loading @@ -56,7 +56,7 @@ FTP - download - download - authentication - authentication - kerberos security - kerberos security - PORT or PASV - active/passive using PORT, EPRT, PASV or EPSV - single file size information (compare to HTTP HEAD) - single file size information (compare to HTTP HEAD) - 'type=' URL support - 'type=' URL support - dir listing - dir listing Loading docs/INSTALL +7 −13 Original line number Original line Diff line number Diff line Loading @@ -36,8 +36,7 @@ UNIX The configure script always tries to find a working SSL library unless The configure script always tries to find a working SSL library unless explicitly told not to. If you have OpenSSL installed in the default search explicitly told not to. If you have OpenSSL installed in the default search path for your compiler/linker, you don't need to do anything special. If path for your compiler/linker, you don't need to do anything special. If you have OpenSSL installed in e.g /usr/local/ssl, you can run configure you have OpenSSL installed in /usr/local/ssl, you can run configure like: like: ./configure --with-ssl ./configure --with-ssl Loading @@ -46,13 +45,13 @@ UNIX ./configure --with-ssl=/opt/OpenSSL ./configure --with-ssl=/opt/OpenSSL If you insist on forcing a build *without* SSL support, even though you may If you insist on forcing a build without SSL support, even though you may have it installed in your system, you can run configure like this: have OpenSSL installed in your system, you can run configure like this: ./configure --without-ssl ./configure --without-ssl If you have OpenSSL installed, but with the libraries in one place and the If you have OpenSSL installed, but with the libraries in one place and the header files somewhere else, you'll have to set the LDFLAGS and CPPFLAGS header files somewhere else, you have to set the LDFLAGS and CPPFLAGS environment variables prior to running configure. Something like this environment variables prior to running configure. Something like this should work: should work: Loading @@ -72,7 +71,7 @@ UNIX LIBS=-lRSAglue -lrsaref LIBS=-lRSAglue -lrsaref (as suggested by Doug Kaufman) (as suggested by Doug Kaufman) KNOWN PROBLEMS KNOWN PROBLEMS (these ones should not happen anymore) If you happen to have autoconf installed, but a version older than 2.12 If you happen to have autoconf installed, but a version older than 2.12 you will get into trouble. Then you can still build curl by issuing these you will get into trouble. Then you can still build curl by issuing these Loading Loading @@ -101,8 +100,8 @@ UNIX MORE OPTIONS MORE OPTIONS Remember, to force configure to use the standard cc compiler if both To force configure to use the standard cc compiler if both cc and gcc are cc and gcc are present, run configure like present, run configure like CC=cc ./configure CC=cc ./configure or or Loading Loading @@ -130,11 +129,6 @@ UNIX ./configure --with-krb4=/usr/athena ./configure --with-krb4=/usr/athena If your system support shared libraries, but you want to built a static version only, you can disable building the shared version by using: ./configure --disable-shared If you're a curl developer and use gcc, you might want to enable more If you're a curl developer and use gcc, you might want to enable more debug options with the --enable-debug option. debug options with the --enable-debug option. Loading docs/README.win32 +5 −12 Original line number Original line Diff line number Diff line Loading @@ -12,18 +12,11 @@ README.win32 systems. While not being the main develop target, a fair share of curl users systems. While not being the main develop target, a fair share of curl users are win32-based. are win32-based. Some documentation in this archive will be tricky to read for Windows The unix-style man pages are tricky to read on windows, so therefore are all people, as they come in unix-style man pages. You can either download a those pages also converted to HTML and those are also included in the freely available nroff binary for win32 (*pointers appriciated*), convert release archives. the files into plain-text on your neighbor's unix machine or run over to the curl web site and view them as plain HTML. The main curl.1 man page is "built-in". Use a command line similar to this The main curl.1 man page is also "built-in" in the command line tool. Use a in order to extract a separate text file: command line similar to this in order to extract a separate text file: curl -M >manual.txt curl -M >manual.txt Download all the libcurl man pages in HTML format using the link on the bottom of this page: http://curl.haxx.se/libcurl/c/ Loading
docs/FEATURES +1 −1 Original line number Original line Diff line number Diff line Loading @@ -56,7 +56,7 @@ FTP - download - download - authentication - authentication - kerberos security - kerberos security - PORT or PASV - active/passive using PORT, EPRT, PASV or EPSV - single file size information (compare to HTTP HEAD) - single file size information (compare to HTTP HEAD) - 'type=' URL support - 'type=' URL support - dir listing - dir listing Loading
docs/INSTALL +7 −13 Original line number Original line Diff line number Diff line Loading @@ -36,8 +36,7 @@ UNIX The configure script always tries to find a working SSL library unless The configure script always tries to find a working SSL library unless explicitly told not to. If you have OpenSSL installed in the default search explicitly told not to. If you have OpenSSL installed in the default search path for your compiler/linker, you don't need to do anything special. If path for your compiler/linker, you don't need to do anything special. If you have OpenSSL installed in e.g /usr/local/ssl, you can run configure you have OpenSSL installed in /usr/local/ssl, you can run configure like: like: ./configure --with-ssl ./configure --with-ssl Loading @@ -46,13 +45,13 @@ UNIX ./configure --with-ssl=/opt/OpenSSL ./configure --with-ssl=/opt/OpenSSL If you insist on forcing a build *without* SSL support, even though you may If you insist on forcing a build without SSL support, even though you may have it installed in your system, you can run configure like this: have OpenSSL installed in your system, you can run configure like this: ./configure --without-ssl ./configure --without-ssl If you have OpenSSL installed, but with the libraries in one place and the If you have OpenSSL installed, but with the libraries in one place and the header files somewhere else, you'll have to set the LDFLAGS and CPPFLAGS header files somewhere else, you have to set the LDFLAGS and CPPFLAGS environment variables prior to running configure. Something like this environment variables prior to running configure. Something like this should work: should work: Loading @@ -72,7 +71,7 @@ UNIX LIBS=-lRSAglue -lrsaref LIBS=-lRSAglue -lrsaref (as suggested by Doug Kaufman) (as suggested by Doug Kaufman) KNOWN PROBLEMS KNOWN PROBLEMS (these ones should not happen anymore) If you happen to have autoconf installed, but a version older than 2.12 If you happen to have autoconf installed, but a version older than 2.12 you will get into trouble. Then you can still build curl by issuing these you will get into trouble. Then you can still build curl by issuing these Loading Loading @@ -101,8 +100,8 @@ UNIX MORE OPTIONS MORE OPTIONS Remember, to force configure to use the standard cc compiler if both To force configure to use the standard cc compiler if both cc and gcc are cc and gcc are present, run configure like present, run configure like CC=cc ./configure CC=cc ./configure or or Loading Loading @@ -130,11 +129,6 @@ UNIX ./configure --with-krb4=/usr/athena ./configure --with-krb4=/usr/athena If your system support shared libraries, but you want to built a static version only, you can disable building the shared version by using: ./configure --disable-shared If you're a curl developer and use gcc, you might want to enable more If you're a curl developer and use gcc, you might want to enable more debug options with the --enable-debug option. debug options with the --enable-debug option. Loading
docs/README.win32 +5 −12 Original line number Original line Diff line number Diff line Loading @@ -12,18 +12,11 @@ README.win32 systems. While not being the main develop target, a fair share of curl users systems. While not being the main develop target, a fair share of curl users are win32-based. are win32-based. Some documentation in this archive will be tricky to read for Windows The unix-style man pages are tricky to read on windows, so therefore are all people, as they come in unix-style man pages. You can either download a those pages also converted to HTML and those are also included in the freely available nroff binary for win32 (*pointers appriciated*), convert release archives. the files into plain-text on your neighbor's unix machine or run over to the curl web site and view them as plain HTML. The main curl.1 man page is "built-in". Use a command line similar to this The main curl.1 man page is also "built-in" in the command line tool. Use a in order to extract a separate text file: command line similar to this in order to extract a separate text file: curl -M >manual.txt curl -M >manual.txt Download all the libcurl man pages in HTML format using the link on the bottom of this page: http://curl.haxx.se/libcurl/c/