Looks like as far as your loris code is concerned,
you have outdated code. ENVIRON is not used anymore,
having been substituted by CSOUND.

Victor

>
> While attemmpting to build Csound5 with CsoundVST, I keep
> getting errors while the Loris code is being compiled.
> I've tried several different routes with this: just
> copying the loris source tree into Opcodes/Loris and also
> replacing the src/lorisgens.C and src/lorisgens.h files
> with the lorisgens5.x files in the Loris csound/ directory
> - and renaming them to remove the 5, as well as trying the
> same with the lorisgens5 files included with Csound5.  I
> also tried replacing the lorisgen5.C files included with
> the ones from Csound5 and vice-versa, etc.
>
> Can someone kindly clarify what needs to be done to get a
> working src/lorisgens.c file?
>
> An example of the errors:
>
> Opcodes/Loris/src/lorisgens.C:48:36: warning: "/*" within
> comment In file included from
> Opcodes/Loris/src/lorisgens.C:64:
> Opcodes/Loris/src/SdifFile.h:202: warning: ignoring
> #pragma mark  Opcodes/Loris/src/lorisgens.C:98: warning:
> ignoring #pragma mark  Opcodes/Loris/src/lorisgens.C:103:
> error: variable or field `setup_globals' declared void
> Opcodes/Loris/src/lorisgens.C:103: error: `ENVIRON' was
> not declared in this scope
> Opcodes/Loris/src/lorisgens.C:103: error: `csound' was not
> declared in this scope Opcodes/Loris/src/lorisgens.C:104:
> error: expected `,' or `;' before '{' token
> Opcodes/Loris/src/lorisgens.C:309: warning: ignoring
> #pragma mark  Opcodes/Loris/src/lorisgens.C:391: warning:
> ignoring #pragma mark  Opcodes/Loris/src/lorisgens.C:491:
> warning: ignoring #pragma mark
> Opcodes/Loris/src/lorisgens.C: In constructor
> `LorisReader::LorisReader(const std::string&, double,
> INSDS*, int)': Opcodes/Loris/src/lorisgens.C:525: warning:
> comparison between signed and unsigned integer expressions
> Opcodes/Loris/src/lorisgens.C: In member function `long
> int LorisReader::updateEnvelopePoints(double, double,
> double, double)': Opcodes/Loris/src/lorisgens.C:578:
> warning: comparison between signed and unsigned integer
> expressions
>
> The only other problem is getting this to find tcl.h.  I
> have a link from /usr/include/tcl.h to
> /usr/include/tcl8.3/tcl.h, but it still isn't being found.
>
> The biggest surprise in attempting to get CsoundVST built
> was the enormous amount of disk space consumed while
> building boost; wow!
>
> Lastly, what sort of problems result if Python 2.3 rather
> than 2.4 is used?  I'm going by a remark in the
> installation notes for cabel about a problem with
> processes and csound when using Python 2.3.
>
> Other than that, I can build Csound5, and it seems to
> work.  :-) Thanks for all of the work that so many of you
> have put into Csound!
>
> --
>    R. D. Davis                The difference between
> humans & other animals: an www.rddavis.org  410-744-4900
>  unnatural belief that we're above Nature & her
>      Dangling Spiders              other creatures, using
> dogma to justify such
>    Electronic Music Studio           beliefs and to
> justify much human cruelty. --
> Send bugs reports to this list.
> To unsubscribe, send email to
> csound-unsubscribe@lists.bath.ac.uk

Are you using Makefiles or scons?
==John ffitch

Istvan Varga wrote:

>On Sunday 18 December 2005 17:56, R. D. Davis wrote:
>
>  
>
>>Hi, thanks.  Doing that solves the Loris problem. :-)  Now to figure out
>>what's going on with Opcodes/stk/stkOpcodes.cpp not being found...
>>    
>>
>
>This file should be included with the Csound5 CVS sources. You also
>need the STK sources from here:
>  http://ccrma.stanford.edu/software/stk/download.html
>  
>
Csound5 is starting to look like a real hodge-podge of stuff. The stk 
page says this: "all source included, no unusual libraries, and no 
hidden drivers" about itself. In fact it looks as though one could do a 
whole lot of synthesis using stk alone. What is csound for? It seems 
like just that: a collection of unusual libraries from various places, 
the whole structure made inconsistent and unstable by a single change in 
any of them. Earlier versions of csound seemed to be more or less 
self-contained but now so much of the functionality has been offloaded 
onto code from other projects that perhaps it would be better to develop 
a csound operating system instead of a program.
I would have enjoyed having a csound core library with no graphics, 
MIDI, OSC, python, tcl/tk, etc., one that could be used for sound 
synthesis. I thought the api would provide this but I can't compile it 
because it needs all this other stuff, which I don't need. In fact it 
seems like I could make most of csound out of stk or pure data. This is 
a bit circular, no?

...2 cents in coin of the realm.

Martin