You will need at least

1. libsndfile (www.mega-nerd.com/libsndfile)
2. scons (www.scons.org)

Then you just have to rename ./custom.py.mkg
to custom.py and then run

scons

Csound will then build in the current directory.
To install, run ./install.py, with admin permissions.

The Csound command will be installed in /usr/bin.

Victor

> Hi,
>
> I'm not very familiar with compiling from source in
> general, and I'm having a hard time finding documentation
> on how to build csound in linux or ubuntu. Is there a
> step-by-step list somewhere that can (at least somewhat)
> painlessly illustrate how to do this for Ubuntu? I've been
> attempting this for a while but have yet to get it
> working.
>
> Thanks,
> Jeremy Flores
>
> flores1@mit.edu
>
>
> --
> Send bugs reports to this list.
> To unsubscribe, send email to
> csound-unsubscribe@lists.bath.ac.uk

Victor Lazzarini wrote:

>... you just have to rename ./custom.py.mkg
>to custom.py and then run
>
>scons
>
>Csound will then build in the current directory.
>To install, run ./install.py, with admin permissions.
>  
>
None of these instructions are in the package. I suggest they be 
included in either a README or one of the installation descriptions.

Best,

dp

I think that the problem here is that custom.py is missing from the source
package for 5.06 (correct?).  This was an oversight, so those instructions
should not be added to the README/manual.

And as Victor pointed out, the install target of scons and the install.py
script have not been maintained.  I believe someone was looking into it ...

Anthony

Dave Phillips wrote on 7/31/07 7:29 AM:

> Victor Lazzarini wrote:
> 
>> ... you just have to rename ./custom.py.mkg
>> to custom.py and then run
>> 
>> scons
>> 
>> Csound will then build in the current directory.
>> To install, run ./install.py, with admin permissions.
>> 
>> 
> None of these instructions are in the package. I suggest they be
> included in either a README or one of the installation descriptions.
> 
> Best,
> 
> dp

I thought the problem was that the custom.py was not necessary correct for 
everyone.  I have long since ceased attempting to d/load it as it made my 
system unbuilbable.
==John ff

I very well may be mistaken as I do not build with scons.  Sorry for any
confusion ...

Anthony

jpff@cs.bath.ac.uk wrote on 8/1/07 1:18 PM:

> I thought the problem was that the custom.py was not necessary correct for
> everyone.  I have long since ceased attempting to d/load it as it made my
> system unbuilbable.
> ==John ff

Hi again, and thanks for the help, Victor.

I got it working; however, I ran into a missing dependency while running 
scons:
'cannot find -lasound'.

If anyone's having this problem in Ubuntu, it seems to originate from 
needing 'libasound-dev', which doesn't seem to come natively with Ubuntu 
(though libasound does). To get it going, all you need to do is run 
'sudo apt-get install libasound-dev' from the terminal before doing scons.

Trying to spare a few headaches...
Jeremy




Victor Lazzarini wrote:
> You will need at least
>
> 1. libsndfile (www.mega-nerd.com/libsndfile)
> 2. scons (www.scons.org)
>
> Then you just have to rename ./custom.py.mkg
> to custom.py and then run
>
> scons
>
> Csound will then build in the current directory.
> To install, run ./install.py, with admin permissions.
>
> The Csound command will be installed in /usr/bin.
>
> Victor
>
>   
>> Hi,
>>
>> I'm not very familiar with compiling from source in
>> general, and I'm having a hard time finding documentation
>> on how to build csound in linux or ubuntu. Is there a
>> step-by-step list somewhere that can (at least somewhat)
>> painlessly illustrate how to do this for Ubuntu? I've been
>> attempting this for a while but have yet to get it
>> working.
>>
>> Thanks,
>> Jeremy Flores
>>
>> flores1@mit.edu
>>
>>
>> --
>> Send bugs reports to this list.
>> To unsubscribe, send email to
>> csound-unsubscribe@lists.bath.ac.uk
>>     

Jeremy,  (or other Linux users),

Now that you have the Ubuntu install all worked out, it would be  
really helpful for others if you could write up a
step by step set of instructions for others.

Maybe this could be included in the manual - or on some WIKI that  
Linux Users could constantly revise.

Seems that there are a number of packages and requirements that are  
unique for the different versions
of Linux.  This might be a helpful way of keeping up with the  
changing Linux installs and their changing package
requirements etc.

Dr. B.

On Aug 2, 2007, at 2:33 AM, Jeremy Flores wrote:

> Hi again, and thanks for the help, Victor.
>
> I got it working; however, I ran into a missing dependency while  
> running scons:
> 'cannot find -lasound'.
>
> If anyone's having this problem in Ubuntu, it seems to originate  
> from needing 'libasound-dev', which doesn't seem to come natively  
> with Ubuntu (though libasound does). To get it going, all you need  
> to do is run 'sudo apt-get install libasound-dev' from the terminal  
> before doing scons.
>
> Trying to spare a few headaches...
> Jeremy
>
>
>
>
> Victor Lazzarini wrote:
>> You will need at least
>>
>> 1. libsndfile (www.mega-nerd.com/libsndfile)
>> 2. scons (www.scons.org)
>>
>> Then you just have to rename ./custom.py.mkg
>> to custom.py and then run
>>
>> scons
>>
>> Csound will then build in the current directory.
>> To install, run ./install.py, with admin permissions.
>>
>> The Csound command will be installed in /usr/bin.
>>
>> Victor
>>
>>
>>> Hi,
>>>
>>> I'm not very familiar with compiling from source in
>>> general, and I'm having a hard time finding documentation
>>> on how to build csound in linux or ubuntu. Is there a
>>> step-by-step list somewhere that can (at least somewhat)
>>> painlessly illustrate how to do this for Ubuntu? I've been
>>> attempting this for a while but have yet to get it
>>> working.
>>>
>>> Thanks,
>>> Jeremy Flores
>>>
>>> flores1@mit.edu
>>>
>>>
>>> --
>>> Send bugs reports to this list.
>>> To unsubscribe, send email to
>>> csound-unsubscribe@lists.bath.ac.uk
>>>
>
> -- 
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

ya a flag would work just the same.

It seems outvalue outputs on the init pass and k-pass .. so its  
important to terminate before the first k-pass.  Haven't tried a  
duration of 0.  Didn't think it would get scheduled at all that way.   
But that seems like a reasonable alternative plan.

greg

On Aug 16, 2007, at 3:14 AM, Oeyvind Brandtsegg wrote:

> Just a few quick toughts, did not have time to test.
>
> I don't think your code is particularly nasty,
> but it would be possible to use a flag instead of a counter to make it
> a little less nasty.
>
> kFlag init 0
> if kFlag > 0 goto end
> ;do the "call once" code here
> kFlag = 1
> end:
>
> I use this technique routinely for things that needs to be called  
> only once.
>
> In your example, I wonder if you could also call the instrument with a
> duration of zero. I seem to recall that a duration of zero will do
> only an init pass and no k-passes. Maybe outvalue (or something else
> in your instrument) needs at least one  k-pass to operate correctly,
> and that is the reason why your first version did not work.
> For you first code version, does it help to move the turnoff statement
> to the last line, after outvalue ?
>
>
> Oeyvind
>
>
> 2007/8/15, Greg Thompson :
>>
>> This does what I want it to do.  Although its pretty nasty.
>>
>>
>>     instr 101
>> kcounter init 0
>>
>>     Sfname      strget p4
>>
>>     Spathback sprintf "%d/len", p5
>>     Spathbackchan sprintf "%d/channels", p5
>>
>>     ichannels filenchnls Sfname
>>
>>
>>
>>
>>     iftno ftgen p5, 0, 0, 1, Sfname, 0, 0, 1
>>
>> if kcounter >= 0 kgoto done
>>
>>
>>             outvalue Spathback, ftlen(iftno)
>>             outvalue Spathbackchan, ichannels
>>
>> kcounter = kcounter + 1
>>
>>
>> done:
>>
>>
>>     endin
>>
>> greg
>>
>>
>> On Aug 15, 2007, at 2:57 PM, Greg Thompson wrote:
>>
>> The following locks up on my system.   There are two solutions  
>> I've found to
>> overcoming the problem.
>>
>> 1 - Stagger the load times.
>> i101 0 1 "dr_kick4.aiff" 1
>> i101 1 1 "dr_ride1.aif" 2
>> i101 2 1 "dr_snare1.aif" 3
>>
>> Problem:  I want them to load as soon as possible
>>
>> 2 - Remove the turnoff opcode
>>
>> Problem: I want to use the outvalue opcode to send a message back  
>> to my
>> system telling me that the ftgen has completed along with some other
>> information about the file.  How can I ensure that outvalue is  
>> only called
>> once?  I guess I could put a if and a counter .. but that seems to  
>> be an
>> unnecessary hack.  Am I crazy or is turnoff buggy?  Suggestions  
>> welcome..
>>
>>
>> 
>> 
>> -odac
>> 
>> 
>>     sr = 44100
>>     kr = 4410
>> nchnls = 2
>>
>>     instr 101
>>
>>     turnoff ; only allow for an init pass
>>
>>     Sfname      strget p4
>>
>>     iftno ftgen p5, 0, 0, 1, Sfname, 0, 0, 1
>>
>>     endin
>>
>> 
>> 
>>
>> i101 0 1 "dr_kick4.aiff" 1
>> i101 0 1 "dr_ride1.aif" 2
>> i101 0 1 "dr_snare1.aif" 3
>>
>> 
>> 
>>
>>
>> 
>> 
>> 
>>
>>
>>
>>
>>
>> Audio files are attached.
>>
>> greg
>>
> -- 
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>

I just compiled csound5 in Ubuntu 7.10 as per instructions, everything went
fine, I am just confused about one thing (very basic I think, but I am newb
material)
After running ./install.py I got the message:
Csound installation has been successfully completed.
Before running Csound, make sure that the following environment
variables are set:
  OPCODEDIR=/usr/local/lib/csound/plugins
  CSSTRNGS=/usr/local/share/csound/xmg
Csound can be uninstalled by running /usr/local/bin/uninstall-csound5

and similarly running csound:
        ################################################################
        #               WARNING: OPCODEDIR IS NOT SET !                #
        # Csound requires this environment variable to be set to find  #
        # its plugin libraries. If it is not set, you may experience   #
        # missing opcodes, audio/MIDI drivers, or utilities.           #
        ################################################################

apparently I need to set some environmental variables.  I think I read
something about the command 'setenv', but that command is not available to
me in terminal.

can someone please explain to me how to do this?


Victor Lazzarini wrote:
> 
> You will need at least
> 
> 1. libsndfile (www.mega-nerd.com/libsndfile)
> 2. scons (www.scons.org)
> 
> Then you just have to rename ./custom.py.mkg
> to custom.py and then run
> 
> scons
> 
> Csound will then build in the current directory.
> To install, run ./install.py, with admin permissions.
> 
> The Csound command will be installed in /usr/bin.
> 
> Victor
> 
>> Hi,
>>
>> I'm not very familiar with compiling from source in
>> general, and I'm having a hard time finding documentation
>> on how to build csound in linux or ubuntu. Is there a
>> step-by-step list somewhere that can (at least somewhat)
>> painlessly illustrate how to do this for Ubuntu? I've been
>> attempting this for a while but have yet to get it
>> working.
>>
>> Thanks,
>> Jeremy Flores
>>
>> flores1@mit.edu
>>
>>
>> --
>> Send bugs reports to this list.
>> To unsubscribe, send email to
>> csound-unsubscribe@lists.bath.ac.uk
> -- 
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
> 

-- 
View this message in context: http://www.nabble.com/compiling-csound-5.06-in-ubuntu-tf4178460.html#a13784856
Sent from the Csound - General mailing list archive at Nabble.com.

Hi Matt, I'm not on Linux but perhaps I can help
I presume you're running a bash shell..
(if csh or other the commands are similar)

If so, in your home directory find an existing, or create a file  
called .bashrc
in it put
set OPCODEDIR='/usr/local/lib/csound/plugins'
set CSSTRNGS='/usr/local/share/csound/xmg'

save the file and then, at the prompt, type
source ~/.bashrc
(this alerts the current shell to the new stuff)

if you want to check that the shel 'knows' about its new variables,  
at the bash prompt  type
echo $OPCODEDIR
and
echo $CSSTRNGS

and you see the strings filepaths you've set, above.

David
On 16/11/2007, at 11:13 AM, Matt Enkoan wrote:

>
> I just compiled csound5 in Ubuntu 7.10 as per instructions,  
> everything went
> fine, I am just confused about one thing (very basic I think, but I  
> am newb
> material)
> After running ./install.py I got the message:
> Csound installation has been successfully completed.
> Before running Csound, make sure that the following environment
> variables are set:
>   OPCODEDIR=/usr/local/lib/csound/plugins
>   CSSTRNGS=/usr/local/share/csound/xmg
> Csound can be uninstalled by running /usr/local/bin/uninstall-csound5
>
> and similarly running csound:
>          
> ################################################################
>         #               WARNING: OPCODEDIR IS NOT  
> SET !                #
>         # Csound requires this environment variable to be set to  
> find  #
>         # its plugin libraries. If it is not set, you may  
> experience   #
>         # missing opcodes, audio/MIDI drivers, or  
> utilities.           #
>          
> ################################################################
>
> apparently I need to set some environmental variables.  I think I read
> something about the command 'setenv', but that command is not  
> available to
> me in terminal.
>
> can someone please explain to me how to do this?
>
>
> Victor Lazzarini wrote:
>>
>> You will need at least
>>
>> 1. libsndfile (www.mega-nerd.com/libsndfile)
>> 2. scons (www.scons.org)
>>
>> Then you just have to rename ./custom.py.mkg
>> to custom.py and then run
>>
>> scons
>>
>> Csound will then build in the current directory.
>> To install, run ./install.py, with admin permissions.
>>
>> The Csound command will be installed in /usr/bin.
>>
>> Victor
>>
>>> Hi,
>>>
>>> I'm not very familiar with compiling from source in
>>> general, and I'm having a hard time finding documentation
>>> on how to build csound in linux or ubuntu. Is there a
>>> step-by-step list somewhere that can (at least somewhat)
>>> painlessly illustrate how to do this for Ubuntu? I've been
>>> attempting this for a while but have yet to get it
>>> working.
>>>
>>> Thanks,
>>> Jeremy Flores
>>>
>>> flores1@mit.edu
>>>
>>>
>>> --
>>> Send bugs reports to this list.
>>> To unsubscribe, send email to
>>> csound-unsubscribe@lists.bath.ac.uk
>> -- 
>> Send bugs reports to this list.
>> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>>
>
> -- 
> View this message in context: http://www.nabble.com/compiling- 
> csound-5.06-in-ubuntu-tf4178460.html#a13784856
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>

_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 creative.canberra.edu.au/scrg/

if you're using the csh shell, the commands become

setenv OPCODEDIR '/usr/local/lib/csound/plugins'
setenv CSSTRNGS '/usr/local/share/csound/xmg'

note the lack of the "="

David
On 16/11/2007, at 11:43 AM, David Worrall wrote:

> Hi Matt, I'm not on Linux but perhaps I can help
> I presume you're running a bash shell..
> (if csh or other the commands are similar)
>
> If so, in your home directory find an existing, or create a file  
> called .bashrc
> in it put
> set OPCODEDIR='/usr/local/lib/csound/plugins'
> set CSSTRNGS='/usr/local/share/csound/xmg'
>
> save the file and then, at the prompt, type
> source ~/.bashrc
> (this alerts the current shell to the new stuff)
>
> if you want to check that the shel 'knows' about its new variables,  
> at the bash prompt  type
> echo $OPCODEDIR
> and
> echo $CSSTRNGS
>
> and you see the strings filepaths you've set, above.
>
> David
> On 16/11/2007, at 11:13 AM, Matt Enkoan wrote:
>
>>
>> I just compiled csound5 in Ubuntu 7.10 as per instructions,  
>> everything went
>> fine, I am just confused about one thing (very basic I think, but  
>> I am newb
>> material)
>> After running ./install.py I got the message:
>> Csound installation has been successfully completed.
>> Before running Csound, make sure that the following environment
>> variables are set:
>>   OPCODEDIR=/usr/local/lib/csound/plugins
>>   CSSTRNGS=/usr/local/share/csound/xmg
>> Csound can be uninstalled by running /usr/local/bin/uninstall-csound5
>>
>> and similarly running csound:
>>          
>> ################################################################
>>         #               WARNING: OPCODEDIR IS NOT  
>> SET !                #
>>         # Csound requires this environment variable to be set to  
>> find  #
>>         # its plugin libraries. If it is not set, you may  
>> experience   #
>>         # missing opcodes, audio/MIDI drivers, or  
>> utilities.           #
>>          
>> ################################################################
>>
>> apparently I need to set some environmental variables.  I think I  
>> read
>> something about the command 'setenv', but that command is not  
>> available to
>> me in terminal.
>>
>> can someone please explain to me how to do this?
>>
>>
>> Victor Lazzarini wrote:
>>>
>>> You will need at least
>>>
>>> 1. libsndfile (www.mega-nerd.com/libsndfile)
>>> 2. scons (www.scons.org)
>>>
>>> Then you just have to rename ./custom.py.mkg
>>> to custom.py and then run
>>>
>>> scons
>>>
>>> Csound will then build in the current directory.
>>> To install, run ./install.py, with admin permissions.
>>>
>>> The Csound command will be installed in /usr/bin.
>>>
>>> Victor
>>>
>>>> Hi,
>>>>
>>>> I'm not very familiar with compiling from source in
>>>> general, and I'm having a hard time finding documentation
>>>> on how to build csound in linux or ubuntu. Is there a
>>>> step-by-step list somewhere that can (at least somewhat)
>>>> painlessly illustrate how to do this for Ubuntu? I've been
>>>> attempting this for a while but have yet to get it
>>>> working.
>>>>
>>>> Thanks,
>>>> Jeremy Flores
>>>>
>>>> flores1@mit.edu
>>>>
>>>>
>>>> --
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email to
>>>> csound-unsubscribe@lists.bath.ac.uk
>>> -- 
>>> Send bugs reports to this list.
>>> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>>>
>>
>> -- 
>> View this message in context: http://www.nabble.com/compiling- 
>> csound-5.06-in-ubuntu-tf4178460.html#a13784856
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
> _________________________________________________
> experimental polymedia:	www.avatar.com.au
> Sonic Communications Research Group,
> University of Canberra:	 creative.canberra.edu.au/scrg/
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>

_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 creative.canberra.edu.au/scrg/

did you do source ~/.bashrc?

( logging in to a new shell should do it as well)

you are right in assuming these are shell variables not csound  
command-line options (which are placed in the .csoundrc file.

if it still doesn't work, send a copy of the contents of .bashrc

(I'm answering this mainly because I may be the only one awake!)

David

On 16/11/2007, at 12:12 PM, Matt wrote:

> David,
> Thanks for the reply but this doesn't seem to be working.
> I edited .bashrc as suggested.
> On 'echo $OPCODEDIR' I receive just a blank line.
>
> Yes, I am running bash shell.
>
> I was reading the cSound manual about this (pg. 63):
> "You can set environmental variables on the command line or the  
> configuration
> file .csoundrc by using the flag --env:NAME=VALE.......Please note  
> that this
> method of setting environmental variables will not work for  
> variables which
> are parsed before the command line arguments...the following  
> environmental
> variables must be set on the system prior to running csound:
> OPCODEDIR..CSSTRINGS..."
>
> I assume that's what you were helping me to do, but like I said, still
> receiving the same error message from cSound5.
>
>
> On Thursday 15 November 2007 7:43:44 pm David Worrall wrote:
>> Hi Matt, I'm not on Linux but perhaps I can help
>> I presume you're running a bash shell..
>> (if csh or other the commands are similar)
>>
>> If so, in your home directory find an existing, or create a file
>> called .bashrc
>> in it put
>> set OPCODEDIR='/usr/local/lib/csound/plugins'
>> set CSSTRNGS='/usr/local/share/csound/xmg'
>>
>> save the file and then, at the prompt, type
>> source ~/.bashrc
>> (this alerts the current shell to the new stuff)
>>
>> if you want to check that the shel 'knows' about its new variables,
>> at the bash prompt  type
>> echo $OPCODEDIR
>> and
>> echo $CSSTRNGS
>>
>> and you see the strings filepaths you've set, above.
>>
>> David
>>
>> On 16/11/2007, at 11:13 AM, Matt Enkoan wrote:
>>> I just compiled csound5 in Ubuntu 7.10 as per instructions,
>>> everything went
>>> fine, I am just confused about one thing (very basic I think, but I
>>> am newb
>>> material)
>>> After running ./install.py I got the message:
>>> Csound installation has been successfully completed.
>>> Before running Csound, make sure that the following environment
>>> variables are set:
>>>   OPCODEDIR=/usr/local/lib/csound/plugins
>>>   CSSTRNGS=/usr/local/share/csound/xmg
>>> Csound can be uninstalled by running /usr/local/bin/uninstall- 
>>> csound5
>>>
>>> and similarly running csound:
>>>
>>> ################################################################
>>>         #               WARNING: OPCODEDIR IS NOT
>>> SET !                #
>>>         # Csound requires this environment variable to be set to
>>> find  #
>>>         # its plugin libraries. If it is not set, you may
>>> experience   #
>>>         # missing opcodes, audio/MIDI drivers, or
>>> utilities.           #
>>>
>>> ################################################################
>>>
>>> apparently I need to set some environmental variables.  I think I  
>>> read
>>> something about the command 'setenv', but that command is not
>>> available to
>>> me in terminal.
>>>
>>> can someone please explain to me how to do this?
>>>
>>> Victor Lazzarini wrote:
>>>> You will need at least
>>>>
>>>> 1. libsndfile (www.mega-nerd.com/libsndfile)
>>>> 2. scons (www.scons.org)
>>>>
>>>> Then you just have to rename ./custom.py.mkg
>>>> to custom.py and then run
>>>>
>>>> scons
>>>>
>>>> Csound will then build in the current directory.
>>>> To install, run ./install.py, with admin permissions.
>>>>
>>>> The Csound command will be installed in /usr/bin.
>>>>
>>>> Victor
>>>>
>>>>> Hi,
>>>>>
>>>>> I'm not very familiar with compiling from source in
>>>>> general, and I'm having a hard time finding documentation
>>>>> on how to build csound in linux or ubuntu. Is there a
>>>>> step-by-step list somewhere that can (at least somewhat)
>>>>> painlessly illustrate how to do this for Ubuntu? I've been
>>>>> attempting this for a while but have yet to get it
>>>>> working.
>>>>>
>>>>> Thanks,
>>>>> Jeremy Flores
>>>>>
>>>>> flores1@mit.edu
>>>>>
>>>>>
>>>>> --
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email to
>>>>> csound-unsubscribe@lists.bath.ac.uk
>>>>
>>>> --
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>>>
>>> --
>>> View this message in context: http://www.nabble.com/compiling-
>>> csound-5.06-in-ubuntu-tf4178460.html#a13784856
>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>> "unsubscribe csound"
>>
>> _________________________________________________
>> experimental polymedia:	www.avatar.com.au
>> Sonic Communications Research Group,
>> University of Canberra:	 creative.canberra.edu.au/scrg/
>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe
>> csound"
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>

_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 creative.canberra.edu.au/scrg/

of course -it's hard for old dogs to learn new tricks  :-)

On 16/11/2007, at 1:55 PM, Steven Yi wrote:

> You may want to use 'export' instead of 'set' for those variables for
> csound5 in your .bashrc.
>
> On Nov 15, 2007 5:47 PM, Matt Enkoan  wrote:
>> Yes, I did source ~/.bashrc to no avail.
>>
>> I also did a little digging and found that editing the file /etc/ 
>> environment
>> is suggested in Ubuntu.  I did so and then
>>
>> source /etc/environment
>>
>> then
>>
>> echo $OPCODEDIR
>>
>> and was returned the correct path name.
>> However running csound I STILL received the same error! Apparently  
>> the shell
>> now knows but csound still does not.
>>
>> environment:
>> PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/ 
>> bin:/usr/games"
>> LANG="en_US.UTF-8"
>> OPCODEDIR="/usr/local/lib/csound/plugins"
>> CSSTRNGS="/usr/local/share/csound/xmg"
>>
>> .bashrc:
>>
>> # ~/.bashrc: executed by bash(1) for non-login shells.
>> # see /usr/share/doc/bash/examples/startup-files (in the package  
>> bash-doc)
>> # for examples
>>
>> # If not running interactively, don't do anything
>> [ -z "$PS1" ] && return
>>
>> # don't put duplicate lines in the history. See bash(1) for more  
>> options
>> export HISTCONTROL=ignoredups
>> # ... and ignore same sucessive entries.
>> export HISTCONTROL=ignoreboth
>>
>> # check the window size after each command and, if necessary,
>> # update the values of LINES and COLUMNS.
>> shopt -s checkwinsize
>>
>> # make less more friendly for non-text input files, see lesspipe(1)
>> [ -x /usr/bin/lesspipe ] && eval "$(lesspipe)"
>>
>> # set variable identifying the chroot you work in (used in the  
>> prompt below)
>> if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
>>     debian_chroot=$(cat /etc/debian_chroot)
>> fi
>>
>> # set a fancy prompt (non-color, unless we know we "want" color)
>> case "$TERM" in
>> xterm-color)
>>     PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\ 
>> [\033[00m\]:
>> \[\033[01;34m\]\w\[\033[00m\]\$ '
>>     ;;
>> *)
>>     PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
>>     ;;
>> esac
>>
>> # Comment in the above and uncomment this below for a color prompt
>> #PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033 
>> [00m\]:
>> \[\033[01;34m\]\w\[\033[00m\]\$ '
>>
>> # If this is an xterm set the title to user@host:dir
>> case "$TERM" in
>> xterm*|rxvt*)
>>     PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD/ 
>> $HOME/~}\007"'
>>     ;;
>> *)
>>     ;;
>> esac
>>
>> # Alias definitions.
>> # You may want to put all your additions into a separate file like
>> # ~/.bash_aliases, instead of adding them here directly.
>> # See /usr/share/doc/bash-doc/examples in the bash-doc package.
>>
>> #if [ -f ~/.bash_aliases ]; then
>> #    . ~/.bash_aliases
>> #fi
>>
>> # enable color support of ls and also add handy aliases
>> if [ "$TERM" != "dumb" ]; then
>>     eval "`dircolors -b`"
>>     alias ls='ls --color=auto'
>>     #alias dir='ls --color=auto --format=vertical'
>>     #alias vdir='ls --color=auto --format=long'
>> fi
>>
>> # some more ls aliases
>> #alias ll='ls -l'
>> #alias la='ls -A'
>> #alias l='ls -CF'
>>
>> # enable programmable completion features (you don't need to enable
>> # this, if it's already enabled in /etc/bash.bashrc and /etc/profile
>> # sources /etc/bash.bashrc).
>> if [ -f /etc/bash_completion ]; then
>>     . /etc/bash_completion
>> fi
>>
>> # added for cSound5
>> set OPCODEDIR='/usr/local/lib/csound/plugins'
>> set CSSTRNGS='/usr/local/share/csound/xmg'
>>
>>
>>
>> On Thursday 15 November 2007 8:24:25 pm David Worrall wrote:
>>> did you do source ~/.bashrc?
>>>
>>> ( logging in to a new shell should do it as well)
>>>
>>> you are right in assuming these are shell variables not csound
>>> command-line options (which are placed in the .csoundrc file.
>>>
>>> if it still doesn't work, send a copy of the contents of .bashrc
>>>
>>> (I'm answering this mainly because I may be the only one awake!)
>>>
>>> David
>>>
>>> On 16/11/2007, at 12:12 PM, Matt wrote:
>>>> David,
>>>> Thanks for the reply but this doesn't seem to be working.
>>>> I edited .bashrc as suggested.
>>>> On 'echo $OPCODEDIR' I receive just a blank line.
>>>>
>>>> Yes, I am running bash shell.
>>>>
>>>> I was reading the cSound manual about this (pg. 63):
>>>> "You can set environmental variables on the command line or the
>>>> configuration
>>>> file .csoundrc by using the flag --env:NAME=VALE.......Please note
>>>> that this
>>>> method of setting environmental variables will not work for
>>>> variables which
>>>> are parsed before the command line arguments...the following
>>>> environmental
>>>> variables must be set on the system prior to running csound:
>>>> OPCODEDIR..CSSTRINGS..."
>>>>
>>>> I assume that's what you were helping me to do, but like I said,  
>>>> still
>>>> receiving the same error message from cSound5.
>>>>
>>>> On Thursday 15 November 2007 7:43:44 pm David Worrall wrote:
>>>>> Hi Matt, I'm not on Linux but perhaps I can help
>>>>> I presume you're running a bash shell..
>>>>> (if csh or other the commands are similar)
>>>>>
>>>>> If so, in your home directory find an existing, or create a file
>>>>> called .bashrc
>>>>> in it put
>>>>> set OPCODEDIR='/usr/local/lib/csound/plugins'
>>>>> set CSSTRNGS='/usr/local/share/csound/xmg'
>>>>>
>>>>> save the file and then, at the prompt, type
>>>>> source ~/.bashrc
>>>>> (this alerts the current shell to the new stuff)
>>>>>
>>>>> if you want to check that the shel 'knows' about its new  
>>>>> variables,
>>>>> at the bash prompt  type
>>>>> echo $OPCODEDIR
>>>>> and
>>>>> echo $CSSTRNGS
>>>>>
>>>>> and you see the strings filepaths you've set, above.
>>>>>
>>>>> David
>>>>>
>>>>> On 16/11/2007, at 11:13 AM, Matt Enkoan wrote:
>>>>>> I just compiled csound5 in Ubuntu 7.10 as per instructions,
>>>>>> everything went
>>>>>> fine, I am just confused about one thing (very basic I think,  
>>>>>> but I
>>>>>> am newb
>>>>>> material)
>>>>>> After running ./install.py I got the message:
>>>>>> Csound installation has been successfully completed.
>>>>>> Before running Csound, make sure that the following environment
>>>>>> variables are set:
>>>>>>   OPCODEDIR=/usr/local/lib/csound/plugins
>>>>>>   CSSTRNGS=/usr/local/share/csound/xmg
>>>>>> Csound can be uninstalled by running /usr/local/bin/uninstall-
>>>>>> csound5
>>>>>>
>>>>>> and similarly running csound:
>>>>>>
>>>>>> ################################################################
>>>>>>         #               WARNING: OPCODEDIR IS NOT
>>>>>> SET !                #
>>>>>>         # Csound requires this environment variable to be set to
>>>>>> find  #
>>>>>>         # its plugin libraries. If it is not set, you may
>>>>>> experience   #
>>>>>>         # missing opcodes, audio/MIDI drivers, or
>>>>>> utilities.           #
>>>>>>
>>>>>> ################################################################
>>>>>>
>>>>>> apparently I need to set some environmental variables.  I think I
>>>>>> read
>>>>>> something about the command 'setenv', but that command is not
>>>>>> available to
>>>>>> me in terminal.
>>>>>>
>>>>>> can someone please explain to me how to do this?
>>>>>>
>>>>>> Victor Lazzarini wrote:
>>>>>>> You will need at least
>>>>>>>
>>>>>>> 1. libsndfile (www.mega-nerd.com/libsndfile)
>>>>>>> 2. scons (www.scons.org)
>>>>>>>
>>>>>>> Then you just have to rename ./custom.py.mkg
>>>>>>> to custom.py and then run
>>>>>>>
>>>>>>> scons
>>>>>>>
>>>>>>> Csound will then build in the current directory.
>>>>>>> To install, run ./install.py, with admin permissions.
>>>>>>>
>>>>>>> The Csound command will be installed in /usr/bin.
>>>>>>>
>>>>>>> Victor
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I'm not very familiar with compiling from source in
>>>>>>>> general, and I'm having a hard time finding documentation
>>>>>>>> on how to build csound in linux or ubuntu. Is there a
>>>>>>>> step-by-step list somewhere that can (at least somewhat)
>>>>>>>> painlessly illustrate how to do this for Ubuntu? I've been
>>>>>>>> attempting this for a while but have yet to get it
>>>>>>>> working.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Jeremy Flores
>>>>>>>>
>>>>>>>> flores1@mit.edu
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Send bugs reports to this list.
>>>>>>>> To unsubscribe, send email to
>>>>>>>> csound-unsubscribe@lists.bath.ac.uk
>>>>>>>
>>>>>>> --
>>>>>>> Send bugs reports to this list.
>>>>>>> To unsubscribe, send email to csound- 
>>>>>>> unsubscribe@lists.bath.ac.uk
>>>>>>
>>>>>> --
>>>>>> View this message in context: http://www.nabble.com/compiling-
>>>>>> csound-5.06-in-ubuntu-tf4178460.html#a13784856
>>>>>> Sent from the Csound - General mailing list archive at  
>>>>>> Nabble.com.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe csound"
>>>>>
>>>>> _________________________________________________
>>>>> experimental polymedia:    www.avatar.com.au
>>>>> Sonic Communications Research Group,
>>>>> University of Canberra:     creative.canberra.edu.au/scrg/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>> "unsubscribe
>>>>> csound"
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>> "unsubscribe csound"
>>>
>>> _________________________________________________
>>> experimental polymedia:       www.avatar.com.au
>>> Sonic Communications Research Group,
>>> University of Canberra:        creative.canberra.edu.au/scrg/
>>>
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>> "unsubscribe
>>> csound"
>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>

_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 creative.canberra.edu.au/scrg/