Re: Broken Project
Re: Broken Project
- Subject: Re: Broken Project
- From: Scott Tooker <email@hidden>
- Date: Tue, 26 Oct 2004 10:54:42 -0700
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. 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.
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.
Scott
On Oct 20, 2004, at 11:38 PM, Jeff Laing wrote:
I have an odd problem which I'm sure is just a setting somewhere in
XCODE
but I can't for the life of me find it.
I have a project that I've been working on for quite some time, and
its been
working fine, both in Debug mode and with Release builds.
Stupidly, I tried rearranging a bunch of stuff, and somehow I appear
to have
broken the ability to run the App from within XCODE.
When I "Build and Run", the build works, the application starts up
(ie, it
shows in the Activity Monitor) but it doesn't appear in the dock, nor
does
its menu become visible, etc. It just sits there eating cycles.
Running by double-clicking the icon in the Finder works fine.
Running from XCODE through Shark (part of CHUD) works fine.
Its just running from within XCODE that doesn't, nor launching via the
debugger in XCODE.
The only thing I can think of that *might* have caused it is that I
rearranged where I built my subordinate frameworks, but I thought I
got that
right.
The app is factored into a real application, and a utility framework
which I
was intending to use in other apps, and as such was building straight
into
/Library/Frameworks. This caused grief when you did a clean because
permissions got themselves knotted - so I moved the framework into the
same
build directory as the executable, and updated the library search path
appropriately (this is all part of incremental development, I finally
got
around to doing the installer package)
Sadly, this all happened before I managed to get CVS working so I
can't roll
my project back to a working state. What baffles me is that I don't
understand why the app doesn't startup properly - I could believe it
if it
started bouncing in the dock, or gave me syslogs about missing
frameworks.
But to sit there doing nothing (but burning cycles) smells of having
goofed
something really odd.
Does anyone have any clues on where to look for this sort of problem?
Jeff Laing <email@hidden>
------------------------------------------------------------------
I got a lot of ideas. Trouble is, most of them suck.
---George Carlin
_______________________________________________
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
_______________________________________________
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