From: Rene Rivera (grafik.list_at_[hidden])
Date: 2004-01-05 08:59:06
Toon Knapen wrote:
> Sean Perry from IBM explained me a better way to build the shared
> libraries (instead of using Python). Only minor modifications are needed
> to make it work. In short it comes down to:
> 1) removing the '.imp' from SUFDLL in allyourbase.jam
> 2) removeing the 'Aix-Implib-action'
> 3) adding the '-G' flag to the "xlC-Link-action"
> The main thing is that now we need to make a distinction between linking
> a shared library and an executable (the 'xlC-Link-action' is used for
> both though) because the '-G' flag is needed for shared libraries but
> not for executables. So I could define a new action e.g.
> 'xlC-Link-so-action' that could be used for linking .so's or I could add
> a variable which is equal to '-G' or empty and which can be used on the
> link-line. Which of these solutions would be preferable and is it OK to
> commit these changes ?
I would think adding:
flags vacpp LINKFLAGS <target-type>$(SHARED_TYPES) : -G ;
Would be easier than another separate action.
But sure if it does the same work that the Python script is doing go ahead. It
can't all that much worse than the current situation ;-)
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
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