The whole point of plugins is... plug-in: not having to recompile or even have the Csound sources. In fact you only need the headers, not even linking to CsoundLib is needed.
The SConstruct thing is misleading. It is supposed to be a convenience to use it, but given that it's only about one short gcc command-line, it's hardly worth it. Note also that Steven has produced an SDK for plugins, which could be used alternatively.
Victor
----- Original Message -----
From: Jacob Joaquin <jacobjoaquin@gmail.com>
Date: Thursday, July 22, 2010 6:12 pm
Subject: Re: [Cs-dev] plugins
To: Developer discussions <csound-devel@lists.sourceforge.net>
> On Thu, Jul 22, 2010 at 10:04 AM, matt ingalls
> <matt@sonomatics.com> wrote:
> > the real problem is the manual "adding a plugin..." section
> really makes it look like
> > the only option is to:
> > 1-3) compile your plugin
> > 4) change sconstruct
> > 5) recompile csound
>
> That's precisely how I read it, and is the reason why I've put off
> writing plugins for Csound for so long. Know that I know this isn't
> the case, I'll be writing some plugins in the near future.
>
> Best,
> Jake
> --
> The Csound Blog - http://csound.noisepages.com/
> Slipmat - http://slipmat.noisepages.com/
>
> -----------------------------------------------------------------
> -------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
National University of Ireland, Maynooth