aboutsummaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2018-06-25 15:01:12 +0200
committerDaniel Stenberg <daniel@haxx.se>2018-06-25 15:01:12 +0200
commit13120f28b309e6276690383b2daa977ec9aa99c8 (patch)
tree40ad881fbff56bba856bad806dcf9882a8acc002 /include
parent75e8dc05081132a9f825f8f40991c7f2c8a8e445 (diff)
include/README: remove "hacking" advice, not the right place
Diffstat (limited to 'include')
-rw-r--r--include/README19
1 files changed, 2 insertions, 17 deletions
diff --git a/include/README b/include/README
index c2589ec8c..091ef76d1 100644
--- a/include/README
+++ b/include/README
@@ -14,20 +14,5 @@ of environment. You must include files from here using...
... style and point the compiler's include path to the directory holding the
curl subdirectory. It makes it more likely to survive future modifications.
-NOTE FOR LIBCURL HACKERS
-
-* If you check out from git on a non-configure platform, you must run the
- appropriate buildconf* script to set up files before being able of compiling
- the library.
-
-* We cannot assume anything else but very basic compiler features being
- present. While libcurl requires an ANSI C compiler to build, some of the
- earlier ANSI compilers clearly can't deal with some preprocessor operators.
-
-* Newlines must remain unix-style for older compilers' sake.
-
-* Comments must be written in the old-style /* unnested C-fashion */
-
-To figure out how to do good and portable checks for features, operating
-systems or specific hardwarare, a very good resource is Bjorn Reese's
-collection at https://sourceforge.net/p/predef/wiki/
+The public curl include files can be shared freely between different platforms
+and different architectures.