From: David Abrahams (david.abrahams_at_[hidden])
Date: 2001-11-01 19:29:08
----- Original Message -----
From: "Jeremy Siek" <jsiek_at_[hidden]>
> But this is horrible... how can I portably specify the path? It may differ
> from machine to machine.
It's not that bad; it's just an issue that needs addressing, and it should
be easy enough to fix ;-)
My problem so far is that I don't have a clear picture of what people
want/need to do with prebuilt libraries in a cross-platform build system.
Let's discuss it. Once I understand it, getting you what you want should be
Are you trying to link to a library like libxxx.a? If so, I guess that the
system will look in your LD_LIBRARY_PATH, and we need to somehow get -lxxx
onto the command-line.
What is the analogue for non-unix systems? My impression is that only unix
does the lib + name + .a trick. Is there any point in worrying about the
non-uniformity? Perhaps the libraries are always named differently on
different platforms anyway?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk