[PD-dev] pd-double: how to selectively build external libs for development?

[IOhannes m zmoelnig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-10-17 22:27, katja wrote:

> There's however a small issue to reckon with: at the moment, the only
> way to force double precision compilation upon the external libs, is
> to hardcode #define PF_FLOAT_PRECISION 64 in m_pd.h. If we put it in

i think this is the only solution on the long way anyhow.

when building an external for a given Pd-binary, there is no way to tell
whether it was a single or double precision build (apart from checking
whether the resulting external produces nonsense or even crashes).
the only reference is the include file, which must be non-ambiguous.

fgmasdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6dIowACgkQkX2Xpv6ydvRvGACgzFA5WQ5re+2f3iSCTOiLjtJ6
B+wAnAg172TMkK9H52Pop5oEKuu9LxaC
=YHLC
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20111018/d1118811/attachment.bin>