#17 Themed exe with x86_64-w64-windres

closed
nobody
5
2009-10-16
2009-10-16
No

Hi.
I just compiled my tool with ming64.
with standard mingw32, there is no problem.
But when I use mingw64 it's problem for me.
It build main ICON but not make menus "themed"

Discussion

  • Death Knight®

    Death Knight® - 2009-10-16

    mingw32 windres

     
    Attachments
  • Death Knight®

    Death Knight® - 2009-10-16

    mingw64 windres

     
    Attachments
  • Death Knight®

    Death Knight® - 2009-10-16

    I used wxWidgets 2.9.0 with
    "../configure --enable-static --enable-unicode --disable-shared --enable-monolithic --host=x86_64-w64-mingw32 --build=i686-linux"
    configuretion.
    Also resulting exe is not executing. Thats windres generated problem. I think its generate for 32 bit architecture.
    Default wx-config --rescomp returns
    "x86_64-w64-mingw32-windres --include-dir /wxWidgets-2.9.0/include --define __WIN32__ --define __WIN95__ --define __GNUWIN32__"
    and makes exe corrupt.
    I recompile object file with using
    "x86_64-w64-mingw32-windres --include-dir /wxWidgets-2.9.0/include" only and after using "--define __WIN64__" and "--define __GNUWIN64__" flags but doesn't help.
    Resulting screenshot of exe is attached. It's could be half ming64 and half wxWidgest bug. But I think needed to solved.

    Thanks

     
  • Death Knight®

    Death Knight® - 2009-10-16
    • labels: --> Build 3rd party app
     
  • Death Knight®

    Death Knight® - 2009-10-16

    Fixed via using "--define WX_CPU_AMD64"

     
  • Death Knight®

    Death Knight® - 2009-10-16
    • status: open --> closed
     
  • NightStrike

    NightStrike - 2009-10-16

    Glad we could help! :) :) :)

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks