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

[Jonathan Greig]

This discussion started on the Qt mailing lists, but Mark suggested I ask here.

1) I'm wanting to setup a cross-compiler targeting 32-bit Windows from a Travis-CI 64-bit Linux environment. If I can reliably do this on my home machine, getting it to work in Travis-CI should be fairly easy. Since MXE is on GitHub, why isn't MXE isn't using Travis-CI?

2) I'm wanting a shared Qt5 library. Mark said shared library support was added recently. I looked here: https://github.com/mxe/mxe/blob/master/src/qtbase.mk and it seems that it is hardcoded to build Qt5 statically. Is it possible to build a shared Qt5 library yet?

3) Is there any estimated timeframe on when shared library support will hit the stable branch? I've been burnt several times in the past using master as noted below.

Jonathan

On Thu, Mar 6, 2014 at 7:26 PM, Mark Brand <address@hidden> wrote:

On 03/07/2014 12:40 AM, Jonathan Greig wrote:

I've used MXE several times in the past even before it was called MXE. I must have really bad luck, because any time I have ever used the master ends up in disaster. Mark, Since I know your involved with MXE more than most, is there an estimate on when the shared lib support will make it into the stable branch or is it too early to tell?

I noticed it was subsumed into the win32-g++ mkspec but the note suggests you need to build Qt5 from source, which I would like to avoid if possible because that lengthens the build process considerably. I'm on Kubuntu 13.10 and using the .deb packages(which I'm assuming are bootstrapped from Debian) previously tried using -spec win32-g++ without much luck. If I can get it working reliably on my machine, there's little reason why it wouldn't work on Travis-CI. Are the Debian packages not configured for cross-compiling?

MXE builds everything from source, but it's painless and fast. It will build all packages from gcc through all the Qt 5 modules during your coffee break.

It's probably best to ask on the MXE list about shared libraries and the stable branch. Many people use the master branch successfully, at least as a base for their own private fork.

I have haven't tried it any other way than with MXE for a long time so I can't say much about Travis-CI or the Debian packages. If you look at how the Qt configure script is invoked in MXE, that might give you some ideas.