It looks like you're new here. If you want to get involved, click one of these buttons!
Hello, this question is about building vanilla pd (and libpd) from source to use on an embedded processor.
I am interested in using libpd on an embedded DSP processor, specifically, an Analog Devices SHARC DSP (266 MHz, native floating point), a part I’m familiar with. I’ve read the instructions and tutorials available for getting started with libpd, but some things are still not clear to me, and some instructions remain unclear for my purposes.
First, most of the instructions for using libpd are understandably focused on iOS and Android, and typically involve executing some sort of makefile command to kick off some initial compilation. Since I want to use libpd on an embedded processor with its own unique compiler/linker, it seems like I’ll need to build vanilla pd / libpd without these makefiles, and instead directly from source in the tools for the DSP.
I haven’t been able to find instructions on how best to do this. For example, I’ve had success using the embeddable scripting language Lua follow these instructions (http://www.lua.org/manual/5.2/readme.html#other ) which indicate how to build the Lua library, compiler, and interpreter from source if you want to run in a native C, but not Window/Linux environment. Are there similar instructions for building pd/libpd?
A second more general question I have is in regards to vanilla pd, and the version of pd supplied with the libpd source. I assume that typical vanilla pd source includes basic graphics source files necessary for using pd in the typical way, but the vanilla pd source supplied with libpd removes this, and only includes the audio processing/messaging/etc source. Is this accurate? Can I build vanilla pd from the source supplied with libpd by itself, or must the libpd layer also be included?
Thanks for any help or information you can provide to point me in the right direction!