Hi Simon, Here is my usage (from a tcsh script):
set faustCompiler = "/usr/local/bin/faust" set faustOptions = "-scn $parentClass -a $archfile -cn $outputName -inpl -uim -i" ... $faustCompiler $faustOptions $dspfile -o $dest/$outputFile I think the most important option for you is -cn, but I'm not sure since you don't show your naming conflicts (others are possible). I agree --namespace has problems and I don't use it myself. - Julius On Mon, Nov 7, 2022 at 3:49 AM Simon Hill <cont...@simonhill.fr> wrote: > Hello, > > I’m following the « Faust for the confined » tutorial ( > https://faustdoc.grame.fr/workshops/2020-04-10-faust-juce/) to integrate > faust dsp into a Juce application using « faust -i -a faustMinimal.h > FaustEffect.dsp -o Effect/Source/FaustEffect.h » > I’m able to integrate the example echo effect in my app, but when I try to > integrate other effects I run into naming conflicts. > Searching the compiler manual, I see there is a « --namespace <name> » > option, which sound like it would solve my problem. > However this only adds a namespace around all the generated code, > including the includes, which prevents compilation. > > The solution I found is adding a namespace by hand around every class in > FaustEffect.h, but I don’t really understand everything in this file and > would prefer not to change it by hand for each effect that I will need. > > So here is my question : *Is this the proper approach to integrate > multiple separate effects inside a Juce application ?* > > Thank you > > Simon > > _______________________________________________ > Faudiostream-users mailing list > Faudiostream-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/faudiostream-users > -- "Anybody who knows all about nothing knows everything" -- Leonard Susskind
_______________________________________________ Faudiostream-users mailing list Faudiostream-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-users
