[Scons-users] Building versioned shared library fails when using MinGW

[William Blevins]

Ray,

I don't know the exact problem, but 2.4.1 contained a major update to how
versioned shared libraries were built.

I know there is a bug fix patch currently unreleased, but I assume your
issue is different. Probably an issue with platform setup. Here is the
CHANGES.TXT notes:

  From Paweł Tomulik:
    - Fixed the issue with LDMODULEVERSIONFLAGS reported by Tim Jennes
      (https://pairlist4.pair.net/pipermail/scons-users/2016-May/004893.html
).
      An error was causing “-Wl,Bsymbolic” being added to linker's
command-line
      even when there was no specified value in LDMODULEVERSION and thus no
      need for the flags to be specified.
    - Added LoadableModule to the list of global functions
(DefaultEnvironment
      builders).

V/R,
William

On Sat, Nov 19, 2016 at 5:59 PM, Ray Speth <speth at darkmatter.mit.edu> wrote:

> Hi,
>
> I have encountered an apparent bug when trying to build versioned shared
> libraries with MinGW. A minimal SConstruct:
>
>     env = Environment(tools=['mingw'])
>     lib = env.SharedLibrary('foo', ['foo.cpp'], SHLIBVERSION='2.4')
>     env.AlwaysBuild(lib)
>
> generates the following output:
>
>     scons: Reading SConscript files ...
>     scons: *** A shared library should have exactly one target with the
> suffix: .dll
>     File "path\to\SConstruct", line 2, in <module>
>
> I have tested this with SCons 2.4.1, 2.5.0, and 2.5.1, with the same
> results.
>
> Regards,
> Ray
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20161119/911faf04/attachment.html>