On 7 Mar 2014, at 23:43, Jonathan Greig <address@hidden> wrote:
Mark,
I tried again after manually deleting the files that "make distclean" takes care of and tried again but it still doesn't work. So next I compiled the qt5 mdi example(just because our app is mdi based but implemented differently) and the mdi.exe works fine thru wine as well as in my VM. So I think you might be right, something either in our sources or possibly our .pro file isn't exposed anywhere else but when using MXE. I'll dive into the problem deeper, I'll do a fresh clone of our code and start systematically dismembering it until it works so I can pinpoint the problem. I'll post what it is when I find it since it is quite mysterious.
Coming to the conversation late, but I’ll second Mark’s earlier comment about not seeing issues like that, and can confirm that the steps will lead to failing executable. Qt on master is generally very “stable”.
After that, then I'll try a shared MXE build.
The shared build does work (opens up with a blank “Tip of the Day”), though these are still early and undocumented. You’ll need to use the *-w64-* targets (there’s an issue with gnutls on i686-pc-mingw32.shared that is very hard to resolve):
make qt5 MXE_TARGETS='x86_64-w64-mingw32.shared i686-w64-mingw32.shared' -j4
Note that this will also build qtwebkit so you may want to specify the submodules you want instead of the full qt5.
Cheers,
Tony
