On Oct 4, 2011, at 7:06 PM, katja wrote:
Forgot to mention this: at start up there's a logpost (level 3) 'PD_FLOATPRECISION=32 bits' for single and 'PD_FLOATPRECISION=64 bits' for double build.
Ah, so tomorrow a single and double precision build will automatically be made? Cool.
It's confusing. At the moment there is vanilla Pd patched to work in double precision. But for Pd-extended it is: a single precision Pd-extended with double-ready core code. Not a double precision Pd-extended, not even double-ready Pd-extended. Let's better call it something like Pd-0.43.1-single-20111004-macosx106-x86_64.dmg etc., Hans?
Its a dev branch to test the double stuff, so its going to be messy, unless someone wants to clean up the scripts. Pd-extended is still using 32-bit floats for t_float and t_symbol. The pd-double build will have some vestiges of the 'extended' name in it, because the build scripts are crufty and kludgey and should be replaced. But they work.
So you are saying that the stuff in pd-double is not building using 64- bit floats? Let's get a github repo going so we can work on this stuff. Unless you want to, I'll happily set one up at:
https://github.com/pd-projects/pd-double
And add people who are interested in working on it. Or do you want to maintain your own git repo that we submit patches to?
.hc
----------------------------------------------------------------------------
You can't steal a gift. Bird gave the world his music, and if you can hear it, you can have it. - Dizzy Gillespie