mingw linking problem
Stefan.Leichter at camline.com
Mon Mar 5 14:51:44 CST 2007
Am Tuesday 27 February 2007 19:43 schrieb Paul Millar:
> Hi Stefan,
> On Sunday 25 February 2007 18:13, Stefan Leichter wrote:
> > This fail for some dlls at the linking, eg. comdlg32.dll misses the
> > imports
> > _IID_IContextMenu, _IID_IShellFolder, _IID_IPersistFolder2,
> > _IID_IShellBrowser, _IID_ICommDlgBrowser, _IID_IShellView,
> These are part of the MinGW's W32api v3.8. I don't know how long they've
> been in W32api, so you may need to upgrade to this version.
> > _SID_STopLevelBrowser
This was a stupid error in my hand edited patch
> The set of patches I have includes a definition for this GUID (as well as
> many, many others). The complete set of patches (against w32api v3.8) is
> available from:
> Using a MinGW tool-chain (that has these patches) I was able to build
can you build comdlg32.dll if you have shell32.dll? If i run make clean in
shell32 directory comdlg32.dll builds fine for me. If shell32 is there from a
previous build, comdlg32.dll fails for me with the problems described above.
In short it can be said this way:
comdlg32.dll needs to be build shell32.dll and libuuid.a from mingw or from
wine, but the "two files" must be used from one source either wine or mingw.
It is not possible to use one file from wine and one file from mingw.
But this happend for me currently
When i build wine with mingw the Makefile uses shell32.dll from wine and
libuuid from mingw. This gives me the uinresolved symbols.
More information about the wine-devel