Just committed my changes to the subversion repository.
A few new features and general stability improvements, but mostly a very thorough cleanup of the source code, so you can actually compile it now.
Compilation Instructions
Open Xcode preferences, scroll across to Source Trees and add one with a Setting Name of “QSFrameworks” and path of /Applications/Quicksilver.app/Contents/Frameworks/.
Then unzip Quicksilver.xcodeproj.zip, and open the Quicksilver.xcodeproj project in Xcode. Make sure you set the Active Build Configuration to “Release”. Click the Build button and you’re away.
Note: This build appears to be incompatible with the File Tagging plugin.
36 Comments so far
Leave a commentExcellent! Now are you planning on releasing a nice universal binary of that or do I need to dust of my compiler?
=]
reasonded by Dave Bullock on December 13, 2007 9:25 am | Permalink
Ankur,
I simply want to thank you for all the work you’ve done and plan to do on Quicksilver.
Cheers,
-John
stated by Ankur on December 13, 2007 10:17 am | Permalink
How does a non-programmer take advantage of your hard work?
written by Jeremy on December 13, 2007 10:29 am | Permalink
I’m still having trouble compiling the branch. Which build configuration should work - debug or release? On debug, I get an error about QSCore not being found and on release, I get an error about QuickStep foundation “-filelist “.
Of note, both the paths Xcode gives me for these errors are looking in a directory called ppc down in the hierarchy, and I’m on an Intel Mac.
I’m running Xcode 3 on 10.5.1. Also, I’m almost completely unfamiliar with Xcode. So, step by step instructions would be awesome, if possible.
Thanks for all the effort you’re putting in to this.
composed by exark on December 13, 2007 10:48 am | Permalink
Thanks for that, having read that QS was being orphaned I’d decided to take a look at the source as a means of getting into Mac programming (having been a mainframe and windows prgrammer for longer than I care to remember) and got as far as failing to compile it…
I know it’s not the easiest place to start but I will see how I get on and may be able to be of some slight use, albeit slowly.
mentioned by Bill Hughes on December 13, 2007 11:59 am | Permalink
I’ve added instructions on how to compile the source. I can host the compiled application as well, but give me a few days to set up a workflow.
written by Ankur on December 13, 2007 1:55 pm | Permalink
Thanks, compiled and everything. It crashes within 15 seconds on Leopard. Do you want a crash log?
recorded by exark on December 13, 2007 2:39 pm | Permalink
The debug config is busted. I’ve submitted patches to Ankur and he is reviewing them. exark, the filelist error will go away if you follow the compilation instructions that Ankur posted.
published by adhamh on December 13, 2007 2:40 pm | Permalink
Thanks, Exark. I don’t have Leopard, so a crash log would be great.
posted by Ankur on December 13, 2007 2:41 pm | Permalink
Any chance to have it for people w/o XCode?
spoken by NilColor on December 13, 2007 6:12 pm | Permalink
Have just compiled it on Leopard. What’s a bit bad is that the buildscripts try to do a mkdir /Applications/Quicksilver.app, which is not possible if you don’t have admin rights. Also, it crashes on 10.5.1 as previously described. If i can help with further debugging the crashes, let me know.
stated by Martin Hauser on December 13, 2007 7:43 pm | Permalink
I tried to compile it but I get this error message:
http://myskitch.com/halbtuerke/quicksilver_-_build_results-20071213-115040.png
Greetings and thanks for your efforts.
reported by Patrick on December 13, 2007 8:57 pm | Permalink
Wait a minute. Why are you setting up XCode to point to frameworks in the compiled version of the app in your Applications directory? This would seem to imply you’d already have to have Quicksilver installed in order to compile it. Shouldn’t these frameworks be copied somewhere else in the source tree and compiled from there?
voiced by Rick on December 14, 2007 12:40 am | Permalink
why “/Applications/Quicksilver.app/Contents/Frameworks/”?
Does this mean that we need to have a previous version of QuickSilver in order for compiling?
Thank you very much for the hard work!
mentioned by mediter on December 14, 2007 1:36 am | Permalink
I’ve compiled it. Download it from here:
http://www.mediafire.com/?7wm0q2msr42
Thanks Ankur
professed by Robert on December 14, 2007 4:21 am | Permalink
Exark, did you have any luck? I’ve run into the same issue.
announced by Adam Black on December 14, 2007 4:41 am | Permalink
Yeah, I got it to copile with the build settings suggested and I got it to run by deleting my Quicksilver folder in ~/Library/Application Support
posted by exark on December 14, 2007 5:20 am | Permalink
I’ve compiled it. Download it from here:
http://www.mediafire.com/?7wm0q2msr42
Thanks Ankur
-I posted this earlier but it only shows up when I visit this page in firefox on my computer, not in safari or on other computers, which is very strange…
*Edit: And now that I posted this, my old comment shows up in Safari, but the number of comments at the top of the page ignores by posts…
proclaimed by Robert on December 14, 2007 5:32 am | Permalink
Robert, your build crashes for me on Leopard with a Bus Error on startup, without even showing the crash reporter. I get similar behavior with a build I did myself, except it shows the Crash reporter. I didn’t delete my QS application support folder, so this report is probably of little value /-:
posted by Andreas Fuchs on December 14, 2007 11:02 am | Permalink
Great work all!
I get a silent crash when installing the file tagging plugin, only removing file tagging plugin will allow restart, then it works (so far). This is on Leopard, after deleting my previous App support/QS folder…
mentioned by Ian on December 14, 2007 11:19 am | Permalink
Andreas Fuchs: I’m not sure why its crashing for you - I had no problems compiling or running it (on Leopard). I don’t know enough about Quicksilver to help you; I just followed the directions that Ankur gave above.
Perhaps it would be easiest if Ankur were to post a compiled version of Quicksilver
expressed by Robert on December 14, 2007 11:47 am | Permalink
I am getting a crash whenever I try to start this. This is with my previously installed plugins and preferences.
2007-12-13 22:23:58 -0500
EXC_BAD_ACCESS (0×0001)
KERN_PROTECTION_FAILURE (0×0002) at 0×00000020
Thread 3 Crashed:
0 objc_msgSend + 24
1 -[QSFileTagsPlugInSource objectsForEntry:] + 204
2 -[QSCatalogEntry scannedObjects] + 396 (QSCatalogEntry.m:499)
3 -[QSCatalogEntry scanAndCache] + 216 (QSCatalogEntry.m:519)
4 -[QSCatalogEntry scanForced:] + 1112 (QSCatalogEntry.m:565)
5 -[QSLibrarian scanCatalogIgnoringIndexes:] + 704 (QSLibrarian.m:513)
6 -[QSLibrarian scanCatalog:] + 92 (QSLibrarian.m:541)
7 forkThreadForFunction + 108
8 _pthread_body + 96
It starts successfully with nothing installed, but crashes (among other times) when installing the file tagging plugin and when trying to open the Scripts category in the catalogue pane. I’ll try to dig up the crash logs for those too.
I wanted to debug it, but there seems to be no way to build the Debug configuration. A little bit of fiddling with the project configuration got me to the stage of building everything successfully, but then failing to put it all together.
Otherwise, thanks for this. It was nice at least catching a glimpse of the new features.
announced by Eris on December 14, 2007 1:28 pm | Permalink
Here is the stack trace after installing File Tagging:
Thread 3 Crashed:
0 libobjc.A.dylib 0×90a400f8 objc_msgSend + 24
1 …uicksilver.QSFileTagsPlugIn 0×0150f0f8 -[QSFileTagsPlugInSource objectsForEntry:] + 204
2 com.blacktree.QSCore 0×37041cc0 -[QSCatalogEntry scannedObjects] + 396 (QSCatalogEntry.m:499)
3 com.blacktree.QSCore 0×37041fd0 -[QSCatalogEntry scanAndCache] + 216 (QSCatalogEntry.m:519)
4 com.blacktree.QSCore 0×37042770 -[QSCatalogEntry scanForced:] + 1112 (QSCatalogEntry.m:565)
5 com.blacktree.QSCore 0×37014790 -[QSLibrarian scanCatalogIgnoringIndexes:] + 704 (QSLibrarian.m:513)
6 com.blacktree.QSCore 0×37014a7c -[QSLibrarian scanCatalog:] + 92 (QSLibrarian.m:541)
7 com.apple.Foundation 0×92be40c0 forkThreadForFunction + 108
8 libSystem.B.dylib 0×9002bd08 _pthread_body + 96
My installed plugins:
QSUIAccessPlugIn
QSKeychainPlugIn
QSCorePlugIn
QSSafariPlugIn
QSiTunesPlugIn
QSShelfPlugIn
QSFileTagsPlugIn
QSSymbolicHotKeyPlugIn
QSAppleMailPlugIn
QSClipboardPlugIn
QSiPhotoPlugIn
QSAddressBookPlugIn
QSHotKeyTriggerPlugIn
QSFlashlightInterface
Let me know if I should supply more/different information.
recorded by Eris on December 14, 2007 2:38 pm | Permalink
I gave this build a try on Leopard (Thanks Robert). I didn’t remove the files from Application Support & Quicksilver wouldn’t start up.
So I removed the tagging plug-in & now it will work OK, so it definitely looks like a problem between this version & the tagging module.
Alcor said at the Quicksilver forum that ‘Most of the plugin source still hasn’t been released yet’, so hopefully he’ll release this soon & this problem can be fixed.
The tagging plug-in is one of my most used ones in Quicksilver.
recorded by Jono on December 14, 2007 7:35 pm | Permalink
Hey Ankur
This is me, manning the appreciation stations. You´re cool in my book, keep up the good work.
divulged by soundmasterj on December 15, 2007 10:56 pm | Permalink
I tried this yesterday on Leo. It worked fine. Haven’t tested any plugins because frankly it’s not our cuppa. But it’s a well behaved app in all respects I could see. No intrusion, extra files only in acceptable locations, and above all a reasonable footprint. Very nice.
I used this link: http://www.mediafire.com/?7wm0q2msr42. I pruned out headers, private headers, classes.nib, and info.nib and got it down by about 500 KB. It’s a far cry from what it used to be. Please let us know when you have a build URL available so we can write about it. At the very least this is a good example of what a difference dedication makes. And it seems QS fans have reason to be overjoyed.
determined by Rick on December 16, 2007 7:56 pm | Permalink
Ok, I’m getting a download link up soon.
proclaimed by Ankur on December 18, 2007 10:59 am | Permalink
Download link here.
recorded by Ankur on December 18, 2007 4:35 pm | Permalink
Going up soon.
http://rixstep.com/4/2/qs,01.shtml
expressed by Rick on December 18, 2007 9:11 pm | Permalink
Thanks Rick.
voiced by Ankur on December 18, 2007 9:26 pm | Permalink
I must say, you are the man for working with this app. The latest release absolutely flies on leopard. There are no more immediate memory hogs. I uninstalled all settings and plugins and started from scratch and it is running great. Keep up the good work.
recorded by Mattie J on February 1, 2008 2:15 am | Permalink
Tried building the latest svn code checked out on 3/17
I added the QSFrameworks path and selected “Release” as the build type. This is the first time I have ever fired up Xcode.
Here are the errors that resulted:
Building target “QSCrucible” of project “Crucible” with configuration “Release” — (2 errors)
cd /Users/isen/downloads/blacktree-alchemy-read-only/Crucible
/Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -strip-debug-symbols -resolve-src-symlinks /Users/isen/downloads/blacktree-alchemy-read-only/Crucible/External/CoreGraphics/CGSPrivate2.h /build/Release/QSCrucible.framework/Versions/A/Headers
pbxcp: CGSPrivate2.h: No such file or directory
pbxcp: CGSPrivate2.h: No such file or directory
cd /Users/isen/downloads/blacktree-alchemy-read-only/Crucible
/Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -strip-debug-symbols -resolve-src-symlinks /Users/isen/downloads/blacktree-alchemy-read-only/Crucible/Code/NDHotKeyEvent_QSMods.h /build/Release/QSCrucible.framework/Versions/A/Headers
pbxcp: NDHotKeyEvent_QSMods.h: No such file or directory
pbxcp: NDHotKeyEvent_QSMods.h: No such file or directory
Build failed (2 errors)
disclosed by Tom on March 18, 2008 9:03 am | Permalink
Tom, that’s the trunk. The version in question is in branches/B5X/.
uttered by Ankur on March 18, 2008 3:07 pm | Permalink
Downloaded the B5X branch code and I still get an error in the build. Building target “QuickStep Foundation” of project “Quicksilver” with configuration “Release” — (1 error)
cd /Users/isen/downloads
/Developer/usr/bin/gcc -E -P -x c -Wno-trigraphs “PropertyLists/QSCore-Info copy.plist” -o “/Users/isen/downloads/build/Quicksilver.build/Release/QuickStep Foundation.build/Preprocessed-Info.plist”
i686-apple-darwin9-gcc-4.0.1: PropertyLists/QSCore-Info copy.plist: No such file or directory
i686-apple-darwin9-gcc-4.0.1: warning: ‘-x c’ after last input file has no effect
i686-apple-darwin9-gcc-4.0.1: no input files
i686-apple-darwin9-gcc-4.0.1: no input files
i686-apple-darwin9-gcc-4.0.1: no input files
i686-apple-darwin9-gcc-4.0.1: no input files
i686-apple-darwin9-gcc-4.0.1: no input files
Build failed (1 error)
First, I have downloaded and I have been using the compiled version at http://lipidity.com/software/quicksilver/. Is there any reason to compile myself?
Second, what exactly is the trunk version all about? Is there a web home for that version? I am on Leopard and I’d like to use the new, slimmer version if possible.
reported by Tom on March 19, 2008 11:54 am | Permalink
Not really, unless you really want to stay up to date.
It’s the Leo-only highly unstable (still being developed) version. At this stage I think it’s only of interest if you want to test it, or if you want to help write code for it (and if you have Leopard).
divulged by Ankur on March 19, 2008 12:41 pm | Permalink
Leave a comment