Re: Cocoa application does not run outside of Xcode
Re: Cocoa application does not run outside of Xcode
- Subject: Re: Cocoa application does not run outside of Xcode
- From: Rosyna <email@hidden>
- Date: Thu, 23 Sep 2004 04:05:33 -0700
dyld should log something to the console about a missing library when
this occurs. Make sure the install name of the library is the same as
the path where it can actually be found as well.
Yeah, I didn't need to quote it all.
Ack, at 9/23/04, Daniel Spelmezan said:
I have a strange problem with all my Cocoa applications that use
external .dylib libraries, which I add from /usr/local/lib to my
Xcode project.
Within Xcode, the app runs as expected without errors, but when I
double-click the executable in my build products directory, the app
will not run. The icon will appear in the dock and disappear
immediately thereafter, without generating any errors at the console.
Yet, if I right-click the executable in Finder and select "Show
Package Contents", browse to the Contents/MacOS directory and
double-click the unix executable file in there, a terminal pops up
that launches the app, which then runs as expected.
If I do not instantiate the class that uses the functions in the
external libraries, this problem does not occur. I have also tried
other "Library Style" linking options (static, dynamic, bundle) and
checked the corresponding paths for the libraries, tragets, etc.,
without any success.
Did someone experience a similar problem? Why is the app running
when I click the "build and go"-button in Xcode or when I
double-click the file within the executable's package directory
Contents/MacOS, but not when I double-click the executable itself in
the build directory?
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
_______________________________________________
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