Re: [Mingw-cross-env-list] Qt5 Shared / Travis-CI

[Jonathan Greig]

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. After that, then I'll try a shared MXE build.

The CONFIG+=deploy is just something we added to our .pro files that ensures a release build is made rather than a debug one and has the benefit of being shorter to type. It's also something we will be integrating into our nightly build system.

Thanks for the explanation about JOBS vs -j4.

Cheers,

Jonathan

On Fri, Mar 7, 2014 at 6:08 AM, Mark Brand <address@hidden> wrote:

On 03/07/2014 11:46 AM, Jonathan Greig wrote:

Mark,

Just got done building, and I did encounter the same issue again:

Qt5 GUI app (embroidermodder2.exe) written in C++ and should work with mxe's qmake: FAIL

Command line converter app (libembroidery-convert.exe) which is written in C89 and does not rely on Qt, but I use mxe's qmake to build it: PASS

Here is exactly how I cross-compiled the executables:

cd embroidermodder2
make distclean
export PATH=/mydata/mxe/usr/bin:$PATH
/mydata/mxe/usr/i686-pc-mingw32.static/qt5/bin/qmake CONFIG+=deploy
make
[embroidermodder2.exe is successfully made but fails in windows]
cd ../libembroidery-convert
make distclean
/mydata/mxe/usr/i686-pc-mingw32.static/qt5/bin/qmake CONFIG+=deploy
make
[libembroidery-convert.exe is successfully made and actually runs on windows]

Am I missing a step or is this really a problem?

Nothing obvious to me. But I wouldn't necessarily trust "make distclean" in a situation like this. I would start fresh just to be sure. I have no experience with "deploy", but I doubt that's the culprit. You could try the other MXE_TARGETS. You might also consider whether there is something wrong in the sources that is only exposed in this particular environment. I hope somebody else will comment on this after looking at the error message in your screen shot.

I've attached pictures showing the result in my VM.

I'm not sure why you would need both JOBS=4 and -j4

-j4 allows building different packages at the same time. JOBS=4 allows parallel building within the packages.