Hi all,

I was thinking today about the float/doubles issue with opcode libraries 
  being compiled for csound or csound64.  Should we have an OPCODELIB64 
environment variable that csound64 checks for loading opcode libraries? 
  Or perhaps a convention that opcode libraries that end with 64.dll or 
64.so or 64.dylib will be ones that csound64 uses to load and stay with 
one OPCODELIB environment variable?  I think I like the second 
convention.  I think in the end I'd like to be able to have both csound 
and csound64 installed on my system and don't want to have to spend time 
doing any tricks for the right libraries to be loaded.

Any other thoughts on this?

steven

This is the ideal:  No user concerns.

If we do this correctly (not sure exactly what that is), then we could even
make it possible on MacOS X (and maybe OS 9) to include both the 32-bit and
64-bit versions of a library in the same bundle.  Csound would automagically
use the right one and the user would never be the wiser.

Anthony Kozar
anthony.kozar@utoledo.edu
http://akozar.spymac.net/
 

On 7/20/04 5:32 PM, steven yi etched in stone:

> I think in the end I'd like to be able to have both csound
> and csound64 installed on my system and don't want to have to spend time
> doing any tricks for the right libraries to be loaded.