John ffitch wrote
> I am not a guru.  The build stuff is in python which I do not know
> and there are parts in java (never written any that works) and C++
> (which I try to avoid).  I just run a command that says
> scons -j 3 generateTags=1 useJack=1 generateZip=0 install=0 useOSC=1 useDouble=1 buildInterfaces=1 buildTclcsound=1 usePortMIDI=1 useALSA=1 noDebug=0 buildJavaWrapper=1 pythonVersion=2.6 buildPythonOpcodes=1 buildRelease=0 buildWinsound=1 Word64=1 buildCsound5GUI=0 buildCSeditor=1 Lib64=1 buildNewParser=1 useUDP=1 useGettext=1 gcc4opt=k8 tclversion=8.5 includeMP3=1 includeWii=1 buildPythonWrapper=1
> 
> and wait.  When it fails I ask the developer list who point out the
> obvious that I missed

Thank you, John.  I assume that this is for installing on Linux, 
since a see an option for Jack.  As a windows user, I am 
unlikely to have encountered anything like this process..in fact 
it is only through being interested in csound that I have 
encountered phrases like "change your PATH variable to..", "run 
a command..", and "at the command prompt, type..".  Through the 
scant info explaining this stuff in the csound docs, and through 
following posts to this list, I'm beginning to see what these 
mean.  And more, I'm beginning to see how utilizing the command 
line interface could be useful, and how being able to make a 
custom installation of csound might even be desirable over a 
pre-made installer.  But I'm still not sure how all this works. 
  As I mentioned before, the current manual seems unclear to 
someone like me, and needs to be modified (amplified, 'dumbed 
down' or something) so that a Win-dodo like myself can begin to 
benefit from the power such knowledge provides.  I am certainly 
not afraid of approaching csound as a programming language, and 
have made use of the many tutorial resources and books that are 
available explaining it.  The power of csound is what attracted 
me to it in the first place.  What I'd like to see is a tutorial 
that includes something like you posted to get a newbie up and 
running , if they so choose, on their own installation.  Several 
poster have stated it's no that hard to do.   Of course, not 
much is, when you know how to do it.  Until such an addendum is 
included with the documentation, I will content my self with 
trying to see if I can get your example to work for me on 
windows.  So..thanks again
Bob Foose


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"