I was more thinking about a tool that would determine platforms were the
distribution would work by fetching database containing an historic of
all pd functions, internals, externals, and abstractions.
Then the distribution provider would know if it works on other
platforms, and why it wouldn't work, eventually advising the use of some
objects and methods over some other to be compatible everywhere, .
Of course deken could be used at the other end for providing the missing
objects.
Building pd wouldn't resolve many cases were some functions aren't
compatible between different platforms.
Le 28/07/2017 à 00:41, Fede Camara Halac a écrit :
Of course a pd patch is in itself platform independent, which is what allows
one to bring patches to diff platforms.
For externals, my guess is that you can ask deken to fetch the corresponding
binary for the target platform and use that in the exported bundle.
I dont understand, though, how from pd in one platform you would build pd for another.
Or, perhaps you dont need to build and you need only to fetch the corresponding build
from Miller's builds and put the libs in the "extra" (as suggested in the deken
path github discussion)
Are Miller's builds dekenizable for that matter?
fdch.github.io/tv
On Jul 27, 2017, at 5:57 PM, patrice colet <colet.patr...@free.fr> wrote:
functions in pd headers
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
