At first when I started to take a look the the Services plugin I was thinking the same. I was also adding a custom executable (namely the Quicksilver.app build product from the QS source tree) and using that to bootstrap the plugin I was debugging. And for me at least this worked. (P.S. if you still want to go this route make sure you have "load symbols lazily" in the Debugging preferences pane from Xcode's prefs turned OFF).
However, as Etienne showed me there is also another way. As I understand it, the way the QS build system is set up is that whenever you build a plugin from blacktree-elements-public (QS' plugins) it will copy itself into the QS build product location into Resources/ PlugIns. With that in place, you can set breakpoints in the plugin's code, set breakpoints in QS' code and just start debugging QS itself. Whenever QS loads/uses your plugin Xcode is smart enough to find debugging symbols for the plugin and hit your breakpoint. (I don't know if you have to have both Xcode projects open or if that doesn't matter). Here's some posts where this is discussed further: http://groups.google.com/group/blacktree-quicksilver/browse_thread/thread/bb2d870572289bba http://groups.google.com/group/blacktree-quicksilver/browse_thread/thread/ccf43942bc5eb4a1 HTH! André On 1 Sep., 11:09, cialz <[email protected]> wrote: > Hi to all, I'm new to QS plugin development. I've done some VST audio > plugins in the past, to debug them with Xcode the only thing to do was > adding the host application as Custom Executable. > > I've tried to do the same thing adding quicksilver but without > success, any breakpoint wasn't reached during execution of the action. > > Any help is very appreciated.
