OK : See
https://github.com/grame-cncm/faust/commit/b3bdfb9c6ea37d36e23324522efd7697729832ab
1) I added a new explicit -dm (= debug messages) in faust2supercollider to
explicitly activate debug messages in the generated plugin, separated forth -d
parameter that keeps the intermediated created
Stéphane,
not sure I can provide a patch (so far I have manually commented out the
debug messages in the cpp files), but I tried to have a closer look to
where the DEBUG messages come from.
I guess a
#define NDEBUG
in supercollider.cpp might do the trick
In the faust2supercollider script, ther
Would be great if this could be a compilation flag for faust2supercollider :
Can you possibly provide a patch for that?
Thanks.
Stéphane
> Le 7 mars 2017 à 21:47, Florian Grond a écrit :
>
>
> Thanks, Stéphane, for the hint, for now, I just commented out the debug
> settings in the C++
Thanks, Stéphane, for the hint, for now, I just commented out the debug
settings in the C++ files.
Would be great if this could be a compilation flag for faust2supercollider
Best, Florian
I also always need to change this line:
SC1="/usr/local/include/SuperCollider/
so that the plugin_interfac
You may have to hack the faust2supercollider script, see how F2SC_DEBUG flag is
used, and possibly play with DNDEBUG also.
Stéphane
> Le 7 mars 2017 à 18:50, Florian Grond a écrit :
>
> Dear list,
>
> I am currently trying to put together SC3plugins based on Faust.
> When I compile the .dsp
Dear list,
I am currently trying to put together SC3plugins based on Faust.
When I compile the .dsp files using the faust2supercollider script, all
works fine.
When I try to keep the .cpp file by using the -d flag so that I can later
add the .cpp + .sc files to the SC3plugins repository and compi
