Hi,
I just wanted to jump on the Python 3 and (Py)Qt 4.5 train.
I am on Mac OS X 10.5.6 with Python 3.0.1 installed from the binary
packages available at python.org and the QT-SDK 4.5 from
Trolltech/Nokia!
I used the latest snapshots for sip and PyQt.
I have two issues:
1. In the configure.py it
On Wed, 25 Mar 2009 10:05:39 +0100, Oliver Heyme
wrote:
> Hi,
>
> I just wanted to jump on the Python 3 and (Py)Qt 4.5 train.
> I am on Mac OS X 10.5.6 with Python 3.0.1 installed from the binary
> packages available at python.org and the QT-SDK 4.5 from
> Trolltech/Nokia!
> I used the latest sna
I had this error on two different machines using both 10.4 and 10.5.
I'm building universal binaries by passing -n to sip. Is your build
environment any different?
On Wed, Mar 25, 2009 at 8:08 PM, Phil Thompson
wrote:
> On Wed, 25 Mar 2009 10:05:39 +0100, Oliver Heyme
> wrote:
>> Hi,
>>
>> I jus
Hi Damien,
I fixed that on my 10.5. machine!
I still had an old SIP 4.7.9 for Python 2.5.1 installed. Although I
installed the latest sip-snapshot with Python 3 it somehow got
confused with that old version!
I just removed all files from that installation and then it worked
without any problem!
H
Unfortunately in my case one of the machines I tested was a fresh
install, so there should be no issue of old libraries lying around. I
also tried removing the old sip libraries and installing the latest
sip on the other machine, but no go.
Phil, can you give me any instructions on how I can track
Hello,
2009/3/27 Damien Elmes :
> Unfortunately in my case one of the machines I tested was a fresh
> install, so there should be no issue of old libraries lying around. I
> also tried removing the old sip libraries and installing the latest
> sip on the other machine, but no go.
I've just tried
On Fri, 27 Mar 2009 14:13:48 +0900, Damien Elmes wrote:
> Unfortunately in my case one of the machines I tested was a fresh
> install, so there should be no issue of old libraries lying around. I
> also tried removing the old sip libraries and installing the latest
> sip on the other machine, but
This seems to be a problem with building universal binaries. If I
recompile sip without the -n flag to configure, the library loads
correctly.
Watching the compile for a -n build shows this warning
ld warning: in
/Users/ema/PyQt-mac-gpl-4.5-snapshot-20090326/qpy/QtCore/libqpycore.a,
file is not
I was testing this on a 10.5 box. I just noticed that it's using the
10.5 sysroot, so I will try again using the 10.4u SDK. On the 10.4 box
I was using, however, I was already using the 10.4u SDK.
On Sat, Mar 28, 2009 at 12:16 PM, Damien Elmes wrote:
> This seems to be a problem with building uni
Found the bug. In the project files, you are doing
CONFIG += ppc i386
as per the qmake docs, it should read
CONFIG += ppc x86
This resulted in only the PPC half of the library being built, and
thus missing symbols when running on an Intel. I changed configure.py
in a few places to use the corre
The build was successful, and the few example programs I tested run
fine now. However, my app seems to be dying - it looks like some
internal data is getting clobbered somewhere. An line like:
import mymodule
results in a
TypeError: bad argument type for built-in operation
The problem seems to
On Sat, 28 Mar 2009 15:51:29 +0900, Damien Elmes wrote:
> The build was successful, and the few example programs I tested run
> fine now. However, my app seems to be dying - it looks like some
> internal data is getting clobbered somewhere. An line like:
>
> import mymodule
>
> results in a
>
>
On Sat, 28 Mar 2009 13:01:53 +0900, Damien Elmes wrote:
> Found the bug. In the project files, you are doing
>
> CONFIG += ppc i386
>
> as per the qmake docs, it should read
>
> CONFIG += ppc x86
>
> This resulted in only the PPC half of the library being built, and
> thus missing symbols when
13 matches
Mail list logo
