On Thu, Sep 2, 2010 at 8:47 PM, Felix Wolfheimer <[email protected]> wrote:
> Hi Bidski,
>
> thanks for your help! The workaround you proposed fixed the issue (in
> fact I've duplicated the libwctl3d32 such that I have now both
> libwctl3d32 and libctl3d32). After this modification wxWidgets-2.9.2
> builds without problems.
Couldn't find 2.9.2 t wxWidgets.org so I looked at 2.9.1
> I've checked the configure.in of wxWidgets and it contains the
> following:
>
> *snip*
> dnl --- FIXME: This is still a somewhat random list of libs,
> dnl --- some of them should probably be included conditionally.
> case "${host}" in
> x86_64-*-mingw32* )
> dnl --- For mingw-w64 lctl3d32's name has changed
> LIBS="$LIBS -lwinspool -lwinmm -lshell32 -lcomctl32
> -lcomdlg32 -lwctl3d32 -ladvapi32 -lwsock32 -lgdi32"
>
> dnl we need to define this to embed the manifest for correct
> dnl platform from wx/msw/wx.rc (this is not needed for x86
> which is
> dnl the default in wx/msw/rcdefs.h)
> WINDRES_CPU_DEFINE="--define WX_CPU_AMD64"
> ;;
> * )
> LIBS="$LIBS -lwinspool -lwinmm -lshell32 -lcomctl32
> -lcomdlg32 -lctl3d32 -ladvapi32 -lwsock32 -lgdi32"
> *snip*
>
> Seems that they have noticed that the lib has been renamed but the
> x86_64-*-mingw32* does not catch all cases where the renaming occurs.
> I'll drop the wxWidgets guys a note about this.
>
> BTW: Is there any reason why this lib and probably some of the others
> have been renamed (libwfoo instead of libfoo)?
Some notes and questions here:
# Those extra w* stuff were experimental, not to be used by end
users.
# Win64 does _not_ provide a ctl3d32.dll. It is an ancient dll
only for x86.
# Look at the msdn pages, that functions exported from ctl3d32.dll
have heither a header nor an import library and they should be used
by way of LoadLibrary and GetProcAddress functions.
# wxWidgets do not seem to use any of the exported functions from
ctl3d32.dll: none of Ctl3dGetVer, Ctl3dSubclassDlg, Ctl3dSubclassCtl,
Ctl3dCtlColor, Ctl3dEnabled, Ctl3dColorChange, BtnWndProc3d,
EditWndProc3d, ListWndProc3d, ComboWndProc3d, StaticWndProc3d,
Ctl3dRegister, Ctl3dUnregister, Ctl3dAutoSubclass, Ctl3dDlgProc,
Ctl3dCtlColorEx, Ctl3dSetStyle, Ctl3dDlgFramePaint, Ctl3dSubclassDlgEx,
Ctl3dWinIniChange, Ctl3dIsAutoSubclass, Ctl3dUnAutoSubclass,
Ctl3dSubclassCtlEx, Ctl3dUnsubclassCtl, Ctl3dAutoSubclassEx.
Therefore why is it trying to link against ctl3d32.dll ?
# If you edit the wxWidgets' configury and remove the ctl3d32 linkage,
does it link and run correctly?
>
> Anyway thanks again for your help!
>
> Best regards
>
> Felix
--
Ozkan
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
