| Thanks Victor. I have my bundle now but when calling
csound->Compile("bla.csd") return an error, the bla.csd is in the same
directory as the executable but it won't see it. If I change the name
of bla.csd to match the name of the bundle it gets past Compile() but
fails when I try to start performance. The fail on performance seems
to have something to do with the CsoundPerformanceThread class and
wxWidgets..
2009/8/18 :
> yes, it's just a matter of linking using -bundle and then copying
> everything into the plugin directory structure. See this for
> VST plugins (plugin code in plugin.cpp and vstsdk2.4 in the
> current dir):
>
> g++ -bundle -o plugin plugin.cpp
> vstsdk2.4/public.sdk/source/vst2.x/audioeffect.cpp
> vstsdk2.4/public.sdk/source/vst2.x/audioeffectx.cpp
> vstsdk2.4/public.sdk/source/vst2.x/vstplugmain.cpp
> -I vstsdk2.4/public.sdk/source/vst2.x/ -I vstsdk2.4
>
> On OSX we have to drop the dynamic module inside a bundle, together with a couple of files. The first one of them is called info.plist and is an XML file that looks like this:
>
>
>
>
>
>
> CFBundleDevelopmentRegion
> English
> CFBundleExecutable
> plugin
> CFBundleIdentifier
> com.apple.carbonbundletemplate
> CFBundleInfoDictionaryVersion
> 6.0
> CFBundleName
> plugin
> CFBundlePackageType
> BNDL
> CFBundleShortVersionString
> 1.0
> CFBundleSignature
> ????
> CFBundleVersion
> 1.0
> CSResourcesFileMapped
>
>
>
>
>
> The only important thing as far as we are concerned is that we give the correct name of the plugin library file we compiled (shown above in bold letters). The bundle structure is created with the following commands:
>
> mkdir plugin.vst
> mkdir plugin.vst/Contents
> mkdir plugin.vst/Contents/MacOS
> cp plugin plugin.vst/Contents/MacOS
> cp info.plist plugin.vst/Contents/
>
> The second file we need is just a text file with eight characters ‘BNDL????’, which can be created like this:
>
> echo “BNDL????” > plugin.vst/Contents/PkgInfo
>
> The whole bundle directory structure looks like this:
>
> plugin.vst
> /Contents
> /info.plist
> /PkgInfo
> /MacOS/plugin
>
> Finally, we want to hide the directory structure inside the bundle, so the Finder sees it as a single file. We can use the command:
>
> /Developer/Tools/SetFile -a B plugin.vst
>
>
>
>
>
>
>
>
>
>
>
>
>
> ----- Original Message -----
> From: Rory Walsh
> Date: Tuesday, August 18, 2009 11:47 am
> Subject: [Csnd] [OT] bundles on OSX...
> To: csound@lists.bath.ac.uk
>
>> It seems the easiest way to create bundles on OSX is to use
>> xcode, but
>> what if one is using g++ to build their applications. Can I
>> create a
>> bundles manually, or better still does anyone know of python script
>> that will do it for me?
>>
>> Rory.
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> "unsubscribe csound"
>
> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
> National University of Ireland, Maynooth
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |