Sorry for the second question, now read the pd-lib-builder README. It states that 64-bit externals will indeed get a different name.
On 12/6/23 10:21, Lucas Cordiviola wrote:
there is a name convention to support both float types in the same path.
https://msp.ucsd.edu/Pd_documentation/x4.htm#s1.2.1
If you are using lib-pd-builder see:
https://github.com/pure-data/pd-lib-builder/blob/master/tips-tricks.md#build...
--
Mensaje telepatico asistido por maquinas.
On 06/12/2023 05:12, Roman Haefeli wrote:
On Wed, 2023-12-06 at 09:43 +0200, Alexandros Drymonitis wrote:
The question now is how to have both versions run happily side by side? On the 64-bit version I did find zexy (but some other libraries I searched for, including my own, neuralnet, were not available - not a surprise for my own, I haven't compiled it for the 64-bit version), but installing it through deken, breaks compatibility with the 32-bit version (I guess it overrides it).
You could configure different install and search paths for single- and double-precision versions of Pd. I don't know if they share the config file. If they do, you would have to adjust the config whenever you switch between them.
So when I open the 32-bit version, zexy is no longer available. If I install it through deken from the 32-bit Pd, then it's not available for the 64-bit Pd.
Another question is, how to compile externals for 64-bit Pd? I would like to offer [neuralnet] for this version too.
Just compile it against the m_pd.h of the double-precision edition of Pd. That's not a very qualified statement, though. I haven't tried it myself yet. And from what I read about the topic, not all sources are compatible with Pd64 right away.
Roman
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list