From: Kevin Wheatley (hxpro_at_[hidden])
Date: 2005-12-21 12:11:08
I'm trying to port a make file over to BBv2 and I was wondering about
the following situation:
foo.lib -> filteringcommand -> bar.lib
i.e. I'd like to take a library I've just built and then run a few
commands on it transforming it into a different output library.
As an example, run 'lmstrip' which changes the names of some symbols
exported by the library.
Am I right in assuming this is best handled using a 'make' rule?
make bar.lib : foo.lib : do-lmstrip ;
lmstrip command here...
I also want to version some symbols, looking at the docs it appears I
can do this by extending the link command (of gcc) to understand a
feature <export-symbols> or some such. Does anybody else need this
and whats a good name to use?
If I want to do this it must only pass the option
--version-script=filename if the file exists otherwise you get errors
- whats the appropriate way of handling this in an action?
It would also be useful to be able to tweak the link command line to
insert things like -Bsymbolic at the required place, is there an
option to insert such things before a target is used in a link line?
or should I just resort to similar make rules tfor such fine control?
-- | Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this | | Senior Technology | My employer for certain | | And Network Systems Architect | Not even myself |
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