Re: mingw woes

[Andrew Johnson <anj@aps.anl.gov>]

Hi Mark,

On 08/25/2016 08:22 AM, Mark Rivers wrote:
> However, for mingw this is not true, winmm must be explicitly linked
> with.

> corvette:base-3.15.4/configure/os>diff
> CONFIG.linux-x86.win32-x86-mingw.orig
> CONFIG.linux-x86.win32-x86-mingw
> 23,24c23,24
> < # Link with winsock2
> < OP_SYS_LDLIBS = -lws2_32
> ---
>> # Link with winsock2 and mm
>> OP_SYS_LDLIBS = -lws2_32 -lwinmm
> 
> I think this would be a good thing to add to EPICS base.

Agreed. Some other Windows target builds have apparently been linking
against the winmm library for quite a long time, along with a few other
libraries that we are not currently linking against on -mingw targets.
From the 3.14 branch:

> tux% grep -i winmm *
> CONFIG.Common.win32-x86-cygwin:OP_SYS_LDLIBS = -lws2_32 -ladvapi32 -luser32 -lkernel32 -lwinmm
> CONFIG.win32-x86-borland.win32-x86-borland:LDLIBS = ws2_32.lib advapi32.lib user32.lib kernel32.lib winmm.lib
> CONFIG.win32-x86.win32-x86:STATIC_LDLIBS_YES=ws2_32.lib advapi32.lib user32.lib kernel32.lib winmm.lib

Ignoring the now-obsolete -borland target, it looks like the list from
the (also now obsolete) win32-x86-cygwin target is comprehensive and
matches the list used for x86-win32-static builds, so I'll commit a
change to use that one. The change is needed in a couple of places in
3.14, plus one more in 3.15.

It's interesting that for the MS compilers we only have to explicitly
mention these system libraries when doing static builds.

- Andrew

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon