Targets

1. You can set various options here, e.g. Build Styles (Development vs. Deployment), and Optimization (under GCC Compiler Settings).
2. You may want to remove /Users/mike/code/bibdesk entry under Search Paths, since it will give you a warning, but it's basically harmless.
3. Build and run it.
4. If there are errors, the log output is fairly descriptive. If ProjectBuilder can't find a file, it will list it in red, but you might have to start expanding the file tree or use the search. Much of what ProjectBuilder does is beyond my ken, so I usually just muddle around until I find something that looks broken. It is helpful to look at the Build Phases for the Bibdesk target, though, since that will usually give you a clue where things stopped.
5. The Omni frameworks should be copied into Bibdesk.app/Contents/Frameworks automatically in the build process, so the resulting app can run on a machine that does not have them. You can check this by `otool -L Bibdesk.app/Contents/MacOS/Bibdesk` which should reference the Omni frameworks like this:

     @executable_path/../Frameworks/OmniAppKit.framework/Versions/2001A/OmniA
     ppKit (compatibility version 1.0.0, current version 1.0.0)
   

   This tip is from the cocoadev article.