On Apr 4, 2006, at 6:13 PM, Todd O'Bryan wrote: > OK, I successfully installed it. (Thanks for the simple-but-time- > consuming-download-wise fix, Bob.) > > Now, how do I donate the binary back to the cause?
The current strategy would be to either build an egg for it, or a bdist_mpkg (probably the best idea for packages that don't use setuptools yet). Currently the version of py2app that should be used with a universal Python lives here (there hasn't bean a release yet): http://svn.red-bean.com/bob/py2app/branches/py2app-0.2-maint/ If you check that out and do: python setup.py bdist_mpkg --open That will install py2app and related tools. After that's done, you'll have a new bdist_mpkg shell command which you can just run in any directory with a setup.py and it will (more likely than not) build a .mpkg out of it. > P.S. I'm willing to do some others, assuming it's not too > complicated. MySQL-python just released 1.2.1, and 1.2.0 is the most > recent available binary. I was able to install it, I think, but I got > this warning when I tried to build. > > gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -g > -bundle -undefined dynamic_lookup build/temp.macosx-10.4-fat-2.4/ > _mysql.o -L/usr/local/mysql/lib -lmysqlclient_r -lz -lm -o build/ > lib.macosx-10.4-fat-2.4/_mysql.so > /usr/bin/ld: for architecture i386 > /usr/bin/ld: warning /usr/local/mysql/lib/libmysqlclient_r.a > archive's cputype (18, architecture ppc) does not match cputype (7) > for specified -arch flag: i386 (can't load from it) That means your MySQL libraries are PPC only and won't be compatible with Python running on i386. You'll want to obtain a universal build of MySQL to link against. -bob _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
