[PyQt] Next Releases of PyQt and SIP [Building on OS X 10.4]

[Phil Thompson]

On Fri, 30 Oct 2009 23:06:56 -0600, Melton Low <softw.devl at gmail.com>
wrote:
> On Tue, Oct 27, 2009 at 10:31 PM, Melton Low <softw.devl at gmail.com>
wrote:
> 
>> On Wed, Oct 21, 2009 at 3:27 AM, Phil Thompson <
>> phil at riverbankcomputing.com> wrote:
>>
>>> On Tue, 20 Oct 2009 13:23:43 -0600, Melton Low <softw.devl at gmail.com>
>>> wrote:
>>> > On Tue, Oct 20, 2009 at 11:17 AM, Phil Thompson
>>> > <phil at riverbankcomputing.com
>>> >> wrote:
>>> >
>>> >> On Sat, 17 Oct 2009 17:31:40 -0600, Melton Low
<softw.devl at gmail.com>
>>> >> wrote:
>>> >> > Executing PyQt4's configure.py on Mac OS X 10.4.11 continues to
>>> produce
>>> >> > errors.
>>> >> > This is on a PPC Mac running OS X 10.4.11:
>>> >> > Python 2.6.3
>>> >> > Qt 4.5.3 carbon version
>>> >> > Sip 4.9.1 snapshots 20091015
>>> >> > PyQt4 4.6.1 snapshots 20091014
>>> >> >
>>> >> > Configuration problem sharted with:
>>> >> > Qt 4.5.3 carbon version
>>> >> > Sip 4.9.1 snapshots 20091002
>>> >> > PyQt4 4.6.1 snapshots 20091002
>>> >> >
>>> >> > Problem disappeared if I completely removed Qt and reinstalled an
>>> >> > earlier
>>> >> > version of Qt:
>>> >> > Qt 4.5.2 carbon version
>>> >> > Sip 4.9.1 snapshots 20091001
>>> >> > PyQt4 4.6.1 snapshots 20091001
>>> >> >
>>> >> > I had posted the problem earlier.  If this is being worked on,
>>> >> > please
>>> >> > ignore
>>> >> > this.  In case the new configure verbose output is useful I am
>>> >> > including
>>> >> it
>>> >> > as an attachment since it's quite lengthy.
>>> >>
>>> >> Have you tried configuring SIP with "--arch ppc"?
>>> >>
>>> >> Have you installed PyQt before on this system?
>>> >>
>>> >> Phil
>>> >>
>>> >
>>> > I have had PyQt on this system since of Qt 4.5.1.
>>> >
>>> > I tried --arch=PPC with Sip and --use_arch=PPC with PyQt the day
>>> > before.
>>> > No
>>> > difference.
>>>
>>> This looks like a problem with Qt v4.5.3 where it's insisting on
>>> building
>>> for i386 (even if you have "CONFIG -= x86" in your .pro file).
>>>
>>> It would be interesting to compare the contents of Qt's
>>> mkspecs/features/mac directory with an earlier version of Qt. If they
>>> are
>>> different then this is what you would need to hack at.
>>>
>>> You could also try adding "CONFIG -= x86" to the top of the
>>> qtdirs.profile
>>> that PyQt's configure.py generates and run qmake manually on it to see
>>> if
>>> the "-arch i386" still appears in the Makefile.
>>>
>>> Phil
>>>
>>
>> Hi Phil,
>>
>> Just tried run qmake on qtdirs.mk manually with the added CONFIG line to
>> the top of qtdirs.pro.  Please note that 'python configure.py --use-arch
>> ppc' did not complete but it did produce the qtdirs.pro and other qtdirs
>> files.
>>
>> Attached are qtdirs.pro and the output of the qmake command. The first
>> g++
>> line showed -arch i386 and -arch ppc. Your suspicion may be correct.
>>
>> Mel
>>
> 
> Hi Phil,
> 
> I just downloaded the Mac Qt sources for 4.5.2 and 4.5.3.  Two files in
> the mkspecs/features/mac directory have changed namely default_post.prf
and
> objective_c.prf.
> 
> The results running diff are as follow:
> 
> BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac
> melton$
> diff default_post.prf
> ~/Desktop/qt/qt-mac-opensource-src-4.5.3/mkspecs/features/mac2a3,17
>>
>> # Pick a suitable default architecture for qmake-based applications.
>> # If the Qt package contains one of x86 and x86_64, pick that one. If it
>> # contains both then use the compiler default. Make a similiar decision
> for
>> # PowerPC-based systems. Note that this logic assumes that Qt has been
>> # configured with an architecture that is usable on the system.
>> qt:!isEmpty(QT_CONFIG) {
>>     contains(QMAKE_HOST.arch, ppc) {
>>         !contains(QT_CONFIG, ppc64):contains(QT_CONFIG, ppc):CONFIG +=
>>         ppc
>>         contains(QT_CONFIG, ppc64):!contains(QT_CONFIG, ppc):CONFIG +=
> ppc64
>>     } else {
>>         !contains(QT_CONFIG, x86_64):contains(QT_CONFIG, x86):CONFIG +=
> x86
>>         contains(QT_CONFIG, x86_64):!contains(QT_CONFIG, x86):CONFIG +=
> x86_64
>>     }
>> }
> BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac
> melton$
> BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac
> melton$
> diff objective_c.prf
> ~/Desktop/qt/qt-mac-opensource-src-4.5.3/mkspecs/features/mac
> 3d2
> < isEmpty(QMAKE_OBJECTIVE_CFLAGS) { #bootstrap
> 12c11
> < }
> ---
>>
> BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac
> melton$
> 
> I have attached the two files from 4.5.2 and 4.5.3.  They have been
renamed
> so you can tell from which Qt version it came from.
> 
> Hope you can figure out a fix.

This just confirms it's a Qt problem - or maybe you can build Qt in such a
way as to work around it - but I don't see how it is a PyQt problem.

Phil