Yang Tse wrote:
> If you are certainly decided to have two binary libcurl libraries
> available for development on the same machine...

Thanks for the information. For the record, though, there's no
"decision" involved. On every platform I'm aware of, 32-bit code and
64-bit code inhabit parallel universes; there's no way for them to
interact at link time. Thus, on a platform which supports 64-bit, it's
necessary to build for both 32- and 64-bit.

> One possibility, probably the one that will make you suffer less in
> the long run, is to install each set of curl header files on its own
> include subdirectory. For example install the 32-bit configured
> headers in "/usr/local/include/curl/*.h" and the 64-bit configured
> headers in "/usr/local/include64/curl/*.h".

I think it's worth emphasizing a point originally made by Tor Arntsen
elsewhere in this thread: system vendors have _not_ gone with the
separate-headers strategy and have been able to make it work. This can
be seen by the fact that though splits like /usr/lib and /usr/lib/64 are
ubiquitous in 64-bit systems, there's no such thing as /usr/include/64.
So in this sense curl really is departing from long-established norms
and makes me wonder "what makes curl different from all other software"?

MB
Received on 2008-09-06