py2app corrupting libraries

On May 10, 2006, at 5:14 PM, Kent Quirk wrote:

> We have a large mixed Python and C++ application with
about a dozen  
> frameworks which cross-reference one another.
>
>
>
> We’ve been shipping it for almost a year on PPC Macs
using py2app  
> to package things – so we know we have the py2app stuff

> approximately correct. We’ve been trying off and on to
get a fat  
> version of the app working. All the C++ code compiles
and links  
> cleanly on both architectures. We’ve installed fat
Python 2.4.3  
> (the April 7 version).
>
>
>
> When we run the current (0.2-maint) branch of py2app on
our Intel  
> Mac, somewhere along the way, it tells us that it’s
“Thinning” our  
> “Events” library to the i386 part only…then, later on,
it tries to  
> thin the same library to both the ppc and i386
versions…but doesn’t  
> find the ppc version anymore and crashes.
>
>
>
> Possibly of interest, but possibly a red herring:
py2app spends a  
> fair amount of time building the dependency graph and
doing many  
> operations over and over (the graph of our library
dependencies is  
> basically a web, not a hierarchy, and it seems to be
doing a pretty  
> exhaustive walk of the graph).
>
>
>
> We tried going into the macholib/util.py and stubbing
out the  
> thin_to_archs() function. As we only build the two
architectures we  
> care about, and we want both, we figured this should be
safe.  But  
> then py2app crashes with an unrecognized magic number
in some of  
> the libraries. So we changed thin_to_archs() so that it
always used  
> both architectures, no matter what it was asked to
build…and got  
> the same (magic) problem. We even tried reversing the
order of the  
> two in case there was an order dependency somewhere.

This probably isn't going to get fixed unless a patch or a
set of  
binaries to reproduce this issue is available. I'm pretty
much out of  
commission for the rest of the month though, so even with
binaries  
I'm not going to get anywhere with it any time soon.

-bob

_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIGpython.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Bob Ippolito:
> On May 10, 2006, at 5:14 PM, Kent Quirk wrote:

>> We’ve been shipping it for almost a year on PPC
Macs using py2app  
>> to package things – so we know we have the py2app
stuff  
>> approximately correct. We’ve been trying off and on
to get a fat  
>> version of the app working. All the C++ code
compiles and links  
>> cleanly on both architectures. We’ve installed fat
Python 2.4.3  
>> (the April 7 version).
>>
>> When we run the current (0.2-maint) branch of
py2app on our Intel  
>> Mac, somewhere along the way, it tells us that it’s
“Thinning” our  
>> “Events” library to the i386 part only…then, later
on, it tries to  
>> thin the same library to both the ppc and i386
versions…but doesn’t  
>> find the ppc version anymore and crashes.

You are probably aware of this, and even if not I'm not
sure whether it 
helps, but here it goes anyway: did you add an
"archs='ppc,i386'" to the 
py2app options? Before I did that too much stuff got thinned
away for me 
too.

Example options from setup.py:

if sys.argv[1] == 'py2app':
     import py2app
     setupOptions.update(dict(app=['taskcoach.py'],
         options=dict(py2app=dict(archs='ppc,i386',
argv_emulation=True,
             compressed=True, dist_dir=builddir, optimize=2,
             iconfile='icons.in/taskcoach.icns',
             packages=['i18n']))))

Hope that is of use, Frank
_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIGpython.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

py2app corrupting libraries

Thread: py2app corrupting libraries