aboutsummaryrefslogtreecommitdiff
path: root/docs/FAQ
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2016-03-18 08:14:05 +0100
committerDaniel Stenberg <daniel@haxx.se>2016-03-18 08:14:05 +0100
commit9c2cbc104de97c566dc94c6c394a13cb5e6f465e (patch)
tree4e4e8846d1b1b4ea1fdc62b2a154fa43459cfe4c /docs/FAQ
parentd816e8cf52ff031d3af97a7fd93c1886bfda76e4 (diff)
FAQ: 2.5 Install libcurl for both 32bit and 64bit?
Diffstat (limited to 'docs/FAQ')
-rw-r--r--docs/FAQ27
1 files changed, 27 insertions, 0 deletions
diff --git a/docs/FAQ b/docs/FAQ
index b3035eea5..860815341 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -30,6 +30,7 @@ FAQ
2.2 Does curl work/build with other SSL libraries?
2.3 Where can I find a copy of LIBEAY32.DLL?
2.4 Does curl support SOCKS (RFC 1928) ?
+ 2.5 Install libcurl for both 32bit and 64bit?
3. Usage Problems
3.1 curl: (1) SSL is disabled, https: not supported
@@ -464,6 +465,32 @@ FAQ
Yes, SOCKS 4 and 5 are supported.
+ 2.5 Install libcurl for both 32bit and 64bit?
+
+ In curl's configure procedure one of the regular include files get created
+ with platform specific information. The file 'curl/curlbuild.h' in the
+ installed libcurl file tree is therefore somewhat tied to that particular
+ platform.
+
+ To allow applications to get built for either 32bit or 64bit you need to
+ install libcurl headers for both setups and unfortunately curl doesn't do
+ this automatically.
+
+ A commonly used procedure is this:
+
+ $ ./configure [32bit platform]
+ $ mv curl/curlbuild.h curl/curlbuild-32bit.h
+ $ ./configure [64bit platform]
+ $ mv curl/curlbuild.h curl/curlbuild-64bit.h
+
+ Then you make a toplevel curl/curlbuild.h replacement that only does this:
+
+ #ifdef IS_32BIT
+ #include "curlbuild-32bit.h"
+ else
+ #include "curlbuild-64bit.h"
+ #endif
+
3. Usage problems