RE: Broken Project
RE: Broken Project
- Subject: RE: Broken Project
- From: Jeff Laing <email@hidden>
- Date: Wed, 27 Oct 2004 08:31:24 +1000
> While I can't tell for sure what is going on, I can provide a better
> way to deal with developing using the latest app and framework builds.
> I'm assuming that the framework you are building is in a separate
> project from the application.
Nope, my project has the framework (and it will have several more before I'm
finished), a testbed app (that exercises it pretty thoroughly in
"console-mode", and the actual Cocoa app with the pretty GUI. I have other
projects set up this way and they work fine.
Doing this means that XCODE maintains dependencies properly, because I'm
still adding features to the framework headers as time goes by, and I need
it to all build correctly.
I even have all the files for building the installer package - I really want
this to be properly self-contained.
> If so, just make sure that the
> application and the framework projects share the same build products
> directory (this can be set in the project inspector, the General tab).
>
> Xcode always adds the build products directory to the list of paths to
> find frameworks in, so this way you'll pick up the latest build of the
> framework, even if an older version is installed in the system.
The problem with this is that the built product can *only* be run from
within XCODE, which is more than tedious - its functional enough that I
already use the app in anger from its build location.
And its not "the right shape" to be dumped into the installer package. See
other threads about "framework installation path" a few weeks back.
> If you placed the framework along side the exectuable (i.e.
> myApp.app/Contents/MacOS/), then dyld will never find the framework
> since it doesn't look there. This doesn't explain why the app is
> running outside of Xcode, but it would be interesting to see
> if making these changes solves the problem.
I've tried pushing it all into the same build directory and it made no
difference - running from the finder would work, running from inside Xcode
would spin.
Recently, I've been wondering whether perhaps its some sort of "process
ownership" thing - I've been using one of these "dock alternatives" (Butler)
to load XCode, and I wonder whether perhaps thats somehow interfering with
the effective user-id of Xcode, or its children, or some other
"quota-related" thing. But I'm sure that it was working fine even from
Butler - it must be something I've goofed in the project.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden