I still wonder if there's an easy way to just incorporate all of these libs inside the external binary.
Do you mean static linking? Depends on the dependencies. Some are available as a static library and others are not.
In my "aoo" Pd external, I use the "opus" library, which can be built both as a static and shared library. My build system supports both dynamic and static linking for each dependency. The versions I upload on Deken are all linked statically (i.e. a single binary). For distribution via a system package manager, however, I would choose dynamic linking, since in that case the dependencies are supposed to be installed system-wide.
Personally, I strongly prefer static linking for plugins (like Pd externals). The downside is that you're responsible for providing the correct linker flags, since a static library is just an archive of object files. For complex dependencies, you're better off with linking dynamically and shipping them along side your library.
Christof
On 05.01.2021 23:35, Alexandre Torres Porres wrote:
Em ter., 5 de jan. de 2021 às 19:28, Alexandre Torres Porres <porres@gmail.com mailto:porres@gmail.com> escreveu:
Not that it makes that much of a difference just getting rid of these two out of so many.I still wonder if there's an easy way to just incorporate all of these libs inside the external binary. that would really make it cleaner. But if we have to settle with this, it's fine also...
I mean, it's been mentioned here as an alternative, but I wonder if it's too much hassle and if we'll need to exchange another dozen of emails until I get what I need to do... or until I give up again :)
cheers
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list