I prefer the source code approach because often enough, it's easy enough for 
users who build Csound to update their dependendency sources to get up to 
date code. Otherwise, they'd have to wait for a Csound developer to rebuild 
the library or whatever in CVS.

Regards,
Mike

----- Original Message ----- 
From: "Steven Yi" 
To: 
Sent: Sunday, December 04, 2005 4:42 AM
Subject: Re: [Csnd] OSC mingw


I don't like copying in source trees if possible; maybe it's simple
enough to just create a nother repository in the CVS for dependencies.
 Any binary could go there; it's easy to maintain in CVS but then also
out of the main csound CVS repository.  What does everyone think?

steven


On 12/3/05, Michael Gogins  wrote:
> I agree. No prebuilt third party libraries. However, it would be nice to
> have BUILD SYSTEMs for things that are hard to build, or at least
> INSTRUCTIONS.
>
> I don't mind adding build systems to SConstruct for things like liblo. 
> It's
> only necessary on Windows or OS X, usually.
>
> I suggest the convention of simply copying source trees into the opcode
> subdirectory in such cases, as with Loris and STK.
>
> Regards,
> Mike
>
> ----- Original Message -----
> From: "Istvan Varga" 
> To: 
> Sent: Saturday, December 03, 2005 4:51 AM
> Subject: Re: [Csnd] OSC mingw
>
>
> > On Friday 02 December 2005 20:06, James Hearon wrote:
> >
> >> Also still not sure why mingw doesn't like the original cvs
> >> csound5/windowsdlls/liblo.a
> >
> > Which is another reason to remove it from CVS.
> > --
> > Send bugs reports to this list.
> > To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
> >
>
>
> --
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>
-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk