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 folder.

2) /usr/local/include/SuperCollider/include » also added in the list of 
searched headers 

Available on  the « master-dev » branch for now :  can you test and report?

Thanks.

Stéphane 


> Le 8 mars 2017 à 03:03, Florian Grond <floriangr...@gmail.com> a écrit :
> 
> 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, there is the following section:
> 
>     # compile the .dsp file to c++ and xml
>     faust -xml -time -t 0 "$SRCDIR/$f" -o /dev/null  || exit
>     mv "$SRCDIR/$f.xml" $TMP/
>     faust -i -a supercollider.cpp -time -t 0 $OPTIONS "$SRCDIR/$f" -o 
> "$TMP/${f%.dsp}.cpp" || exit 
> 
> 
> My understanding is that:
>   faust -i -a supercollider.cpp ...
> generates the cpp file 
> 
> in the architecture file supercollider.cpp
> 
> I find in line 545:
> 
> #if !defined(NDEBUG)
>         Print("Faust[%s]:\n", g_unitName);
>         Print("    Inputs:   %d\n"
>               "    Outputs:  %d\n"
>               "    Callback: %s\n",
>               numInputs, numOutputs,
>               unit->mCalcFunc == (UnitCalcFunc)Faust_next ? "zero-copy" : 
> "copy");
> #endif
> 
> and in 620:
> 
> #if !defined(NDEBUG)
>     Print("Faust: %s numControls=%d\n", name.c_str(), g_numControls);
> #endif // NDEBUG
> 
> These are exactly the debug messages popping up from scsynth  in the scide 
> window 
> 
> I can't find however in  supercollider.cpp
> 
> #if !defined(NDEBUG) & defined(SC_API_EXPORT)
>     Print("Faust: supercollider.cpp: sc_api_version = %d\n",sc_api_version);
> #endif
> 
> 
> The reason why it would be cool to have the .cpp with the debug messages 
> disabled is because then SC3plugin development committing them to the public 
> plugin repository is possible. I can correctly compile the plugins for OSX 
> and Pierre did so for Linux (both of which we could possibly also do with 
> Faustlive) but we need the non-debug  .cpp files to compile it for Windows so 
> as to serve all 3 platforms. 
> 
> Thanks,
> 
> Florian
> 
> 
> 
> 
> 
> www.grond.at
> 
> On Tue, Mar 7, 2017 at 5:06 PM, Stéphane Letz <l...@grame.fr> wrote:
> 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 <floriangr...@gmail.com> a écrit :
> >
> >
> > 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_interface is found
> >
> >
> > #-------------------------------------------------------------------
> > # Need SuperCollider 'plugin_interface' include path to compile UGens:
> >
> > SC0=$SUPERCOLLIDER_HEADERS
> > SC1="/usr/local/include/SuperCollider/include"
> > SC2="/usr/local/include/supercollider"
> > SC3="/usr/include/SuperCollider"
> > SC4="/usr/include/supercollider"
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > //    #if !defined(NDEBUG)
> > //            Print("Faust[%s]:\n", g_unitName);
> > //            Print("    Inputs:   %d\n"
> > //                  "    Outputs:  %d\n"
> > //                  "    Callback: %s\n",
> > //                  numInputs, numOutputs,
> > //                  unit->mCalcFunc == (UnitCalcFunc)Faust_next ? 
> > "zero-copy" : "copy");
> > //    #endif
> >
> >
> >
> >
> > // #if !defined(NDEBUG)
> > //    Print("Faust: %s numControls=%d\n", name.c_str(), g_numControls);
> > // #endif // NDEBUG
> >
> >
> >
> > // #if !defined(NDEBUG) & defined(SC_API_EXPORT)
> > //    Print("Faust: supercollider.cpp: sc_api_version = 
> > %d\n",sc_api_version);
> > // #endif
> >
> >
> >
> >
> > www.grond.at
> >
> > On Tue, Mar 7, 2017 at 1:06 PM, Stéphane Letz <l...@grame.fr> wrote:
> > 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 <floriangr...@gmail.com> a écrit :
> > >
> > > 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 compile the 
> > > repository, I get debug output from the Faust based plugins when I launch 
> > > the server and when I launch a synth.
> > > Is there a way to avoid this debug setting when compiling the SC3plugins 
> > > or can I suppress the debug info when generating the CPP files from Faust 
> > > code?
> > >
> > > Kind regards,
> > >
> > > Florian
> > >
> > >
> > >
> > >
> > > www.grond.at
> > > ------------------------------------------------------------------------------
> > > Announcing the Oxford Dictionaries API! The API offers world-renowned
> > > dictionary content that is easy and intuitive to access. Sign up for an
> > > account today to start using our lexical data to power your apps and
> > > projects. Get started today and enter our developer competition.
> > > http://sdm.link/oxford_______________________________________________
> > > Faudiostream-users mailing list
> > > Faudiostream-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/faudiostream-users
> >
> >
> 
> 


------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Reply via email to