On Friday 09 December 2005 17:30, Victor Lazzarini wrote:

> The framework is build with the following structure
>
> CsoundLib.Framework/
>              Headers/        -> Versions/Current/Headers
>              Resources/     ->  Versions/Current/Resources
>              Versions/
>                       5.0/
>                            Headers/ [csound headers]
>                            Resources/
>                                  Opcodes/ [Opcodes 32-bit floats]
>                                  Opcodes64/ [Opcodes 64-bit floats]
>                                  info.plist  (property file for the
> framework) CsoundLib   (the dynamic library)
>                       Current/  -> ./5.0
>              CsoundLib     -> Versions/Current/CsoundLib
>
>
> This whole directory is then put in the standard place for frameworks
> which is /Library/Frameworks; when linking to frameworks it is necessary

Should I change the default plugin directories for the "release" build
to /Library/Frameworks/CsoundLib.Framework/Versions/5.0/Resources/Opcodes
and /Library/Frameworks/CsoundLib.Framework/Versions/5.0/Resources/Opcodes64 ?
Also, if the version is in CS_VERSION.CS_APIVERSION format (that is, 5.1 until
the first binary incompatible API change after the release), then the default
directory names can easily be generated in csmodule.c. Or should the 5.0 be
hardcoded for now ?


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net