You can already set environment variables in .csoundrc. However, some
of the environment variables (e.g. OPCODEDIR) are used before .csoundrc
is read, so you cannot set everything there, and removing that limitation
is not trivial. Of course, any reasonably good installer should deal with
OPCODEDIR - maybe also CSSTRNGS and CS_LANG when language translations
will be done - automatically anyway.

On Thursday 27 April 2006 00:24, Steven Yi wrote:

> That's a possible solution but I'd say perhaps too complicated for end users.
> 
> I'm not sure if this is feasible due to the many ways to set up
> environment variables, but perhaps we should create a GUI app that
> opens up with the Csound variables to edit (with buttons to open up a
> file selector to choose a directory to make it easier)?  Maybe if we
> add a csSettings file that lives in user home or modify .csoundrc to
> allow setting environment variables in a "key=value" format, that
> would make it cross-platform and then not too difficult to make a GUI
> for.  If .csoundrc, then the GUI could also edit the default
> commandline values.  It might be a solution that could satisify all
> parties, whether those who prefer to edit values by text or by GUI. 
> The one issue would be making this backwards compatible with .csoundrc
> as it is now.
> 
> Having one file to edit environment variables in would be a lot easier
> to support in terms of documentation too.


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net