[PD] externals naming conventions
christof.ressi at gmx.at
Fri Jan 24 18:48:49 CET 2020
check out sys_dllextent() in s_loader.c. Here's a summary:
CPU architecture suffixes:
x86_64 (Intel 64-bit): "amd64"
i386 (Intel 32-bit): "i386"
ARM 64-bit: "arm64"
Then you just combine the two, e.g. ".m_amd64" for 64-bit (Intel) binaries on Windows or ".l_i386" for 32-bit (Intel) binaries on Linux
Finally there are the generic, architecture independent extensions:
Linux/FreeBSD: ".pd_linux", ".so"
macOS: ".pd_darwin", ".d_fat", ".so"
OpenBSD: ".pd_openbsd", ".so"
I don't think this is supported.
> Gesendet: Freitag, 24. Januar 2020 um 18:20 Uhr
> Von: "Orm Finnendahl" <orm.finnendahl at selma.hfmdk-frankfurt.de>
> An: pd-list at lists.iem.at
> Betreff: [PD] externals naming conventions
> does anybody have infos about naming conventions for different
> formats of binary externals and their loading priority?
> I'm aware of the following extensions:
> *.l_ia64 (64-bit)
> *.l_i386 (32-bit)
> *.pd_linux (indifferent of bitsize?)
> Are there any conventions for distinguishing 32-bit and 64-bit on OSX
> and Windows? Is there a recommended way?
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
More information about the Pd-list