Daniel Stenberg 67ff8e3ea3 valgrind errors occur too often when 'make test' is used. It is because too
many third-party libs and tools have problems. When curl is built without
--disable-shared, the testing is done with a front-end script which makes the
valgrind testing include (ba)sh as well and that often causes valgrind
errors. Either we improve the valgrind error scanner a lot to better identify
(lib)curl errors only, or we disable valgrind checking by default
2005-02-05 10:25:20 +00:00
..
2005-02-04 23:53:12 +00:00
2002-10-14 07:47:40 +00:00
2005-01-26 11:53:49 +00:00
2003-08-18 15:24:46 +00:00
2004-08-13 11:53:33 +00:00
2005-01-25 12:06:12 +00:00
FAQ
2005-01-04 16:16:03 +00:00
2004-08-12 14:08:46 +00:00
2004-08-13 11:53:33 +00:00
2002-02-27 12:40:01 +00:00
2004-12-10 21:56:35 +00:00
2005-01-29 13:54:15 +00:00

                                  _   _ ____  _     
                              ___| | | |  _ \| |    
                             / __| | | | |_) | |    
                            | (__| |_| |  _ <| |___ 
                             \___|\___/|_| \_\_____|

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