Hans-Christoph Steiner wrote:
On Nov 26, 2007, at 3:43 AM, IOhannes m zmoelnig wrote:
.pd_darwin is still supported for legacy externals.
Pd-extended only builds objects using .pd_darwin as an extension. It
works fine for i386, PowerPC, and universal binaries.
but then, pd-extended
On Nov 27, 2007, at 3:34 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
On Nov 26, 2007, at 3:43 AM, IOhannes m zmoelnig wrote:
.pd_darwin is still supported for legacy externals.
Pd-extended only builds objects using .pd_darwin as an extension.
It works fine for i386,
Alexandre Quessy wrote:
Hi,
On OSX, how can we build universal binaries for externals ?
If not possible, both ppc and intel architecture use the .pd_darwin suffix...
this is not fully true.
the new (as with pd-0.41, probably even 0.40) extensions for externals
on os-x are:
.d_ppc: darwin
Hi,
On OSX, how can we build universal binaries for externals ?
If not possible, both ppc and intel architecture use the .pd_darwin suffix...
Thanks,
--
Alexandre Quessy
http://alexandre.quessy.net
http://www.puredata.info/Members/aalex
___
Hi,
On OSX, how can we build universal binaries for externals ?
If not possible, both ppc and intel architecture use the .pd_darwin suffix...
the easiest approach is to make separate externals for each architecture
(like ppc, ppc64, i386) and glue them together with lipo.
lipo -create
Thanks Thomas !
Is this what is done in pd-extended ? I guess not.
a
2007/11/25, Thomas Grill [EMAIL PROTECTED]:
Hi,
On OSX, how can we build universal binaries for externals ?
If not possible, both ppc and intel architecture use the .pd_darwin
suffix...
the easiest approach is to
You can skip the lipo step, gcc will do it for you if you provide the
right flags. You can also include 64-bit in there. If you want to
do specific optimizations for each CPU, then you'll have to build
each separately and use lipo to assemble them all into one.
CFLAGS=-arch i386 -arch
