Re: [qmc2-devel] New QT 4.8 paths cause MacOS build issues
Brought to you by:
prianthefist,
renereucher
|
From: David E. <ev...@gm...> - 2012-05-21 17:08:18
|
Okay, I tracked down where the problem started. It was rev 3889 which seems to have broke all QT 4.7.3 builds with Xcode 3 on my Snow Leopard build server. QT 4.8 builds with Xcode 4.3 work fine on Lion, with the exception of the SDLMESS bundle icon. Dave On Mon, May 21, 2012 at 12:15 PM, David Ely <ev...@gm...> wrote: > I finally got my QT 4.8 compiles to work. I ended up having to > reinstall Xcode and compile QT myself. Very strange. > > One last problem though. The app bundle for SDLMESS doesn't have the > icon assigned to it. It's just a cosmetic thing, so we can release > without fixing it, but it is a weird problem. The app bundle for > SDLMAME is fine. > > Also, it appears that universal builds broke somewhere in the last 50 > revs or so. I'm trying to figure out exactly where. Here's the build > error: > > --- > ** BUILD FAILED ** > > The following build commands failed: > qmc2-sdlmame: > CompileC build/Makefile.qmake.build/Release/qmc2-sdlmame.build/Objects-normal/i386/miniwebbrowser.o > /Users/goldenegg/Documents/source/qmc2/trunk/miniwebbrowser.cpp normal > i386 c++ com.apple.compilers.gcc.4_2 > (1 failure) > > 2012-05-21 12:13:11.353 xcodebuild[19394:80b] PBXProject at > /Users/goldenegg/Documents/source/qmc2/trunk/Makefile.qmake.xcodeproj > still has 1 registered items after during deallocation. These items > are of the following classes: > 2012-05-21 12:13:11.354 xcodebuild[19394:80b] PBXGlobalID: 1 > 2012-05-21 12:13:11.354 xcodebuild[19394:80b] Global ID list: > 2012-05-21 12:13:11.354 xcodebuild[19394:80b] DF07382C368E7F9EAE2A5016 > make: *** [qmc2-bin] Error 1 > --- > > > Dave > > On Fri, May 11, 2012 at 6:35 AM, R. Reucher <ren...@ba...> wrote: >> On Friday 11 May 2012 09:30:45 Robert Hamberger wrote: >> >>> I will give them a try tonight to find out if it works for me. >> >>> >> >>> Thanks for the (possible) solution. ;-) >> >> I'm quite sure that this IS the solution, though I'm absolutely confused as >> to why my local build acts differently than the 'official' Qt Mac build in >> this regard. >> >> >> With the working-as-expected qmake, everything is mostly the same as on >> Linux/UNIX in general, only the 'make install' step is Mac OS X specific >> (using 'macdeployqt'). >> >> >> Cheers, René >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> qmc2-devel mailing list >> qmc...@li... >> https://lists.sourceforge.net/lists/listinfo/qmc2-devel >> |