| Why do this instead of just using Csound 5? It seems to me that you should
try to use Csound 5 and, if you have problems, report them so we can fix
them.
In other words, the Csound developers in general, and myself in particular,
have limited time. If I have to backport code from Csound 5 to Csound 4,
that means I can't get Csound 5 further towards release status.
However, if there is a REAL (i.e. MUSICAL) reason why Csound 5 won't work
for you, I need to know that. In that case I will either do some minimal
backporting, or I will make fixing the problem in Csound 5 a priority.
A MUSICAL reason is a MUSICAL feature that doesn't work (score doesn't
render, opcode is missing, opcode doesn't work, input/output doesn't work).
If you can ONLY work on Mac OS 9, that too would be a musical reason.
Original Message:
-----------------
From: vanDongen/Gilcher gml@xs4all.nl
Date: Fri, 20 Aug 2004 10:08:24 +0000
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:5229] csoundlib in csound4?
It seems that libcsound is not included in the regular csound release.
Or at least that the installed libcsound.a is compiled with jpff_glue
instead
of csound.c, making it useless for programs using the API.
What version should I tell people to get if they want to use my jcsound
program that requires a libcsound installed?
I think the same goes for wxcsound as well.
regards
Gerard
--
electronic & acoustic musics-- http://www.xs4all.nl/~gml
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ . |