mingw status

[Harri Porten]

On Mon, 20 Feb 2006, Christian Ehrlicher wrote:

> > Yes: you can declare a single member function to have linkage different
> > from the rest of the class. That's what we've been doing all along in
> > KJS.

Such an irony. My colleague ran into the QString/UString issue as well
today when porting our software to MinGW. I'm punished for my own mistakes
half a decade later ;(

> > It's just that the Win32 COFF PE executable format doesn't support this.
> > It's an all or nothing. ELF implements it correctly, because there is
> > only one symbol pool (the global one) and any symbol can be defined
> > anywhere, just as if the program had been statically linked.
> But ths should work:
>
> class foo {
>   KDE_EXPORT foo();
>   myFunction();
> }
>
> Then only the constructor is exported when I'm correct.

Should work indeed and we started that way but still hesitate to continue.
Not only because of the ugly "look" this will result in but because of the
maintenance problem.

The Microsoft compiler and linker has no problem with the code as it is.
Just MinGW. So I wonder if there is another alternative. Tried
--warn-unresolved-symbols but that didn't help. Will
still try --exclude-symbols although the hope is slim.

Harri.