Re: [winegcc] Include .so files when calling winebuild

[Alexandre Julliard]

Peter Berg Larsen  writes:
> Changelog:
>    Currently when compiling a program, winegcc calls winebuild
>    to solve .def references. But winegcc drops .so files,
>         so any new .def symbols in a .so causes a unresolved symbol at
>    link time. This patch adds .so files to the files to winebuild.

I'm not sure I follow you, if your .so files have been built correctly
they shouldn't contain undefined references to Windows APIs. Could you
please show an example of the situation that causes a problem?

[winegcc] Include .so files when calling winebuild

[Boaz Harrosh]

Alexandre Julliard wrote:
> I'm not sure I follow you, if your .so files have been built correctly
> they shouldn't contain undefined references to Windows APIs. Could you
> please show an example of the situation that causes a problem?

.so that are not compiled as dll or fake dll (fake dll is when the lib 
looks like a winelib dll to the wineloader, but is actually also linked 
gcc style for C++ symbols) will have problems with startup and global 
symbols and code. especially if this code calls any wine code, for 
example msvcrt.

Free life
Boaz