From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-03-17 03:59:02
> Ah, I see. I can live with these includes right now.
> But I've got one other question:
> The library names for both qt and stlport are hardcoded in qt.jam and
> stlport.jam for gcc. For windows, I'd need different library names,
> e.g stlport_cygwin for cygwin-gcc, stlport_win32 for msvc and so on.
> Qt should even be mor problematic, because you've got something along
> qt312.lib for Qt-3.1.2 on windows.
> Can you give me a hint when this will be addressed ?
I don't know :-) I think that I'd need some help from you in doing it.
> Or how can I do something myself ?
The first thing to determine is how those names are computed. Do they depend
only on toolset? Or one should be able to configure them?
The first case is pretty simple. One will introduce a new rule in
'stlport.jam', which will take a list of properties and return the library
In the second case, the 'init' rule for stlport.jam should accept some
additional parameters, and the rule returning the name should use them, too.
In either case, the complexity depends on how library names are determined --
there's little Boost.Build internals to fight with :-)
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