Re: Extend libtool dll namespaces for mingw-w64

[Roumen Petrov]

Matěj Týč wrote:
> On Tue, 2010-01-26 at 23:26 +0800, JonY wrote:
> ...
> > I suggest the following naming scheme.
> >
> > mingw.org:      lib<name>-<major>.dll (unchanged)
> > Cygwin:         cyg<name>-<major>.dll (unchanged)
> > mingw-w64(64):  lib64<name>-<major>.dll
> > mingw-w64(32):  lib32<name>-<major>.dll
> >
> > libtool should also check if GCC "-m32" or "-m64" is used, and select
> > the proper namespace accordingly (mingw-w64 GCC can do multilib).
> >
> > Comments?
>
> AFAIK if you use automake, you have to have something like the following
> line in Makefile.am:
> lib_LTLIBRARIES = libfoo.la
> This means that the 'lib' prefix doesn't actually come from mingw, but
> from your automake setup, right?

No http://lists.gnu.org/archive/html/libtool/2007-07/msg00064.html

[SNIP]
> This should allow some library name modifications as proposed here.
> What I would like to see one day though is that I am able to produce a
> library named foo.dll instead of libfoo.dll without any workarounds.
> That lib prefix tends to scare Windows users, but I am sure you know
> that too :-) I was not aware of possible conflicts that were mentioned
> here though.


I'm not sure that idea for lib{64|32} is so good.
As I know for 32 bit process  64 bit microsoft windows os will return 
%WINDOWS%\SysWOW64 as system folder. For 64 bit process it is 
%WINDOWS%\System32 (no comment on design), "Program Files" for 64-bit 
and "Program Files (x86)"(?) for 32-bit (more on MSDN).

I'm not sure that libtool has to know how lets call it "redirection" work.

Roumen