Re: Surprising change in behaviour of createSharedLibBuilder

Steve,

Any API not in the manpage is not subject to depreciation process.

As far as this specific change, it was necessary to introduce an
intermediary variable for  the suffix to properly generate versioned shared
library file names and symlinks.
Not sure why you're calling createSharedLibBuilder() directly?
Perhaps if you can explain why, we can suggest how you should handle this
change.

-Bill

On Mon, Sep 20, 2021 at 1:55 AM Steve Hill (Wireless) via Scons-users <
[email protected]> wrote:

> Hi,
>
>
>
> I’ve just started the process of upgrading from SCons 3.1.2 to 4.2.0 and
> some of our Tools have been broken by a change that I find surprising.
>
>
>
> Where we define a ShLib builder, we define $SHLIBPREFIX and $SHLIBSUFFIX,
> amongst other things, before calling createSharedLibBuilder(env).
>
>
>
> Moving to 4.2.0, this resulted in the prefix still being honoured, while
> the suffix was not. By default, the builder now takes $SHLIBPREFIX and
> $_SHLIBSUFFIX. Could someone explain the reason for the new asymmetry?
>
>
>
> Is the preferred solution to add the optional argument (SCons.Tool.createSharedLibBuilder(env,
> "$SHLIBSUFFIX")) or to change our Tools to define $_SHLIBSUFFIX instead
> of $SHLIBSUFFIX?
>
>
>
> Thanks,
>
>
>
> S.
> _______________________________________________
> Scons-users mailing list
> [email protected]
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>

_______________________________________________
Scons-users mailing list
[email protected]
https://pairlist4.pair.net/mailman/listinfo/scons-users