Re: [qmc2-devel] New QT 4.8 paths cause MacOS build issues

[R. R. <ren...@ba...>]

On Monday 07 May 2012 16:50:42 R. Reucher wrote:
> On Monday 07 May 2012 09:24:33 R. Reucher wrote:
> > Hmmm, Nokia only published a 64-bit binary package of Qt 4.8.1 for Mac OS
> > X, but I need it in 32-bits... I'm now trying to build it myself, but
> > this will take quite some time on my Mac OS X dev-system :(...
> > 
> > @David: do you probably have a suitable Qt 4.8.1 build for me I could use
> > instead?
> 
> Nevermind, it meanwhile built cleanly :).
> 
> You can basically build it in two steps with the current Makefile (NOT
> using xcodebuild!):
> 
> make configure
> make [EMU=...]
> 
> "make install" still doesn't work, I'm working on the Makefile...
> 
> I'm actually trying to get rid of xcodebuild completely in case of Qt 4.8+,
> which would then also fix the issue with XCode 4 (which will then no longer
> be used).
> 
> Let's see :).
I think I have a clean workaround for this now in SVN r3771: when Qt 4.8+ is 
used, the build is now basically done in the exact same way as on Linux/UNIX.

So when *Qt 4.8.0 or above* is used, you can now just do something like this 
to fully build QMC2:

$ make [-j5] EMU=SDLMAME
$ sudo make install EMU=SDLMAME
$ sudo make distclean EMU=SDLMAME
$ make [-j5] EMU=SDLMESS
$ sudo make install EMU=SDLMESS
$ sudo make distclean EMU=SDLMESS

The "make install" step calls 'macdeploqt' which creates some files, so "sudo 
make distclean" is required here (unless you're building *as* root).

I hope I didn't break anything, but it seems to be much clean(er) now!

BTW, this should also work out-of-the-box on Lion since XCode tools are 
actually no longer used -- but again, this requires Qt 4.8+! For Qt 4.7, the 
behavior *should* (untested) be the same as before.

Have fun, René