In the 4.23 Csound directory is a .dev file for Dev-C++ on Windows that
will generate a Makefile.win for libcsound.a (the Csound API). This might
possibly serve as a starting point for making a Linux build of the API for
Csound 5.

When I create Linux or Unix builds these days, I generally start by writing
a Makefile.am (which is quite simple) and go from there. This does not seem
to have been the approach used for Csound, perhaps because people were not
familiar with autoconf/automake (not that I am that familiar with it
myself!), perhaps because Csound has so many configuration choices. 

In fact, I think Csound has far too many configuration choices. In Csound5,
I would prefer a single build of totally platform-neutral C code for the
engine. I think it should be possible to build the entire engine without
any platform-specific macros or system calls, using just the C runtime
library.

I would prefer that all I/O except for reading sco and orc files (i.e. MIDI
input and output, soundfile input and output, and real-time audio input and
output) and all non-open-source opcodes be in plugins that implement
abstract interfaces.

Anyway, I guess I would try to put the files from the Makefile.win for
libcsound.a, adjusting to suit the new arrangement of files in Csound 5,
into a new Makefile.am and go from there.

This should make it possible to use Makefile.am's for building everything
on all platforms without having to develop a skilled understanding of the
autoconf/automake system (I think!).

Original Message:
-----------------
From:  ramsdell@mitre.org (John D. Ramsdell)
Date: 17 Oct 2003 07:47:01 -0400
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3168] Re: New commits for CsoundVST


"Michael Gogins"  writes:

> I am pleased to report that I was able to rebuild CsoundVST on
> Windows with the latest Csound 4.23 sources from CVS.

Good news.

> I have committed two minor changes to the Csound sources. 
...

Please be sure to list your changes in the ChangeLog.  John ffitch has
been so good about listing his, and we should be too.

I have not had much luck playing with the beta in the csound5 module.
My plan was to create a CSound library, link it with the little driver
program I've shared on this list, and then run it under the memory
profiler that comes with a Red Hat 9 system.  I found out the profiler
generates a leak report I can share with developers.

When I went to build the library, the configure script in the csound5
module failed to detect I did not have FLTK installed, and configured
csound5 to use it anyway.  When I told the configure script FLTK was
missing, it still tried to use it until I told it to build without a
gui, however, my troubles were still not over.  It selected X11 to
draw graphs, but POLL_EVENTS is never defined in that configuration.
Worse yet, when I typed "make csound.a" to create the library, the
command did not include csound.o in the link command.  A find showed
no other *.a files created during the make.  How does one create a
library that provides the CSound API?

John


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

"gogins@pipeline.com"  writes:

> When I create Linux or Unix builds these days, I generally start by
> writing a Makefile.am (which is quite simple) and go from there.

For wxCSound, I use both automake and autoconf.  When configuring for
Windows, wxCSound makes use of an extra object file and program to add
resources into the wxCSound executable.  The automake and autoconf
input required to make this happen is straightforward.  For CSound,
one could use the same mechanism to automatically incorporate the
appropriate real-time audio support.

Micheal, I thought the other points you made in your note were good
too.

John

Hi all,

A bit of an aside: I found that Borland's C++ BuilderX IDE is now
available.  There is a free personal edition that is available for
windows, linux, and solaris.  For those who like IDE's this might be of
interest.  (Also, if you're familiar with their JBuilder product, this
is built with the same technology (yes, a C/C++ environment that's built
in Java =) ).

steven