[Pythonmac-SIG] PyObjC/Py2App build problem
bob at redivi.com
Mon Jun 5 21:26:49 CEST 2006
On Jun 5, 2006, at 12:21 PM, Michael Glassford wrote:
> Ronald Oussoren wrote:
>> On 5-jun-2006, at 20:42, Michael Glassford wrote:
>>> Ronald Oussoren wrote:
>>>> On 2-jun-2006, at 22:39, Michael Glassford wrote:
>>>>> This seems to have worked for me. I'm now getting another error
>>>>> (at the end of this message). I haven't had time to look at it
>>>>> yet because of other things that came up today, so it may be
>>>>> something simple.
>>>> This looks like PyObjC being build for PPC being used on Intel,
>>>> that is the architecture for which PyObjC is build doesn't match
>>>> the architecture of the currently running interpreter. The easiest
>>>> way to fix this is probably to build a universal binary of PyObjC,
>>>> there's an AUTO_UNIVERSAL option at the top of setup.py that
>>>> enables building a universal binary with Apple's distribution of
>>>> Python 2.3.
>>> I'm not using Apple's distribution of Python 2.3, so I didn't think
>>> this was necessary (I'm using 2.4.1 from from http://pythonmac.org/
>>> packages/py24-fat/). However, doing this fixed the problem and the
>>> application now works.
>> Ehmm, you are NOT using Python 2.4. Look at the error message in your
>> original e-mail, this mentions /System/Library/Python.framework/
> Well, you're right about that; apparently I wasn't using it there.
> However, I am using it most of the time, including earlier today
> when I
> said I got it working (I've verified that). What must have happened is
> this: /usr/local/bin isn't permanently added to the beginning of my
> because most of the real work I'm doing requires Python 2.3; instead,
> when I want to work on the universal binary build, I open a new
> window and add it manually. I must have forgotten to add it once.
Out of curiosity, what are you doing that requires 2.3?
> So when I am correctly using the universal binary build of Python
> (not 2.4.1, as Bob pointed out; sorry, I'm juggling too many things
> today), is it necessary to set AUTO_UNIVERSAL = 1 in PyObjC's
It's not necessary to set it if you're using a universal build of
Python. It's effectively just a hack to get PyObjC (and only PyObjC)
to build universally with Apple's Python 2.3.
More information about the Pythonmac-SIG