On Nov 16, 8:33 am, Etienne Samson <[email protected]> wrote:
> Depending on the Configuration you build, final files should end up in 
> /tmp/QS/build/$CONFIGURATION_NAME/ (where $CONFIGURATION_NAME is either Debug 
> or Release). You can also just launch /Applications/Quicksilver.app, since 
> this one should be overwritten at each build (but only if the build didn't 
> fail, eg. no errors show up in the Build Log).
> I got rid of the ugly QS_SOURCE_ROOT recently, but I'm afraid building in 
> /tmp/QS creates a duplicate Quicksilver, which is then likely to confuse the 
> Pasteboard server (pbs), and then make Get Current Selection whacky, as 
> pointed out by André.

Right, I've got it building into /tmp/QS/ as an application bundle on
my work machine, but it doesn't update my /Applications install.
Copying it across manually and running it works, but my trigger key
(⌘SPACE) doesn't trigger QS. Interestingly downloading andreberg/
blacktree-alchemy binary version does work just fine, they should
basically be the same build. I built the release version, and don't
see any errors in console when running my built version, it just fails
to listen to my trigger. I've reset my appdata/prefs to see if that
helped; it didn't. I'll try the debug version and see if that gives me
more logging or something.

Thanks, Ian





Reply via email to