I too am relatively new to Faust but I will try to shed some light on this.
Whatever executable you are running to compile faust code to a pd binary will be generating C++ code as an intermediate step. If this is what you want to get your hands on, it should be possible. The various faust2... executables are mostly just bash scripts, so it's not too difficult to modify their behaviour. If you are on a unix-y system, you can find out the path of the script in question by running 'which faust2puredata' (or whichever script it is you are interested in). I would suggest making a copy of script in your local directory, opening it in your text editor, and removing the step at the end which deleted the temporary interim files (in faust2puredata, that's the couple of lines which start rm -rf... near the end of the file). You might also want to just adjust it to output to the current directory, or one of your choice, instead of to a temporary directory as it appears to now. And if you make a copy of the script, remember to make the copy executable with chmod u+x. I'm not 100% sure I have understood your question correctly, but if I have, I hope the above will give you enough to get started. On 10/9/19, Johannes Mario Ringheim <j...@ringheimsauto.org> wrote: > Please excuse this possibly noob'ish question, I have been coding in > Faust for only a couple of weeks. > > Is it possible to compile Faust .dsp code to PD external C source code, > as opposed to binary? > > The reason I want to do this is that I am running a PD patch as part of > an Android application, and some of the PD externals will be written in > Faust. I have set up a build system for Android which compiles other PD > externals also, and I would like the ones made in Faust to be compiled > along with them. > > I have been translating the Faust .dsp code by hand from the output of > the C++ code generated in the web editor to PD external code. It is > absolutely doable but quickly gets old. > > faustgen~ is not a preferrable option since I would rather not have > another thing which can go wrong running in the Android app. > > Thanks for any suggestions. > > > _______________________________________________ > Faudiostream-users mailing list > Faudiostream-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/faudiostream-users > _______________________________________________ Faudiostream-users mailing list Faudiostream-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-users