Re: [jamboost] Boost.Build, legacy changes...

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-01-28 12:20:41

----- Original Message -----
From: "Rene Rivera" <grafik666_at_[hidden]>

> I've finished integrating all the local changes I had made to the legacy
> Boost.Build, still only local to my machine.
>
> The changes include:
>
> * Jamfiles are only included once.
>
> * Addition of "stage" rule to copy and rename targets to a stage
directory.
>
> * Addition of <dll>* as source dependencies. But for this the following
> change is needed...
>
> * Changed the target name of DLLs to be $(PREDLL)<target name>$(SUFDLL).
On
> Windows I've set PREDLL to "", and to "lib" everywhere else.

Consider doing this for static libs as well; that's generally how they're
named on unix, isn't it?

> * Locally changed "libs/regex/build/Jamfile",
"libs/thread/build/Jamfile",
> and "libs/python/build/Jamfile" to account for the DLL name change.
>
> Before I check these changes in question is... Are there any problems that
the
> name change of the DLL might cause?

python.jam uses PYD targets which are mostly derived from DLL targets. You
should check to make sure there are no bad interactions.

Also, in the existing system if you've already supplied a suffix for the
target you get no modification, so:

dll foobar.nonstandard-suffix : .... ;

will build a shared lib called foobar.nonstandard-suffix, not
foobar.nonstandard-suffix.so, libfoobar.nonstandard-suffix.so, libfoobar.so,
etc.

Consider whether that needs to be preserved.

It's currently used by boost only to build dlls and static libs with the
same base name, which is very clumsy at the moment since the user has to use
$(SUFDLL) explicitly.

-Dave