[Qgis-developer] Re: INSTALL.t2t edits

[John C. Tull]

On Nov 18, 2009, at 9:22 AM, John C. Tull wrote:

> 
> On Nov 18, 2009, at 9:13 AM, William Kyngesburye wrote:
> 
>> On Nov 18, 2009, at 11:00 AM, John C. Tull wrote:
>> 
>>> On Nov 18, 2009, at 8:54 AM, William Kyngesburye wrote:
>>> 
>>>> OK, comments and questions:
>>>> 
>>>> - what is the 32bit python/qt issue with cmake?  configuration?  compilation?  I guess I need to check on the cmake compilation occassionally ;)
>>> 
>>> Basically, when you try the cmake installation with qt-carbon (either 4.5.3 or 4.6.0-rc/beta), a complaint about not finding pyqt4 is generated and python bindings are not enabled. I cannot seem to find much out about why this happens or how to get around it. That was where the -m32 settings came from; a shot in the dark to see if it would work. So, the problem is in configuration.
>>> 
>> ... ah, it's very possible that the cmake tests are running python raw, which on Snow means 64bit, thus it doesn't find the 32bit PyQt and SIP.  I can look at it to see if there is an option or workaround so it tests 32bit.
>> 
>> I'm updating Qt/SIP/PyQt to current release versions (4.5.3/4.9.1/4.6.1 Carbon) and I'll try a cmake build.
> 
> A more knowledgeable set of eyes and hands on this will be good! I tried a few things, like prepending the python binary path from ccmake with 'arch -i386', but could not find a solution.
> 

Strangely, I just built qgis as an i386 binary, but the installed qt, pyqt and sip are all x86_64. I get an error about sip.so being the wrong architecture (as expected). It seems that pyqt being 64-bit allows things to get picked up with cmake, despite the architecture not matching the CMAKE_OSX_ARCHITECTURES=i386 setting.

This might shed some light on things. It seems very peculiar that I can have an i386 qgis binary running inside 64-bit qt:

file /Applications/qgis1.4.0.app/Contents/MacOS/qgis 
/Applications/qgis1.4.0.app/Contents/MacOS/qgis: Mach-O executable i386

This build is a little bit like Frankenstein, and not what I intended to do. I forgot to change my CMAKE_OSX_ARCHITECTURES to x86_64. Maybe this sheds some light on the problem, although it seems to obfuscate things in my mind.

John