52e3c60c86
I've developed a script I call symbol-scan.pl that scans the curl.h and multi.h header files and compare the symbols it finds in there with the symbols symbols-in-versions documents and outputs a report on the differences. Using this I've dug through the history to fill up symbols-in-versions with all the symbols my script found mismatches for. I will commit symbol-scan.pl separatly and think of a way to put it to use in the build/tests so that we from now on will get this in-sync check automatically.
_ _ ____ _
___| | | | _ \| |
/ __| | | | |_) | |
| (__| |_| | _ <| |___
\___|\___/|_| \_\_____|
README.win32
Read the README file first.
Curl has been compiled, built and run on all sorts of Windows and win32
systems. While not being the main develop target, a fair share of curl users
are win32-based.
The unix-style man pages are tricky to read on windows, so therefore are all
those pages converted to HTML as well as pdf, and included in the release
archives.
The main curl.1 man page is also "built-in" in the command line tool. Use a
command line similar to this in order to extract a separate text file:
curl -M >manual.txt
Read the INSTALL file for instructions how to compile curl self.