| Recently, on Win XP with the 5.07.2 float installation, I've experienced
something new.
I have also a completely self-contained, selective Csound directory with
everything needed to perform my compositions. When no environment variables
are installed, all works fine.
However, when I do a completely separate 5.07.2 installation, resulting in
environment variables being added, my "self-contained" (everything in and
run from a single directory) Csound gives errors and won't run (specifically
it gives two "can't find Python25.dll" errors). Deleting *all* environment
variables (just PYTHONPATH deleted doesn't do), we're back to running fine
again.
Bottom line question: I thought that first, Csound looks for the files it
needs in the current directory, and runs fine if everything needed is there.
However, now it seems that adding environment variables changes something -
like maybe where Csound looks first. (This is likely because my
"self-contained" Csound is a slightly older version.)
So, is the default directory, and the first searched, the current directory
or not? Has this changed recently? If so, can someone point me to where in
the docs such matters of order and priority are discussed? (I've seen such
for command line flags, but not for files.)
Art Hunkins
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |