blob: c2589ec8c401028e737e2d9f7f6a30fde68f3bcb [file] [log] [blame]
Kristian Monsen5ab50182010-05-14 18:53:44 +01001 _ _ ____ _
2 ___| | | | _ \| |
3 / __| | | | |_) | |
4 | (__| |_| | _ <| |___
5 \___|\___/|_| \_\_____|
6
7Include files for libcurl, external users.
8
9They're all placed in the curl subdirectory here for better fit in any kind
10of environment. You must include files from here using...
11
12 #include <curl/curl.h>
13
14... style and point the compiler's include path to the directory holding the
15curl subdirectory. It makes it more likely to survive future modifications.
16
17NOTE FOR LIBCURL HACKERS
18
Kristian Monsen5ab50182010-05-14 18:53:44 +010019* If you check out from git on a non-configure platform, you must run the
Elliott Hughes82be86d2017-09-20 17:00:17 -070020 appropriate buildconf* script to set up files before being able of compiling
21 the library.
Kristian Monsen5ab50182010-05-14 18:53:44 +010022
23* We cannot assume anything else but very basic compiler features being
24 present. While libcurl requires an ANSI C compiler to build, some of the
25 earlier ANSI compilers clearly can't deal with some preprocessor operators.
26
27* Newlines must remain unix-style for older compilers' sake.
28
29* Comments must be written in the old-style /* unnested C-fashion */
30
31To figure out how to do good and portable checks for features, operating
32systems or specific hardwarare, a very good resource is Bjorn Reese's
Alex Deymo486467e2017-12-19 19:04:07 +010033collection at https://sourceforge.net/p/predef/wiki/