On Sat, Oct 8, 2011 at 12:08 AM, Hans-Christoph Steiner hans@at.or.at wrote:
I think this is caused by using the 10.6 build on 10.5. It is only partially compatible.
Pd-0.43.1-extended-20111002.app, an x86_64 build, tries to load libs from Pd-extended.app which is an i386 build. That's where the message 'wrong architecture' comes from.
In Pd-0.43.1-double-20111007.app, objects from iemlib and other libs can be perfectly instantiated with namespaces. There's no compatibility problem, the extended objects are working as usual. Because it's all single precision still..... It's compiled with PD_FLOAT_PRECISION 32, the core code as well.
Shall we not better start another repo with a clone of the full pd-extended.git to work on?
Katja
On Oct 7, 2011, at 8:13 PM, katja wrote:
On Sat, Oct 8, 2011 at 12:08 AM, Hans-Christoph Steiner hans@at.or.at wrote:
I think this is caused by using the 10.6 build on 10.5. It is only partially compatible.
Pd-0.43.1-extended-20111002.app, an x86_64 build, tries to load libs from Pd-extended.app which is an i386 build. That's where the message 'wrong architecture' comes from.
In Pd-0.43.1-double-20111007.app, objects from iemlib and other libs can be perfectly instantiated with namespaces. There's no compatibility problem, the extended objects are working as usual. Because it's all single precision still..... It's compiled with PD_FLOAT_PRECISION 32, the core code as well.
Shall we not better start another repo with a clone of the full pd-extended.git to work on?
Ok, I figured out why the nightly auto-builds were always 32-bit. The whole Pd-extended build sets CFLAGS= when calling make, and the precision was being set in ./configure in CFLAGS, so it was being overridden by the 'make CFLAGS="-O2 -g"'. I changed it to use AC_DEFINE so its set in DEFS, and now CFLAGS is not overriding it. So tomorrow's build should actually be 64-bit.
.hc
----------------------------------------------------------------------------
"We have nothing to fear from love and commitment." - New York Senator Diane Savino, trying to convince the NY Senate to pass a gay marriage bill
On Sat, Oct 8, 2011 at 11:37 PM, Hans-Christoph Steiner hans@at.or.at wrote:
Ok, I figured out why the nightly auto-builds were always 32-bit. The whole Pd-extended build sets CFLAGS= when calling make, and the precision was being set in ./configure in CFLAGS, so it was being overridden by the 'make CFLAGS="-O2 -g"'. I changed it to use AC_DEFINE so its set in DEFS, and now CFLAGS is not overriding it. So tomorrow's build should actually be 64-bit.
Hans, Pd-0.43.1-double-20111009-macosx106-x86_64.dmg has double precision indeed, it shows 'PD_FLOATPRECISION = 64 bits' at startup and core objects work correctly. At the moment I can not verify that externals are also built in double precision. There's a lot of nonsensical output from objects but this may be caused by their code as well. We're facing a period of intensive bugfixing, that's for sure.
Double precision Pd extended is now a mutant. Part of it's DNA has changed and it's crippled. In fact it is in a disastrous state, but still I'm as excited as when I saw double precision in my own builds for the first time. I hope the project will survive impatience, disappointments and distractions.
Katja