On Mar 17, 2011, at 6:51 PM, Henning Jungkurth wrote: > * There are a lot of different build instructions around the project: > - The README at github > (https://github.com/quicksilver/Quicksilver/blob/master/README.markdown) > say, it "should just work"
I think this is pretty out of date. > - The one on the wiki (http://qsapp.com/wiki/Building_Quicksilver) > mentions the QS_SOURCE_ROOT source tree This was valid the last time I tried it, but there have been some commits that changed the Xcode project recently, so I can't promise it's right. It sounds like if we remove PPC, those instructions will be correct. Is it still necessary to build "Quicksilver Distribution" by hand first? > - There's also the README for the plugins > (https://github.com/quicksilver/Plugins/blob/master/README.markdown), > which mentions a QSFramework source tree Just looked it over and I believe it's correct. > - And there are even more instructions in the plugin development > reference > (https://github.com/quicksilver/Plugins/blob/master/PluginDevelopmentReference/QuicksilverPlug-inReference.mdown) Everything in there should be up to date and correct. > I'm not really sure, which of these is the most current and which is > actually needed. They all should combined somewhere. I guess the wiki > would be the best place for that. To some degree, but the wiki doesn't support Markdown and I'm not going to rewrite the reference in another format. :) The wiki at least links to all of these places. > I also couldn't quite figure out how to debug plugins. I found an old > thread on this list > (http://groups.google.com/group/blacktree-quicksilver/browse_thread/thread/ccf43942bc5eb4a1) > explaining how to do it. But I couldn't get it to work. Even once the > plugin was in the correct folder, load symbols lazily was disabled and > I started debugging QS, in the plugin there still were just the yellow > breakpoints. What did I miss? I haven't even attempted this, but if you figure out how to do it, let me know. It would be useful to have in the plug-in development reference. -- Rob McBroom <http://www.skurfer.com/>
