From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-02-10 06:10:39
On Friday 10 February 2006 13:58, Mark Evans wrote:
> $(OS) is CYGWIN but the /target/ OS is HP NonStop.
> A .so library suffix is generated by my cross-toolset for shared libs.
> FWIW it registers .so as its suffix for SHARED_LIB. The original problem
> was provoked by a prebuilt shared library that had no suffix at all.
> Am I stuck with using <search> instead of <file> ?
You can just add '.so' in the list of shared library suffixes, in
> If I were to constrain all my "imported" / prebuilt libraries to have
> the .so suffix, would there be a way to trick bb2 into accepting such
> <file>s in a cross-development scenario like this?
For now, modifing lib.jam seems like the only option.
> I'm foggy on why bb2 doesn't just tag such library <file>s as <prebuilt>
> and be happy if the file exists.
And, what will Boost.Build do with such file? If it has no idea what's the
type of the file, it has no idea if it can be linked into an executable.
Well, I can change generators code so that targets with unknown type are
silently consumed and passed on to the tool (like linker), but that seems
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk