I was actually just going to send an email round to the devs about QS and build, and I'd been unable to build the release config.
Today I deleted the 'ppc' from valid 'ARCHS' in the Release.xconfig file, and I managed to build it. I followed the exact instructions on the wiki in order to build, plus deleting the 'ppc' as I've just mentioned. I think the main problems I'd had with it not building was the fact that I was running XCode 3.2.4 until this morning when I upgraded to the latest verson. Clang/LLVM seems to change quite a bit between versions, so I'd suggest making sure you're on the latest one. The QSFramework source tree is needed to build plugins. In order to build QS just use the QS_SOURCE_ROOT source tree as mentioned in the wiki. If you're on XCode 4, I can't help with that atm as I don't have it. **** For all users and developers reading this **** Do we have many users on Leopard who are still using PPC (older, non Intel) machines? I think that seeing as: SL is Intel only b54 is supposed to be better for Leopard anyway PPC is just annoying in XCode we should remove ppc support from the latest Quicksilver version and make it Intel only. On 18 March 2011 09:51, Henning Jungkurth <[email protected]>wrote: > Hi, > > I just tried to get into QS development again after quite a while. > Some things I noticed that could help make things easier for other > developers trying to get started: > > * The release build configuration doesn't work with a fresh clone. I > had to fiddle a bit to get it to work. I think it didn't work, because > the debug config only builds for i386 architecture, while the release > config was supposed to build for i386 and ppc. Maybe there were also > other issues, but that's the only one I know for sure. > Maybe someone who actually knows what he's doing should have a look at > that. :-) > > * 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" > - The one on the wiki (http://qsapp.com/wiki/Building_Quicksilver) > mentions the QS_SOURCE_ROOT source tree > - There's also the README for the plugins > (https://github.com/quicksilver/Plugins/blob/master/README.markdown), > which mentions a QSFramework source tree > - And there are even more instructions in the plugin development > reference ( > https://github.com/quicksilver/Plugins/blob/master/PluginDevelopmentReference/QuicksilverPlug-inReference.mdown > ) > > 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. Of course all the other places > should link to it. > > > 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? >
