> >>
> >>     Mac
> >>
> >> No info yet.

Well, that certainly will not do...

If the user has  a Mac that shipped with an OS X version prior to 10.3
(includes 10.2 and 10.1) then it is possible that the default shell is
the Tenex C-shell (tcsh). If this is the case, then you either have to
type

~% setenv OPCODEDIR "/Users/you/your/Csound5/build"

or change your /etc/profile and or edit your .tcshrc file.

If the user has a Mac that shipped with OS X 10.3 or 10.4 then it
likely has the "Bourne-again" C-shell (bash) as the default shell. If
this is the case, then the user must type something like

~$ export OPCODEDIR=/Users/you/your/Csound5/build

in addition if the bash shell is the default, then it is usually
easier to edit your .bashrc or /etc/profile.

Note that if users choose one of the above methods, ie editing the
.bashrc file then the environment variables are executed when a new
shell is created. This can be problematic if your application
implements a Quartz or Aqua interface and does not use the
commandline.

If this is the case, then the standard solution (up to OS 10.3.9) is
to create an XML property list file (called a .plist file by the OS).
This file should nominally be located at ~/.MacOSX/Environment.plist.
This has been a solution specifically for the [csoundapi~] object for
Pd on OS X. Since Pd uses an OS X native .app style packaging, and
runs off of the Aqua interface, the standard means of supplying
environment variables to Csound do not work. The solution is to set
Csound's environment variables for the Aqua environment.

Likely, most users will not have the hidden folder .MacOSX located in
their $HOME directory (aka ~/) This folder must first be created and
the Environment.plist added to this folder. The contents of the
Environment.plist file should be something like

<?xml version="1.0" encoding='UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>OPCODEDIR</key>
    <string>/Library/Frameworks/CsoundLib.framework/Versions/5.1/Resources/Opcodes</string>
    <key>OPCODEDIR64</key>
    <string>/Volumes/ExternalHD/devel/csound5/lib64</string>
    <key>INCDIR</key>
    <string>/Volumes/ExternalHD/CSOUND/include</string>
    <key>SFDIR</key>
    <string>/Volumes/ExternalHD/iTunes/csoundaudio</string>
  </dict>
</plist>

and so on, using the XML <key> tag for each environment variable
required by the API and the <string> tag for it's corresponding path
on the system.

This technique is confirmed to work on Mac OS X up to and including
Mac OS 10.3.9. I don't currently have any Macs with Tiger installed
but from what I have tested, this facility has been changed or
depcrecated in Mac OS 10.4.x.


-David