What is the concrete problem you are facing ? Thanks.
Stéphane > Le 11 oct. 2021 à 21:59, Scott Tooby <scott.to...@gmail.com> a écrit : > > Yes, +1. I'm interested in this too to make it easier to integrate FAUST > generated C++ code into JUCE or other C++ codebases. Similarly, I've noticed > only a single .cpp file is generated when exporting FAUST code to pure C++ > source code (not the JUCE option), so in this case too it would be handy if a > separate .h file was exported alongside the .cpp file. But if there is > already a way to do this via the export process I'd appreciate being pointed > in the right direction. > > Thank you, > Scott Tooby > > On Mon, Oct 11, 2021 at 12:38 PM Steven Kraninger <skranin...@gmail.com> > wrote: > All, > > The current faust2juce script generates a single FaustPluginProcessor.cpp > file. I would like to have separate .h and .cpp files rather than copying > them all inline into one .cpp file. I feel this would make it a bit easier to > modify the program and add new features after generating it (in particular > for the saving of plugin presets and modification of the UI). > Is there any way to do this? > > Thanks > Steven Kraninger > > _______________________________________________ > 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 _______________________________________________ Faudiostream-users mailing list Faudiostream-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-users
