I should have added, my build system was only for the Csound API. I did not
build FLTK widgets (or at least not ones that worked), I did not build the
auxiliary programs - just a csound library and a csound console binary.

Original Message:
-----------------
From:  ramsdell@mitre.org (John D. Ramsdell)
Date: 05 Nov 2003 11:46:09 -0500
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3289] Re: ccsound.c


"gogins@pipeline.com"  writes:

> Thanks for your thoughts. Here's my response.
> 
> I used to have a configure.in, Makefile.am, autoconf, automake,
> libtool build system for Csound 4. I only used it on Linux and I
> dropped it because I needed to focus on SourceForge Csound. (Working
> on 2 builds for Csound was a real nightmare, especially because I
> would get stuff working in my build that was not adopted, or not
> quickly adopted, by the "canonical" build. Getting Csound under LGPL
> and into SourceForge CVS has been a GOD-SEND for me!)

Well gee, it sounds to me as if Michael has already solved our
configuration problems.  All others, is there any reason we shouldn't
let Michael do his magic on the csound5 module?  I say we step aside
and let him go!

John


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

FLTK is being pushed out to an Opcode Library, at least, that's what I
thought the concensus was and was planning to start on next.  The
utilities can be added later.

Your build system would be a great starting point, IMO.

steven

On Wed, 2003-11-05 at 09:55, gogins@pipeline.com wrote:
> I should have added, my build system was only for the Csound API. I did not
> build FLTK widgets (or at least not ones that worked), I did not build the
> auxiliary programs - just a csound library and a csound console binary.