Of course the whole point of us pushing for a release is so that musicians such as yourself can just download and install Csound 5.

In the meantime...

The Loris and STK opcodes build without problem on Windows and Linux (for me anyway) after simply copying the sources from their latest distributions into their respective opcodes directories.

The fluidsynth opcodes build without problem on Windows and Linux after installing Fluidsynth.

The VST host opcodes build without problem on Windows and Linux as far as I know.

The interfaces library is now a separate target from CsoundVST. There is no plan at this time for CsoundVST to be part of the release.

SWIG is a program that automatically generates "glue code" to make interfaces for different languages. SWIG runs on all our supported platforms without problem.

Lua is optional as far as I am concerned, Python and Java both install and run without problem on all our supported platforms.

As far as custom.py is concerned, as the name indicates, this needs to be customized for the directory structure on your own computer so that the build system can find binaries, header files, and libraries that are not in standard locations. 'utah' exists on my PC but that is just my PC, you would need to change the pathnames to suit your own directory structure.

Regards,
Mike





-----Original Message-----
From: David Akbari 
Sent: Nov 20, 2005 12:59 PM
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] Re: Installers


On Nov 20, 2005, at 12:37 PM, Victor Lazzarini wrote:

> I am glad there are more things in the Canonical Csound than there
> were in the past.

I am also very glad for this. However it would seems there are still 
some major issues.

There seem to be optional components that have a lot of trouble 
building "out of the box". I view these currently as:

- Loris opcodes
- STK opcodes
- FluidSynth opcodes
- VST host opcodes
- interfaces library/jCsound/CsoundVST/??? i dont even know where to 
start with this large ball of wax - what do you need ? SWIG, Lua, 
Python 2.4, and Java 5.0 ?? Certainly I have not pursued these so far 
because of all the additional dependencies this introduces, what is 
SWIG even used for ?

What's the deal with custom.py ? I have no c:/utah directory on any 
*nix platform and the documentation in the file itself is confusing and 
sparse. Do I build these opcodes using Windows in VirtualPC as a 
dynamic library ? How is binary compatibility maintained across OSes ? 
It seems the only way to do these things is on Windows.

I'm not a developer i'm just a musician who kind of knows how to use a 
computer so any help is appreciated


-David



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Very helpful information, thank you.

I'll have a look at why these optional targets are not building after 
installation (likely has to do with custom.py) in addition to compiling 
the interfaces library, et al.


-David

On Nov 20, 2005, at 1:34 PM, Michael Gogins wrote:

> In the meantime...
>
> The Loris and STK opcodes build without problem on Windows and Linux 
> (for me anyway) after simply copying the sources from their latest 
> distributions into their respective opcodes directories.
>
> The fluidsynth opcodes build without problem on Windows and Linux 
> after installing Fluidsynth.
>
> The VST host opcodes build without problem on Windows and Linux as far 
> as I know.
>
> The interfaces library is now a separate target from CsoundVST. There 
> is no plan at this time for CsoundVST to be part of the release.
>
> SWIG is a program that automatically generates "glue code" to make 
> interfaces for different languages. SWIG runs on all our supported 
> platforms without problem.
>
> Lua is optional as far as I am concerned, Python and Java both install 
> and run without problem on all our supported platforms.
>
> As far as custom.py is concerned, as the name indicates, this needs to 
> be customized for the directory structure on your own computer so that 
> the build system can find binaries, header files, and libraries that 
> are not in standard locations. 'utah' exists on my PC but that is just 
> my PC, you would need to change the pathnames to suit your own 
> directory structure.



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

> Lua is optional as far as I am concerned

A really minor point on building the Lua interface: when I installed
Lua (5.0.2) from source on Linux, the library name by default was
liblua.so, but the SConstruct file wants to link with liblua50.so.
This is just FYI; I don't know enough about the available packaging
of Lua to suggest a generally portable solution.

For whatever it's worth, I agree that Lua (although it looks like a
very interesting language) is still pretty eclectic to be built into
the canonical distribution.  Surely anyone who wants to hack csound
in Lua will be comfortable installing it as an add-on?

Russell


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Nov 20, 2005, at 2:30 PM, Russell Johnston wrote:

> For whatever it's worth, I agree that Lua (although it looks like a
> very interesting language) is still pretty eclectic to be built into
> the canonical distribution.  Surely anyone who wants to hack csound
> in Lua will be comfortable installing it as an add-on?

I'm just curious - would it perhaps be advisable to create separate  
installers for

Csound - binaries, opcodes, examples, manual
Dependencies - liblo, etc (only for the canonical front end)
Extras - interface library et al + their dependencies

and then let the user decide whether to take the red pill or the blue  
pill ?

Also RE: setting OPCODEDIR et al on OSX I have found that by using

~/.MacOSX/environment.plist (Mac OS 10.3.x)
or
~/.Mac OSX/environment.plist (Mac OS 10.4.x)

it is possible to set all Csound environment variables and they will be  
uniform to the Aqua interface as well as the Terminal (all shells -  
csh, bash, zsh, ksh, tcsh, etc).

by using this environment.plist file





     OPCODEDIR
     /Users/daveakbari/CVS/csound5
     OPCODEDIR64
     /Users/daveakbari/CVS/csound5
     INCDIR
     /Users/daveakbari/CODE/_UDO
     SFDIR
     /loops



This shows up by typing setenv

SECURITYSESSIONID=213e00
HOME=/Users/daveakbari
SHELL=/bin/tcsh
USER=daveakbari
PATH=/sw/bin:/sw/sbin:/bin:/sbin:/usr/bin:/usr/local/bin:/usr/sbin:/ 
usr/X11R6/bin
INCDIR=/Users/daveakbari/CODE/_UDO
OPCODEDIR=/Users/daveakbari/CVS/csound5
OPCODEDIR64=/Users/daveakbari/CVS/csound5
SFDIR=/loops
__CF_USER_TEXT_ENCODING=0x1F7:0:0
TERM_PROGRAM=Apple_Terminal
TERM_PROGRAM_VERSION=100.1.8
TERM=xterm-color
... etc

or export in bash shell

declare -x HOME="/Users/daveakbari"
declare -x HOSTTYPE="powermac"
declare -x INCDIR="/Users/daveakbari/CODE/_UDO"
declare -x INFOPATH="/sw/share/info:/sw/info:/usr/share/info"
declare -x LOGNAME="daveakbari"
declare -x MACHTYPE="powerpc"
declare -x  
MANPATH="/sw/share/man:/usr/share/man:/usr/local/man:/usr/X11R6/man"
declare -x OLDPWD
declare -x OPCODEDIR="/Users/daveakbari/CVS/csound5"
declare -x OPCODEDIR64="/Users/daveakbari/CVS/csound5"
declare -x OSTYPE="darwin"
declare -x  
PATH="/sw/bin:/sw/sbin:/bin:/sbin:/usr/bin:/usr/local/bin:/usr/sbin:/ 
usr/X11R6/bin"
... etc

so I'm fairly certain this should be the standard practice of  
installing with environment variables already set on OSX; by appending  
this file elseif it doesn't exist then create it. Then of course the  
issue is the "reasonable defaults" for these variables ...

What are the expected "reasonable default" settings for the following ??

     "CSNOSTOP",
     "CSOUNDRC",
     "CSSTRNGS",
     "CS_LANG",
     "HOME",
     "INCDIR",
     "OPCODEDIR",
     "OPCODEDIR64",
     "RAWWAVE_PATH",
     "SADIR",
     "SFDIR",
     "SFOUTYP",
     "SNAPDIR",
     "SSDIR"


-David



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net