Nabble - Python - pythonmac-sig

Re: How to get setuptools to build a Universal Binary?

2009-01-07T22:13:23Z

Ned Deily wrote:
> Safer: after fixing the mysql libs installed on your mac (not in the app
> bundle), first rebuild MySQLdb,

yep -- the linking probably failed for the PPC side.

-Chris

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T22:04:50Z

In article <nad-9C3FF0.21305307012009@...>,
Ned Deily <nad@...> wrote:
> Did you try rebuilding the app bundle with py2app after the mysql libs
> were fixed?

Safer: after fixing the mysql libs installed on your mac (not in the app
bundle), first rebuild MySQLdb, then rebuild the app with py2app.

--
Ned Deily,
nad@...

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T21:30:53Z

In article <496586D9.8000000@...>, Joe Strout <joe@...>
wrote:

> Ned Deily wrote:
>
> > Hmm, there's omething odd about that download.
> > ...
>
> > $ file libmysqlclient_r.16.0.0.dylib
> > libmysqlclient_r.16.0.0.dylib: Mach-O universal binary with 3
> > architectures
> > libmysqlclient_r.16.0.0.dylib (for architecture i386): Mach-O
> > dynamically linked shared library i386
> > libmysqlclient_r.16.0.0.dylib (for architecture ppc64): Mach-O 64-bit
> > dynamically linked shared library ppc64
> > libmysqlclient_r.16.0.0.dylib (for architecture ppc): Mach-O dynamically
> > linked shared library ppc
> >
> > $ file libmysqlclient_r.16.dylib
> > libmysqlclient_r.16.dylib: Mach-O dynamically linked shared library i386
>
> OK, I think I see your point here. In the 5.1 download,
> libmysqlclient_r.16.0.0.dylib is universal, but
> libmysqlclient_r.16.dylib is not. From the looks of the 5.0 download,
> these should be the same (both universal).
>
> > Perhaps you can get away with making a symlink or copying from one to
> > the other??
>
> Seems reasonable, so as a test, I copied libmysqlclient_r.16.0.0.dylib
> into my app bundle on top of libmysqlclient_r.16.dylib. I verified with
> "file" that my libmysqlclient_r.16.dylib is now universal, and verified
> that my app still runs on an Intel Mac. But on a PPC (10.4) Mac, it
> still fails:
>
> File
> "/Users/jstrout/Temp/etownCentral.app/Contents/Resources/IADB.py", line
> 12, in <module>
> import MySQLdb
> File "MySQLdb/__init__.pyc", line 19, in <module>
> ImportError:
> dlopen(/Users/jstrout/Temp/etownCentral.app/Contents/Resources/lib/python2.5/l
> ib-dynload/_mysql.so,
> 2): Symbol not found: _mysql_get_host_info
> Referenced from:
> /Users/jstrout/Temp/etownCentral.app/Contents/Resources/lib/python2.5/lib-dynl
> oad/_mysql.so
> Expected in: dynamic lookup

Did you try rebuilding the app bundle with py2app after the mysql libs
were fixed?

> I used "otool -L" to check the dependencies of both _mysql.so and
> libmysqlclient_r.16.dylib. All seemed satisfactory, though the one for
> the latter is a little strange:
>
> $ otool -L libmysqlclient_r.16.dylib
> libmysqlclient_r.16.dylib:
> /usr/local/mysql/lib/libmysqlclient_r.16.dylib (compatibility
> version 17.0.0, current version 17.0.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
> current version 88.1.11)
>
> I'm not sure why libmysqlclient_r.16.dylib is listing a dependency on
> itself, but in /usr/local. There is no /usr/local/mysql on a standard
> machine (including the one where this is failing). Yet otool does list
> a "current version", perhaps because it's finding itself within the app
> bundle? Seems a little odd.

otools -L on the 5.0 libs I have installed shows similar results. I
wouldn't worry about it.

--
Ned Deily,
nad@...

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T20:53:45Z

Ned Deily wrote:

> Hmm, there's omething odd about that download.
> ...

> $ file libmysqlclient_r.16.0.0.dylib
> libmysqlclient_r.16.0.0.dylib: Mach-O universal binary with 3
> architectures
> libmysqlclient_r.16.0.0.dylib (for architecture i386): Mach-O
> dynamically linked shared library i386
> libmysqlclient_r.16.0.0.dylib (for architecture ppc64): Mach-O 64-bit
> dynamically linked shared library ppc64
> libmysqlclient_r.16.0.0.dylib (for architecture ppc): Mach-O dynamically
> linked shared library ppc
>
> $ file libmysqlclient_r.16.dylib
> libmysqlclient_r.16.dylib: Mach-O dynamically linked shared library i386

OK, I think I see your point here. In the 5.1 download,
libmysqlclient_r.16.0.0.dylib is universal, but
libmysqlclient_r.16.dylib is not. From the looks of the 5.0 download,
these should be the same (both universal).

> Perhaps you can get away with making a symlink or copying from one to
> the other??

Seems reasonable, so as a test, I copied libmysqlclient_r.16.0.0.dylib
into my app bundle on top of libmysqlclient_r.16.dylib. I verified with
"file" that my libmysqlclient_r.16.dylib is now universal, and verified
that my app still runs on an Intel Mac. But on a PPC (10.4) Mac, it
still fails:

File
"/Users/jstrout/Temp/etownCentral.app/Contents/Resources/IADB.py", line
12, in <module>
import MySQLdb
File "MySQLdb/__init__.pyc", line 19, in <module>
ImportError:
dlopen(/Users/jstrout/Temp/etownCentral.app/Contents/Resources/lib/python2.5/lib-dynload/_mysql.so,
2): Symbol not found: _mysql_get_host_info
Referenced from:
/Users/jstrout/Temp/etownCentral.app/Contents/Resources/lib/python2.5/lib-dynload/_mysql.so
Expected in: dynamic lookup

I used "otool -L" to check the dependencies of both _mysql.so and
libmysqlclient_r.16.dylib. All seemed satisfactory, though the one for
the latter is a little strange:

$ otool -L libmysqlclient_r.16.dylib
libmysqlclient_r.16.dylib:
/usr/local/mysql/lib/libmysqlclient_r.16.dylib (compatibility
version 17.0.0, current version 17.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 88.1.11)

I'm not sure why libmysqlclient_r.16.dylib is listing a dependency on
itself, but in /usr/local. There is no /usr/local/mysql on a standard
machine (including the one where this is failing). Yet otool does list
a "current version", perhaps because it's finding itself within the app
bundle? Seems a little odd.

The dependencies for mysql.so itself all look fine to me and refer only
to three system files that really do exist.

So I'm stumped again... both libraries are now universal, yet for some
reason, the _mysql_get_host_info symbol is not resolving. Any idea what
to try next?

Thanks,
- Joe

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T20:49:21Z

In article <49657DCF.8030204@...>, Joe Strout <joe@...>
wrote:
> I'm going to come back to this via another post -- sounds like Ned has
> found that the 5.1 distribution of MySQL really is a bit messed up, but
> the 5.0 one is OK. So maybe if I just do this over with the 5.0 distro,
> it will work.

Note, I haven't tested this so YMMV. If you can get away with using a
5.0 client, that should work. But if you just fix-up the 5.1 libs with
a couple of copies that should work, too. Go to the directory of your
mysql installation, probably something like:

cd /usr/local/mysql-5.1.30-osx10.4-universal

Then:

cd lib
ls -l *.dylib
file *.dylib

sudo sh

cp -p libmysqlclient.16.0.0.dylib libmysqlclient.16.dylib
cp -p libmysqlclient.16.0.0.dylib libmysqlclient.dylib

cp -p libmysqlclient_r.16.0.0.dylib libmysqlclient_r.16.dylib
cp -p libmysqlclient_r.16.0.0.dylib libmysqlclient_r.dylib

--
Ned Deily,
nad@...

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T20:15:11Z

Christopher Barker wrote:

>> MySQLdb folder containing a bunch of other .pyc files. Nothing else
>> though; just Python bytecode. Is it possible that MySQLdb is written
>> entirely in Python, and was never the problem at all?
>
> no -- there is C code that needs to be compiled, I"m pretty sure anyway!

You are correct; I found _mysql.so in the
Resources/lib/python2.5/lib-dynload folder. It's a universal binary.

>> /Users/jstrout/Downloads/mysql-5.1.30-osx10.4-universal/lib/libmysqlclient_r.16.dylib:
>> Mach-O dynamically linked shared library i386
>>
>> So it turns out that the 10.4 Universal mysql isn't. (Or at least,
>> this particular library isn't -- perhaps there's another library in
>> here somewhere with a different name, that serves the same function
>> for PPC?)
>
> could be -- I'm just guessing here, but I suspect that libmysqlclient
> may be used only for custom clients, so it may have gotten built
> non-universal and no one has noticed. What do the other libs in there
> look like?

I'm going to come back to this via another post -- sounds like Ned has
found that the 5.1 distribution of MySQL really is a bit messed up, but
the 5.0 one is OK. So maybe if I just do this over with the 5.0 distro,
it will work.

Best,
- Joe

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T18:03:19Z

In article <nad-E5578C.17114507012009@...>,
Ned Deily <nad@...> wrote:
> Yes, but see my followup post. After comparing the 5.0 and 5.1
> tarballs, it seems clear that the libs on the 5.1 tarball are hosed a
> bit.

I've opened bug #41940 on the MySQL tracker to document the problem.

--
Ned Deily,
nad@...

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T17:11:45Z

In article <49654D58.2080001@...>,
Christopher Barker <Chris.Barker@...> wrote:
> > and, with a fat python config:
> >
> > $ file _mysql.so
> > _mysql.so: Mach-O universal binary with 2 architectures
> > _mysql.so (for architecture i386): Mach-O bundle i386
> > _mysql.so (for architecture ppc): Mach-O bundle ppc
>
> Ned, how did you built that?

easy_install -Z MySQL-python

using python from the python.org 2.5 universal installer.

> > $ file libmysqlclient_r.16.0.0.dylib
> > libmysqlclient_r.16.0.0.dylib: Mach-O universal binary with 3
> > architectures
> > libmysqlclient_r.16.0.0.dylib (for architecture i386): Mach-O
> > dynamically linked shared library i386
> > libmysqlclient_r.16.0.0.dylib (for architecture ppc64): Mach-O 64-bit
> > dynamically linked shared library ppc64
> > libmysqlclient_r.16.0.0.dylib (for architecture ppc): Mach-O dynamically
> > linked shared library ppc
>
> and where did you get this? is that from the tarball on the MySQL site?

Yes, but see my followup post. After comparing the 5.0 and 5.1
tarballs, it seems clear that the libs on the 5.1 tarball are hosed a
bit.

--
Ned Deily,
nad@...

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T16:57:45Z

In article <nad-B78282.16124207012009@...>,
Ned Deily <nad@...> wrote:

> In article <49653A6A.3070805@...>, Joe Strout <joe@...>
> wrote:
> [...]
> > But OK, now this brings up the question of why my
> > libmysqlclient_r.16.dylib is Intel-only, when I took pains to install a
> > UB version of MySQL (c.f. the "Installing MySQL" section of
> > <http://www.dotancohen.com/howto/python-app-mac.html>). (I'm going to
> > do a fresh download of that mysql binary package and poke around inside
> > to see what I find.)
>
> Hmm, there's omething odd about that download.
>
> -rw-r--r--@ 1 nad staff 4396 Nov 20 23:31 libdbug.a
> -rw-r--r--@ 1 nad staff 2619952 Nov 20 23:31 libheap.a
> -rw-r--r--@ 1 nad staff 7612800 Nov 20 23:31 libmyisam.a
> -rw-r--r--@ 1 nad staff 3293744 Nov 20 23:31 libmyisammrg.a
> -rwxr-xr-x@ 1 nad staff 15266468 Nov 20 23:32
> libmysqlclient.16.0.0.dylib
> -rwxr-xr-x@ 1 nad staff 4781040 Nov 15 14:57 libmysqlclient.16.dylib
> -rw-r--r--@ 1 nad staff 17541992 Nov 20 23:31 libmysqlclient.a
> -rwxr-xr-x@ 1 nad staff 4781040 Nov 15 14:57 libmysqlclient.dylib
> -rwxr-xr-x@ 1 nad staff 867 Nov 15 14:57 libmysqlclient.la
> -rwxr-xr-x@ 1 nad staff 15337152 Nov 20 23:32
> libmysqlclient_r.16.0.0.dylib
> -rwxr-xr-x@ 1 nad staff 4801460 Nov 15 14:57
> libmysqlclient_r.16.dylib
> -rw-r--r--@ 1 nad staff 17629744 Nov 20 23:31 libmysqlclient_r.a
> -rwxr-xr-x@ 1 nad staff 4801460 Nov 15 14:57 libmysqlclient_r.dylib
> -rwxr-xr-x@ 1 nad staff 881 Nov 15 14:57 libmysqlclient_r.la
> -rw-r--r--@ 1 nad staff 203291168 Nov 20 23:31 libmysqld.a
> -rw-r--r--@ 1 nad staff 5235560 Nov 20 23:31 libmystrings.a
> -rw-r--r--@ 1 nad staff 2435784 Nov 20 23:31 libmysys.a
> -rw-r--r--@ 1 nad staff 125656 Nov 20 23:30 libvio.a
> -rw-r--r--@ 1 nad staff 563080 Nov 20 23:30 libz.a
> -rwxr-xr-x@ 1 nad staff 741 Nov 15 14:57 libz.la
> drwxr-xr-x@ 2 nad staff 408 Nov 20 23:32 plugin
>
> $ file libmysqlclient_r.16.0.0.dylib
> libmysqlclient_r.16.0.0.dylib: Mach-O universal binary with 3
> architectures
> libmysqlclient_r.16.0.0.dylib (for architecture i386): Mach-O
> dynamically linked shared library i386
> libmysqlclient_r.16.0.0.dylib (for architecture ppc64): Mach-O 64-bit
> dynamically linked shared library ppc64
> libmysqlclient_r.16.0.0.dylib (for architecture ppc): Mach-O dynamically
> linked shared library ppc
>
> $ file libmysqlclient_r.16.dylib
> libmysqlclient_r.16.dylib: Mach-O dynamically linked shared library i386
>
> Perhaps you can get away with making a symlink or copying from one to
> the other??

Ah, out of curiosity I download the latest mysql-5.0 universal build and
there all of the library files in lib *are* indeed universal (which can
be verified by a doing a "file lib*"):

~/Downloads/mysql-5.0.67-osx10.4-universal/lib$ ls -l
total 265624
-rw-r--r--@ 1 nad staff 4380 Aug 5 06:14 libdbug.a
-rw-r--r--@ 1 nad staff 2929 Aug 4 05:30 libmysql.imp
-rwxr-xr-x@ 1 nad staff 15367288 Aug 5 06:15
libmysqlclient.15.0.0.dylib
-rwxr-xr-x@ 1 nad staff 15367288 Aug 5 06:15 libmysqlclient.15.dylib
-rw-r--r--@ 1 nad staff 17629984 Aug 5 06:15 libmysqlclient.a
-rwxr-xr-x@ 1 nad staff 15367288 Aug 5 06:15 libmysqlclient.dylib
-rwxr-xr-x@ 1 nad staff 15437700 Aug 5 06:15
libmysqlclient_r.15.0.0.dylib
-rwxr-xr-x@ 1 nad staff 15437700 Aug 5 06:15 libmysqlclient_r.15.dylib
-rw-r--r--@ 1 nad staff 17716472 Aug 5 06:15 libmysqlclient_r.a
-rwxr-xr-x@ 1 nad staff 15437700 Aug 5 06:15 libmysqlclient_r.dylib
-rw-r--r--@ 1 nad staff 5389152 Aug 5 06:15 libmystrings.a
-rw-r--r--@ 1 nad staff 2258096 Aug 5 06:15 libmysys.a
-rw-r--r--@ 1 nad staff 562976 Aug 5 06:14 libz.a

$ diff libmysqlclient_r.15.0.0.dylib libmysqlclient_r.15.dylib
$

So, it looks like the 5.1 universal download is slightly broken and the
copying suggestion should work.

--
Ned Deily,
nad@...

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T16:48:24Z

Ned Deily wrote:
> No, MySQLdb does have a C extension component. There should be a
> _mysql.so there somewhere. If you build it with easy_install, the
> unzipped egg layout is:

and if you build it with plain old "setup.py build", you get a build dir
with:

ls build/lib.macosx-10.3-ppc-2.5/
MySQLdb _mysql.so _mysql_exceptions.py

I've just done it straight, with a PPC build of MySQL -- I got:

gcc -arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -g
-bundle -undefined dynamic_lookup
build/temp.macosx-10.3-ppc-2.5/_mysql.o -L/usr/local/mysql/lib
-lmysqlclient_r -lz -lm -lmygcc -o build/lib.macosx-10.3-ppc-2.5/_mysql.so
/usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: for architecture i386
/usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning
build/temp.macosx-10.3-ppc-2.5/_mysql.o cputype (18, architecture ppc)
does not match cputype (7) for specified -arch flag: i386 (file not loaded)

which I think makes sense, as _mysql.o was built with the flags from
mysql-config, which only gives PPC as it's now set on my machine.

However:

$ file build/lib.macosx-10.3-ppc-2.5/_mysql.so
build/lib.macosx-10.3-ppc-2.5/_mysql.so: Mach-O universal binary with 2
architectures
build/lib.macosx-10.3-ppc-2.5/_mysql.so (for architecture i386):
Mach-O bundle i386
build/lib.macosx-10.3-ppc-2.5/_mysql.so (for architecture ppc): Mach-O
bundle ppc

so I did get a universal _mysql.so, but I doubt it would work on a Intel
machine.

> and, with a fat python config:
>
> $ file _mysql.so
> _mysql.so: Mach-O universal binary with 2 architectures
> _mysql.so (for architecture i386): Mach-O bundle i386
> _mysql.so (for architecture ppc): Mach-O bundle ppc

Ned, how did you built that?

> $ file libmysqlclient_r.16.0.0.dylib
> libmysqlclient_r.16.0.0.dylib: Mach-O universal binary with 3
> architectures
> libmysqlclient_r.16.0.0.dylib (for architecture i386): Mach-O
> dynamically linked shared library i386
> libmysqlclient_r.16.0.0.dylib (for architecture ppc64): Mach-O 64-bit
> dynamically linked shared library ppc64
> libmysqlclient_r.16.0.0.dylib (for architecture ppc): Mach-O dynamically
> linked shared library ppc

and where did you get this? is that from the tarball on the MySQL site?

-Chris

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T16:12:42Z

In article <49653A6A.3070805@...>, Joe Strout <joe@...>
wrote:

> Christopher Barker wrote:
>
> > the extensions that distutils builds will be called something like
> > _mysql. It will be in site_packages, and in your app bundle, along with
> > .py and .pyc files, NOT in with FrameWorks.
>
> Ah, I didn't know that. Poking around in Resources/lib (and including
> unzipping site-packages.zip), I find things like mySQL.pyc, and a
> MySQLdb folder containing a bunch of other .pyc files. Nothing else
> though; just Python bytecode. Is it possible that MySQLdb is written
> entirely in Python, and was never the problem at all? I.e., that given
> a suitable portable mysql client library, MySQLdb will Just Work?

No, MySQLdb does have a C extension component. There should be a
_mysql.so there somewhere. If you build it with easy_install, the
unzipped egg layout is:
$ ls -l
total 224
drwxrwx--- 2 nad admin 272 Feb 23 2008 EGG-INFO
drwxrwx--- 3 nad admin 714 Feb 23 2008 MySQLdb
-rwxrwxr-x 1 nad admin 257 Feb 23 2008 _mysql.py
-rw-rw---- 1 nad admin 697 Feb 23 2008 _mysql.pyc
-rw-rw---- 1 nad admin 697 Feb 23 2008 _mysql.pyo
-rwxrwxr-x 1 nad admin 77964 Feb 23 2008 _mysql.so
-rwxrwxr-x 1 nad admin 2306 Feb 23 2008 _mysql_exceptions.py
-rw-rw---- 1 nad admin 5279 Feb 23 2008 _mysql_exceptions.pyc
-rw-rw---- 1 nad admin 5279 Feb 23 2008 _mysql_exceptions.pyo

and, with a fat python config:

$ file _mysql.so
_mysql.so: Mach-O universal binary with 2 architectures
_mysql.so (for architecture i386): Mach-O bundle i386
_mysql.so (for architecture ppc): Mach-O bundle ppc

> But OK, now this brings up the question of why my
> libmysqlclient_r.16.dylib is Intel-only, when I took pains to install a
> UB version of MySQL (c.f. the "Installing MySQL" section of
> <http://www.dotancohen.com/howto/python-app-mac.html>). (I'm going to
> do a fresh download of that mysql binary package and poke around inside
> to see what I find.)

Hmm, there's omething odd about that download.

-rw-r--r--@ 1 nad staff 4396 Nov 20 23:31 libdbug.a
-rw-r--r--@ 1 nad staff 2619952 Nov 20 23:31 libheap.a
-rw-r--r--@ 1 nad staff 7612800 Nov 20 23:31 libmyisam.a
-rw-r--r--@ 1 nad staff 3293744 Nov 20 23:31 libmyisammrg.a
-rwxr-xr-x@ 1 nad staff 15266468 Nov 20 23:32
libmysqlclient.16.0.0.dylib
-rwxr-xr-x@ 1 nad staff 4781040 Nov 15 14:57 libmysqlclient.16.dylib
-rw-r--r--@ 1 nad staff 17541992 Nov 20 23:31 libmysqlclient.a
-rwxr-xr-x@ 1 nad staff 4781040 Nov 15 14:57 libmysqlclient.dylib
-rwxr-xr-x@ 1 nad staff 867 Nov 15 14:57 libmysqlclient.la
-rwxr-xr-x@ 1 nad staff 15337152 Nov 20 23:32
libmysqlclient_r.16.0.0.dylib
-rwxr-xr-x@ 1 nad staff 4801460 Nov 15 14:57
libmysqlclient_r.16.dylib
-rw-r--r--@ 1 nad staff 17629744 Nov 20 23:31 libmysqlclient_r.a
-rwxr-xr-x@ 1 nad staff 4801460 Nov 15 14:57 libmysqlclient_r.dylib
-rwxr-xr-x@ 1 nad staff 881 Nov 15 14:57 libmysqlclient_r.la
-rw-r--r--@ 1 nad staff 203291168 Nov 20 23:31 libmysqld.a
-rw-r--r--@ 1 nad staff 5235560 Nov 20 23:31 libmystrings.a
-rw-r--r--@ 1 nad staff 2435784 Nov 20 23:31 libmysys.a
-rw-r--r--@ 1 nad staff 125656 Nov 20 23:30 libvio.a
-rw-r--r--@ 1 nad staff 563080 Nov 20 23:30 libz.a
-rwxr-xr-x@ 1 nad staff 741 Nov 15 14:57 libz.la
drwxr-xr-x@ 2 nad staff 408 Nov 20 23:32 plugin

$ file libmysqlclient_r.16.0.0.dylib
libmysqlclient_r.16.0.0.dylib: Mach-O universal binary with 3
architectures
libmysqlclient_r.16.0.0.dylib (for architecture i386): Mach-O
dynamically linked shared library i386
libmysqlclient_r.16.0.0.dylib (for architecture ppc64): Mach-O 64-bit
dynamically linked shared library ppc64
libmysqlclient_r.16.0.0.dylib (for architecture ppc): Mach-O dynamically
linked shared library ppc

$ file libmysqlclient_r.16.dylib
libmysqlclient_r.16.dylib: Mach-O dynamically linked shared library i386

Perhaps you can get away with making a symlink or copying from one to
the other??

--
Ned Deily,
nad@...

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T16:00:30Z

Joe Strout wrote:
> MySQLdb folder containing a bunch of other .pyc files. Nothing else
> though; just Python bytecode. Is it possible that MySQLdb is written
> entirely in Python, and was never the problem at all?

no -- there is C code that needs to be compiled, I"m pretty sure anyway!
maybe I'll get a chance to try it myself.

> I.e., that given
> a suitable portable mysql client library, MySQLdb will Just Work?

that would be great, but no, I don't think so.

> But OK, now this brings up the question of why my
> libmysqlclient_r.16.dylib is Intel-only, when I took pains to install a
> UB version of MySQL (c.f. the "Installing MySQL" section of
> <http://www.dotancohen.com/howto/python-app-mac.html>). (I'm going to
> do a fresh download of that mysql binary package and poke around inside
> to see what I find.)

>
>> You can find what it builds in the "build" directory that distutils
>> creates when you run "setup.py build". It will be in something like:
>>
>> build/lib.macosx-10.3-ppc-2.5
>>
>> and I think will be called -mysql.so
>
> But now I'm confused again. I thought this library was part of the
> mysql distribution -- not something created by the Python script

"libmysqlclient" is part of mysql. I"m pretty sure that the python
module requires a compiled extension, that links against it, and it will
be called something like _mysql.so, and should get put in the build
directory when you built it, and installed somewhere in site-packages
when you install it.

> Thanks for your patience,

no problem -- this really is complex!

> /Users/jstrout/Downloads/mysql-5.1.30-osx10.4-universal/lib/libmysqlclient_r.16.dylib:
> Mach-O dynamically linked shared library i386
>
> So it turns out that the 10.4 Universal mysql isn't. (Or at least, this
> particular library isn't -- perhaps there's another library in here
> somewhere with a different name, that serves the same function for PPC?)

could be -- I'm just guessing here, but I suspect that libmysqlclient
may be used only for custom clients, so it may have gotten built
non-universal and no one has noticed. What do the other libs in there
look like?

-Chris

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

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

real-time video processing

2009-01-07T15:44:25Z

hi all,

first: theres a library called VideoCapture for Win32 environments
which makes it possible to access video-capture devices. is there
something similar for macs?

second: i would like to do real-time video-processing (like bright-
spot detection, movement detection, ...) using images recorded by a
webcam. is python suited to do so? any references?

i appreciate your hints to this quite crude question.

best,
michael
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@...
http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: How to get setuptools to build a Universal Binary?

2009-01-07T15:27:38Z

Christopher Barker wrote:

> the extensions that distutils builds will be called something like
> _mysql. It will be in site_packages, and in your app bundle, along with
> .py and .pyc files, NOT in with FrameWorks.

Ah, I didn't know that. Poking around in Resources/lib (and including
unzipping site-packages.zip), I find things like mySQL.pyc, and a
MySQLdb folder containing a bunch of other .pyc files. Nothing else
though; just Python bytecode. Is it possible that MySQLdb is written
entirely in Python, and was never the problem at all? I.e., that given
a suitable portable mysql client library, MySQLdb will Just Work?

But OK, now this brings up the question of why my
libmysqlclient_r.16.dylib is Intel-only, when I took pains to install a
UB version of MySQL (c.f. the "Installing MySQL" section of
<http://www.dotancohen.com/howto/python-app-mac.html>). (I'm going to
do a fresh download of that mysql binary package and poke around inside
to see what I find.)

> You can find what it builds in the "build" directory that distutils
> creates when you run "setup.py build". It will be in something like:
>
> build/lib.macosx-10.3-ppc-2.5
>
> and I think will be called -mysql.so

But now I'm confused again. I thought this library was part of the
mysql distribution -- not something created by the Python script
(indeed, not something specific to Python at all). If that's so, why
would "setup.py build" have anything to do with it?

Thanks for your patience,
- Joe

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T13:49:57Z

In article <nad-0B8379.13305407012009@...>,
Ned Deily <nad@...> wrote:
> It looks like there is an open feature request for the MySQL prebuilt
> packages to be built as universal libraries. The submitter includes a
> recipe for doing it yourself. I haven't tried it myself, though.
>
> <http://bugs.mysql.com/bug.php?id=23701>

P.S. This might also be of help:

<http://www.entropy.ch/blog/Mac+OS+X/2007/11/14/4-Way-Universal-Binary-My
SQL-for-Leopard-Configuration.html>

--
Ned Deily,
nad@...

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T13:30:54Z

In article <496506CC.30708@...>, Joe Strout <joe@...>
wrote:

> I'm (still) trying to make a neatly packaged Python app that works on
> both PPC and Intel Macs. All is good except for mysqldb; following the
> procedure I've documented at
> <http://www.dotancohen.com/howto/python-app-mac.html>, my app bundle
> contains an Intel-only binary of the mysqldb library
> (libmysqlclient_r.16.dylib).
>
> This page
> (http://developer.apple.com/opensource/buildingopensourceuniversal.html)
> at Apple suggests a possible solution: build separate Intel and PPC
> binaries, and then combine them with lipo. But of course that's using
> Makefiles. MySQLdb instead uses setuptools.
>
> So: does anyone have a clue how I can convince setuptools to build a PPC
> binary (or better yet, a Universal one) on an Intel machine?

libmysqlclient is part of the MySQL distribution, i.e. not specific to
python, so setuptools isn't the problem here.

It looks like there is an open feature request for the MySQL prebuilt
packages to be built as universal libraries. The submitter includes a
recipe for doing it yourself. I haven't tried it myself, though.

<http://bugs.mysql.com/bug.php?id=23701>

For python packages with C extensions, distutils, and hence setuptools,
does know how to build fat (ppc-32, intel-32) and even universal
({ppc|intel}{32|64}) libraries, depending on how the python distribution
itself was built and assuming the proper OSX SDK was installed from an
Xcode (Apple Developer Tools) distribution (see /Developer/SDKs/). The
recent pythons (2.5/2.6) from python.org are fat and were built with the
MacOSX10.4u.sdk.

BTW, I just use easy_install (from setuptools) to build and install
MySQLdb and, for that matter, nearly all python packages these days. As
long as the package uses distutils and doesn't get too fancy with
overriding or extending them, they install just fine with easy_install
as an egg, even if they don't explicitly use setuptools. In the
increasingly rare cases where that don't work, it's usually immediately
obvious, i.e. the install fails.

Also, eggs don't have to be installed as single zip files: that's just
the default. Add --always-unzip or -Z to the easy_install options to
install unzipped. To always install unzipped, create a
.pydistutils.cfg file in your home directory with an [easy_install]
section:

[easy_install]
zip-ok = 0

So, once you have a universal mysql client library installed,

easy_install -Z MySQL-python

should be all you need to download, build, and install mysqldb.

HTH!

--
Ned Deily,
nad@...

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T13:25:08Z

Christopher Barker wrote:
> here's mine:
> $ /usr/local/mysql/bin/mysql_config --cflags
> -I/usr/local/mysql/include -g -Os -arch ppc -fno-common
> -D_P1003_1B_VISIBLE -DSIGNAL_WITH_VIO_CLOSE -DSIGNALS_DONT_BREAK_READ
> -DIGNORE_SIGHUP_SIGQUIT -DDONT_DECLARE_CXA_PURE_VIRTUAL
>
> Darn -- there is an "-arch ppc" in there. However, it may be that
> distutils still add the "arch i386" who knows?

if it doesn't, you can probably add it yourself with a small edit to
setup.py

-Chris

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T13:20:06Z

Joe Strout wrote:
>> I just downloaded the mysqldb module from sourceforge to have a look
>> at how it decides how to compile its C extension. It looks like it's
>> getting the CFLAGS and LFLAGS from mysql_config. You'll need a
>> universal binary of libmysqlclient (as Chris already pointed out).

ouch, this does complicate things a bit -- as I have no idea how to get
a "universal" mysql_config -- it may be telling distutils to build the
extension with only one architecture.

> OK, but to be clear, libmysqlclient isn't something from somewhere else
> that mysqldb uses -- it's the C extension of mysqldb itself, right?
> Something built when I do "python setup.py install" in the mysqldb
> source directory?

nope -- see my other note.

the extensions that distutils builds will be called something like
_mysql. It will be in site_packages, and in your app bundle, along with
.py and .pyc files, NOT in with FrameWorks.

>> At any rate, you'll want to try to see what CFLAGS/LFLAGS were used to
>> compile libmysqlclient. You might try to run the following command in
>> terminal:
>>
>> $ mysql_config --cflags

here's mine:
$ /usr/local/mysql/bin/mysql_config --cflags
-I/usr/local/mysql/include -g -Os -arch ppc -fno-common
-D_P1003_1B_VISIBLE -DSIGNAL_WITH_VIO_CLOSE -DSIGNALS_DONT_BREAK_READ
-DIGNORE_SIGHUP_SIGQUIT -DDONT_DECLARE_CXA_PURE_VIRTUAL

Darn -- there is an "-arch ppc" in there. However, it may be that
distutils still add the "arch i386" who knows?

if you get it to build, you can then look at what it builds, and see if
that's Universal or not:

$ file name_of_lib

You can find what it builds in the "build" directory that distutils
creates when you run "setup.py build". It will be in something like:

build/lib.macosx-10.3-ppc-2.5

and I think will be called -mysql.so

but I don't actually have it building here.

I suppose I should try -- now that I've gone this far!

-Chris

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T13:08:23Z

Joe Strout wrote:
> That's what I'm trying to figure out how to do. (libmysqlclient is the
> library behind MySQLdb, as far as I can tell.)

libmysql is the library that PySQLdb depends on -- it is provided by
MySQL -- it is NOT built by distutils -- it is only linked to.

> you seem to
> think that libmysqlclient is something other than MySQLdb. I'm under
> the impression that it's the same thing.

nope -- I'm right -- libmysqlclient is just what you'd think __ it's the
library for mysql clients -- provide by MySQL. I just confirmed this my
downloading the installer from MySQL, and looking in and seeing what there:

$ file libmysqlclient.16.0.0.dylib

libmysqlclient.16.0.0.dylib: Mach-O dynamically linked shared library ppc

(I've got a PPC machine)

It looks like there is a static lib there, too.

So this is what I'd do:

get the dmg installer for both PPC and Intel for 10.4 from MySQL.

copy the intallers to your hard drive, and unpack Contents/Archive.pax.gz

poke around in there, and you'll find the dynlibs.

lipo the intel and ppc ones together, and presto!

Actually, I suppose what I'd do is install the native one on your build
machine properly, and then use lipo to add the other one to the copy
that's on that machine.

> It's fairly ridiculous, and I'm now to the
> point where I have to seriously consider whether it's worth continuing
> this project in Python, or spend a day or two rewriting it in REALbasic.

or use a different DB...

> I feel like I'm close, though --

I think so too.

> if I can just figure out how to make a
> P.S. While people have been very generous with their free help and
> advice, if anyone could be more motivated to spend a few hours on it as
> a paid consulting gig, I'd be happy to pay.

I'm not in a position to do that now -- but you can buy me a beer if we
ever cross paths!

-CHB

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T12:48:31Z

Daniel Miller wrote:

>> So: does anyone have a clue how I can convince setuptools to build a PPC
>> binary (or better yet, a Universal one) on an Intel machine?
>
> I just downloaded the mysqldb module from sourceforge to have a look at
> how it decides how to compile its C extension. It looks like it's
> getting the CFLAGS and LFLAGS from mysql_config. You'll need a universal
> binary of libmysqlclient (as Chris already pointed out).

OK, but to be clear, libmysqlclient isn't something from somewhere else
that mysqldb uses -- it's the C extension of mysqldb itself, right?
Something built when I do "python setup.py install" in the mysqldb
source directory?

> At any rate,
> you'll want to try to see what CFLAGS/LFLAGS were used to compile
> libmysqlclient. You might try to run the following command in terminal:
>
> $ mysql_config --cflags

-I/usr/local/mysql/include -g -Os -fno-common -D_P1003_1B_VISIBLE
-DSIGNAL_WITH_VIO_CLOSE -DSIGNALS_DONT_BREAK_READ
-DIGNORE_SIGHUP_SIGQUIT -DDONT_DECLARE_CXA_PURE_VIRTUAL

> Which may shed some light on the situation. You'll be looking for
> something like this in the output:
>
> -arch ppc -arch i386

Hmm, I don't see those. If this were a makefile situation, I'd have
some idea where to start poking further to find (or specify) these
flags. With setuptools, I haven't a clue -- what's the next step? Is
this something I can hack into setup.py, or what?

> Which tells the compiler to include these architectures in the resulting
> binary. As Chris already mentioned, you'll also need a universal
> Python--I'm assuming you've already got that...

Yes, I do seem to. And I can make an app (with py2app) that works fine
on PPC and Intel Macs, as long as it doesn't use mysql. So this appears
to be the last part of the puzzle.

Thanks,
- Joe

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T12:40:06Z

Christopher Barker wrote:

> sorry to hear that you are still struggling with this.

I appreciate the sympathy (and the help).

>> So: does anyone have a clue how I can convince setuptools to build a PPC
>> binary (or better yet, a Universal one) on an Intel machine?
>
> setuptools using distutils to build, and distutils should build a
> Universal binary if you run it with a Universal Python (the python .org
> one)

But that's what I was doing:

<http://www.dotancohen.com/howto/python-app-mac.html>

...unless there is some step I've missed?

>> This may or may not also be involved:
>> <http://bugs.python.org/setuptools/issue19>
>
> I don't think so. I think the issue there is with easy_install getting
> confused when you try to install a Universal binary.

That's how it seemed to me too.

> I'm not familiar with MySQLDB, but there are two issues at hand when
> building Universal extensions:
>
> 1) making the extension Universal -- that SHOULD be taken care of by
> distutils.

This appears to be the problem, I think.

> 2) making sure all the libs that the extension depends on are Universal
> -- you have to do this first, and it has nothing to do with setuptools,
> or distutils, or even python.

The only other extension involved, as far as I can tell, is wx, and that
one is already universal.

> It looks like you have a libmysqlclient dependency -- which makes sense
> -- you need to find a way to get a Universal one of those.

That's what I'm trying to figure out how to do. (libmysqlclient is the
library behind MySQLdb, as far as I can tell.)

> Best case:
>
> If the lib source has been tweaked to be able to build universal, you
> may be able to pass a flag like "universal" into configure, if you're
> really lucky, otherwise, sometimes passing in both arch=PPC and arch=x86
> or something like that can work.

What is this "configure" you speak of? MySQLdb doesn't use the
configure/make dance which is standard for Unix libraries; it uses
setuptools (which appears to be standard for Python libraries). If it's
using configure or make, it's doing so under the hood. Any idea how I
would specify universal or arch in this case?

> Next best case:
>
> You can pass in either PPC or x86 separately, building two versions and
> then lipo-ing them together.

Same question as above.

> Worst case:
>
> Some code can only be built for the architecture the compiler is run on,
> due to how they detect endianess, etc. In this case you need to build
> one on PPC, and one on Intel, and then move them to the same machine to
> lipo them together.

I suppose.

> The other complication is that you need to make sure to use the right
> SDK, if you want o build on 10.5 and allow it to run on 10.4.

I gave up on that one a while back -- all this is being done on a 10.4
(Intel) machine. I can do it all again on a PPC machine if necessary.

> Anyway, the short version is that I think you need to dig around the net
> for info on how to build libmysqlclient Universal -- hopefully someone
> has done it and distributes a binary, but presumably you've already
> looked for that.

This is exactly the question I was asking how to do. But you seem to
think that libmysqlclient is something other than MySQLdb. I'm under
the impression that it's the same thing. The only other library in my
"Frameworks" folder is libwx_macud-2.8.0.dylib, which I presume is
wxPython. (This one already is a universal binary.)

> One last note: usually, when folks want to distribute a python extension
> that depends on a lib that Apple does not provide, they build that lib
> statically, then link that version into their extension, so you don't
> have to worry about distributing it -- same issue with Universal, though.

I think you're still imagining libmysqlclient as being something MySQLdb
depends on, rather than the MySQLdb extension itself.

> I quick poking around tells me that MySQL themselves distribute Intel
> and PPC binaries separately -- I suspect you could get each of those,
> and pull the libs out and libo them together. This may be easier than
> building it yourself.

Maybe -- I got a UB of MySQL itself, so I don't think that's the
problem. (But of course it's entirely possible that I'm more confused
than I realize.)

> PS: I'm really surprised that no one seems to have done this already,
> and posted a binary egg or something! MySQLdb is not a minor package!

No kidding! I've spent more time futzing around with this than I have
writing the app itself. It's fairly ridiculous, and I'm now to the
point where I have to seriously consider whether it's worth continuing
this project in Python, or spend a day or two rewriting it in REALbasic.

I feel like I'm close, though -- if I can just figure out how to make a
UB of this libmysqlclient thing, I think I'll be there.

Thanks,
- Joe

P.S. While people have been very generous with their free help and
advice, if anyone could be more motivated to spend a few hours on it as
a paid consulting gig, I'd be happy to pay.

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T12:35:06Z

> MySQLdb instead uses setuptools.
>
> So: does anyone have a clue how I can convince setuptools to build
> a PPC
> binary (or better yet, a Universal one) on an Intel machine?

I just downloaded the mysqldb module from sourceforge to have a look
at how it decides how to compile its C extension. It looks like it's
getting the CFLAGS and LFLAGS from mysql_config. You'll need a
universal binary of libmysqlclient (as Chris already pointed out). At
any rate, you'll want to try to see what CFLAGS/LFLAGS were used to
compile libmysqlclient. You might try to run the following command in
terminal:

$ mysql_config --cflags

Which may shed some light on the situation. You'll be looking for
something like this in the output:

-arch ppc -arch i386

Which tells the compiler to include these architectures in the
resulting binary. As Chris already mentioned, you'll also need a
universal Python--I'm assuming you've already got that... Good luck.

~ Daniel

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

Re: How to get setuptools to build a Universal Binary?

2009-01-07T12:18:55Z

Joe,

sorry to hear that you are still struggling with this.

Joe Strout wrote:
> I'm (still) trying to make a neatly packaged Python app that works on
> both PPC and Intel Macs. All is good except for mysqldb; following the
> procedure I've documented at
> <http://www.dotancohen.com/howto/python-app-mac.html>, my app bundle
> contains an Intel-only binary of the mysqldb library
> (libmysqlclient_r.16.dylib).

> This page
> (http://developer.apple.com/opensource/buildingopensourceuniversal.html)
> at Apple suggests a possible solution: build separate Intel and PPC
> binaries, and then combine them with lipo.

that's actually pretty easy to do.

> So: does anyone have a clue how I can convince setuptools to build a PPC
> binary (or better yet, a Universal one) on an Intel machine?

setuptools using distutils to build, and distutils should build a
Universal binary if you run it with a Universal Python (the python .org one)

> This may or may not also be involved:
> <http://bugs.python.org/setuptools/issue19>

I don't think so. I think the issue there is with easy_install getting
confused when you try to install a Universal binary.

> Any advice will be greatly appreciated...

I'm not familiar with MySQLDB, but there are two issues at hand when
building Universal extensions:

1) making the extension Universal -- that SHOULD be taken care of by
distutils.

2) making sure all the libs that the extension depends on are Universal
-- you have to do this first, and it has nothing to do with setuptools,
or distutils, or even python.

It looks like you have a libmysqlclient dependency -- which makes sense
-- you need to find a way to get a Universal one of those.

That apple page you referenced should help guide you.

Best case:

If the lib source has been tweaked to be able to build universal, you
may be able to pass a flag like "universal" into configure, if you're
really lucky, otherwise, sometimes passing in both arch=PPC and arch=x86
or something like that can work.

Next best case:

You can pass in either PPC or x86 separately, building two versions and
then lipo-ing them together.

Worst case:

Some code can only be built for the architecture the compiler is run on,
due to how they detect endianess, etc. In this case you need to build
one on PPC, and one on Intel, and then move them to the same machine to
lipo them together.

The other complication is that you need to make sure to use the right
SDK, if you want o build on 10.5 and allow it to run on 10.4.

Anyway, the short version is that I think you need to dig around the net
for info on how to build libmysqlclient Universal -- hopefully someone
has done it and distributes a binary, but presumably you've already
looked for that.

One last note: usually, when folks want to distribute a python extension
that depends on a lib that Apple does not provide, they build that lib
statically, then link that version into their extension, so you don't
have to worry about distributing it -- same issue with Universal, though.

I quick poking around tells me that MySQL themselves distribute Intel
and PPC binaries separately -- I suspect you could get each of those,
and pull the libs out and libo them together. This may be easier than
building it yourself.

A couple helpful pages you've probably already found:

http://dev.mysql.com/downloads/mysql/5.1.html#macosx-dmg
http://developer.apple.com/internet/opensource/osdb.html
http://davidmichaelthompson.com/?p=12

I hope that helps,

-Chris

PS: I'm really surprised that no one seems to have done this already,
and posted a binary egg or something! MySQLdb is not a minor package!

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

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

How to get setuptools to build a Universal Binary?

2009-01-07T11:47:24Z

I'm (still) trying to make a neatly packaged Python app that works on
both PPC and Intel Macs. All is good except for mysqldb; following the
procedure I've documented at
<http://www.dotancohen.com/howto/python-app-mac.html>, my app bundle
contains an Intel-only binary of the mysqldb library
(libmysqlclient_r.16.dylib).

This page
(http://developer.apple.com/opensource/buildingopensourceuniversal.html)
at Apple suggests a possible solution: build separate Intel and PPC
binaries, and then combine them with lipo. But of course that's using
Makefiles. MySQLdb instead uses setuptools.

So: does anyone have a clue how I can convince setuptools to build a PPC
binary (or better yet, a Universal one) on an Intel machine?

This may or may not also be involved:
<http://bugs.python.org/setuptools/issue19>

Any advice will be greatly appreciated...

Thanks,
- Joe

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

Re: How to install latest 2.5 in OS X 10.4?

2009-01-07T08:13:08Z

On 30-Dec-08, at 4:26 PM, Joe Strout wrote:

> We've gotten most of this mostly working on 10.5 Intel, but now to
> make a properly portable app, I need to go back and do it all again
> on a 10.4 machine. I'm stuck on step 1.

If you're using the Python.org build of python, it's built against the
10.4u SDK, so the apps you build should be portable to any 10.4
machine, even if built on 10.5. What error are you encountering when
you try to run the 10.5-built app on 10.4?

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

Re: py2app: Bombing on unknown load command 27

2009-01-05T16:38:42Z

Joel Gluck wrote:
> Chris, here's the setup script (which I run in my cwd, containing the
> main program I'm creating an app out of, "savi.py"). TIA for your
> diagnosis, doc! -- Joel*

that all looks pretty normal.

oh, you do run it as:

$python setup.py py2app

don't you?

One note:

>>> One more related question on this -- when I run my setup script, the
>>> following 4 eggs appear in my cwd:
>>> *altgraph-0.6.7-py2.5.egg*
>>> *modulegraph-0.7-py2.5.egg*
>>> *bdist_mpkg-0.4.3-py2.5.egg*
>>> *macholib-1.1-py2.5.egg*

I still have no idea why those eggs get into you dir, but I'm running
macholib 1.2:

>>> import macholib
>>> macholib.__version__
'1.2'

so it looks like you haven't succeeded in fully upgrading py2app and all
its dependencies.

The mackolib upgrade may help your unknown load command error.

-Chris

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

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

Re: py2app: Bombing on unknown load command 27

2009-01-05T15:39:15Z

Chris, here's the setup script (which I run in my cwd, containing the main program I'm creating an app out of, "savi.py"). TIA for your diagnosis, doc! -- Joel

import os

from setuptools import setup

print os.system(r'sudo rm -rf mac_build mac_dist savi_log.txt')

APP = ['savi.py']

DATA_FILES = ['../gameplay', 'data', 'en']

OPTIONS = { 'argv_emulation': True,

"iconfile": "icons/mac_savi_icon.icns",

"dist_dir":"mac_dist",

"bdist_base":"mac_build",

"frameworks": ["SDL_image.framework", "SDL_ttf.framework", "SDL_mixer.framework", "SDL.framework"],

"includes":["Numeric"] }

setup( app=APP,

data_files=DATA_FILES,

options={'py2app': OPTIONS},

setup_requires=['py2app'],

version="0.2.3" )

print os.system(r'sudo rm -rf mac_dist/savi.app/Contents/Frameworks/*.*')

print os.system(r'sudo cp -R mac_frameworks/*.* mac_dist/savi.app/Contents/Frameworks')

A Couple of Notes on the Above:

1) The py2app "frameworks" option doesn't work for multiple items, which is why I end up copying the frameworks into the app manually at the end -- I keep a copy of them in a special folder...)

2) This script always bombs in setup() -- here's the error:

File "build/bdist.macosx-10.3-i386/egg/macholib/MachO.py", line 178, in load

raise ValueError("Unknown load command: %d" % (cmd_load.cmd,))

ValueError: Unknown load command: 27

> /Users/joel/Documents/OT Video Games/SAVI Learning Tool Prototype ver 2.3/build/bdist.macosx-10.3-i386/egg/macholib/MachO.py(178)load()

Perhaps it never gets to delete the eggs because it bombs? Although I do tell Pdb to "cont" and it seems to exit normally... -- Joel

On Jan 5, 2009, at 6:14 PM, Christopher Barker wrote:

Joel Gluck wrote:
Hi Chris,
One more related question on this -- when I run my setup script, the following 4 eggs appear in my cwd:
*altgraph-0.6.7-py2.5.egg*
*modulegraph-0.7-py2.5.egg*
*bdist_mpkg-0.4.3-py2.5.egg*
*macholib-1.1-py2.5.egg*
Why is this happening?

those are the py2app dependencies -- why in the world you'd get them in your cwd is beyond me.

When you say "my setup script" -- do you mean your setup.py that is supposed to build your app?

post it, and we'll see if there is anything weird about it.

Is it safe to have my script just delete these when I'm done?

I would think so, but I don't know why they are there at all.

-CHB

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA 98115       (206) 526-6317   main reception

Chris.Barker@...

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