Hello Dan, I was busy this week, so this was delayed a couple of days.
> I have now begun to work on a JUCE audio library RB plugin for my own project > needs. If successful its highly likely that i'll contact you to work out a > deal where hopefully you will agree to market and sell it for a cut. Okay. > But although I already have written two RB plugins successfully for my own > projects in Xcode3 ( im only building on OSX ) I am having frustrating > problems in XCode 4 setting up a project with target settings to build a > macho dylib that can be loaded in a Realbasic app and debugged in xcode . > Its been ages since i had to fuss with build settings etc, over which i > usuallylose hair and resort to the bottle.. I'm still using Xcode 3. No idea about Xcode 4, but I expect things to be similar. First I'd change the name of the project to JUCERBX.dylib and machotype to bundle. You need a .dylib file and if you use "file" command in terminal, it should show Mach-O bundle i386. Also you need to define exports file. That's a textfile named "exports.txt" inside Build/MacOSX folder. And in the settings you put this file name "exports.txt" into Export Symbol File setting. This exports.txt file contains only one line with "_REALPluginMain", the name of the main function. Now you can compile and on link, you get some link error with objective-c classes. > i'm willing to PayPal you £100 for taking the time to look into this. I'd be happy to take the money :-) > 1) After copying the built dylib to the RB plugins folder, and launching > the RB IDE, none of the two JUCE plugin classes appear in the RB IDE. Well, the plugin does not load because the REALPluginMain function is not exported. > 2) I cannot seem to get Xcode to output an executable with a dylib extension, > so for the moment i just manually add the .dylib extension and copy it to my > /Applications/REALbasic/Plugins folder. in my previous projects i recall > being able to have xcode automatically put the dylib extension on the end. in the settings it's product name where you enter the name with dylib. > 3) I'd like to configure the xcode build settings so that for debugging > purposes, a BUILD will automatically copy the resultant dylib into > /Applications/REALbasic/Plugins, ready for testing in RB. Looks like you have this install path already there. Of course you could simply add a compile step there and have a cp command run. > 4) I cant figure out how to Ive also not been able to figure out how to > configure XCode so i can launch RB or a test RB app - and be able to debug > the PluginEntry() call to my dylib.. I never used that. But you can use "run paused" in Real Studio and copy the dylib right into the compiled app in the frameworks folder. > 5) Although for quite a while - I am fine to just continue working with a > dylib, it would be great if you can configure the build settings so that a > proper .RBX package that follows the RB plugin specification can be > output. For rbx file you need a little RB utility coming with plugin SDK. Greetings Christian -- Read our blog about news on our plugins: http://www.mbsplugins.de/ _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
