I see that, thanks.

A couple "Source Tree" entries need to be added to XCode before you
can build QS.
XCode->Preferences->Souce Trees->'+' (plus sign)

Settings Name                Display Name                  Path
QSFramework                 Quicksilver Framework   /Applications/
Quicksilver.app/Contents/Frameworks
QS_SOURCE_ROOT     Quicksilver source root   ~/XCodeProjects/blacktree-
alchemy/Quicksilver

Apply, then build. For the very first target to build select
"Quicksilver Distribution".  This just ensures that all the plugins
and extra stuff is built as well, afterwards you can just build the
Quicksilver targtet.

Initially you've been running QS from the Applications directory, make
sure you've quit QS before running from XCode.  When running QS from
XCode for the first time it may quit on its own and a debug message
says "Debugger stopped".  Just hit "Build and Debug" again.  This time
you might see 2 instances of QS (I run it from the menu bar and I'll
see 2 QS icons), quit both of these. Then finally hit "Build and
debug" again, everything should be fine.  You won't have to deal with
that again until you run QS normally from the Applications directory.

QS build files are located in
/tmp/QS/build/Debug
/tmp/QS/build/Release


On Mar 23, 5:25 am, Rob McBroom <[email protected]> wrote:
> On Mar 23, 2010, at 1:48 AM, Paul Kohut wrote:
>
> > Just looked at issue 8 and now remember seeing what you describe back
> > when I was getting familiar with the QS code.  I'll make looking into
> > this a priority. IIRC, it had something to do with the command/action/
> > paste board stuff.  Will keep you up to date.
>
> Thanks! If you can help me with the issues building Quicksilver itself, I can 
> probably look into it as well. If you look at the last comment I posted on 
> there, it narrows it down some.
>
> --
> Rob McBroom
> <http://www.skurfer.com/>

To unsubscribe from this group, send email to 
blacktree-quicksilver+unsubscribegooglegroups.com or reply to this email with 
the words "REMOVE ME" as the subject.

Reply via email to