Re: No launchable executable present at path?

• Subject: Re: No launchable executable present at path?
• From: Mason Mark <email@hidden>
• Date: Fri, 31 Mar 2006 00:50:19 +0900
• Delivered-to: email@hidden
• Delivered-to: email@hidden

Oh, I think we are talking about slightly different situations,

Cheers,

--
Mason Mark
Five Speed Software, Inc.
http://www.fivespeed.com

On Mar 30, 2006, at 10:58 PM, Jeremy Sagan wrote:

I too have seen this frequently and I think it is related to the location of the executable. In my case I moved the executable from its default location.

I do not think you have to create a custom executable to work around this Xcode bug.

Every time I create a new directory, which I do each time I create a new version, I have to manually go the location that Xcode thinks the executable should be and create an alias (symlink) to the actual location. It is easy to tell where XCode wants the alias to go because included in the error message is the complete path.

HTH,

Jeremy

On Mar 29, 2006, at 6:33 PM, Mason Mark wrote:

I see this very frequently.

The trick is, make a new executable (Project menu->New Custom Executable), and enter the same path it is already supposed to be using. You may have to enter a new name, e.g., "MyApp2" (or more likely, "MyAppAgainGodDamnIt"). The other day I witnessed a bug that crashed (the app) and every time it crashed like that, on the subsequent attempt to debug the app, Xcode would freak out in the way you describe, so this procedure had to be done for each debugging session.

Doing this does get extremely tedious, but it is the only way that I know about to solve this recurring issue. Of course for some projects this bug does not manifest, but I have never figured out what things might influence it.

Cheers,
--
Mason Mark
Five Speed Software, Inc.
http://www.fivespeed.com

On Mar 29, 2006, at 9:19 PM, Theodore H. Smith wrote:

Any help with this anyone?

I should have said that this message only occurs when I try to debug my tool, using Xcode's "Build and Debug" button, or it's "Debug" button.

How can I debug then? Debugging has been killed off by this bug in Xcode!

What can I do? Any help, anything?

On 28 Mar 2006, at 21:17, Theodore H. Smith wrote:

Hi people,

I'm getting some strange error. I made a small C++ shell tool, using Xcode. It contains some calls to libxml2.

If I don't link in the library libxml2, then I can debug the shell tool, although it fails at the first call to any libxml2 functions of course.

If I DO link in the library, I get this "No launchable executable present at path?" error. I've never seen this before. Why is this happening?

I've linked to libraries before and had no problem, so I can't understand why this is happening now.

I tried executing it from the terminal, and it DOES run just fine. So it is an executable after all!

What is up?

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/jeremy.sagan% 40verizon.net

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:
http://lists.apple.com/mailman/options/xcode-users/msi_list% 40comosoft.de

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:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

• Prev by Date: Breaking into debugger with key press while running GUI app
• Next by Date: Re: std::log10() problem
• Previous by thread: Re: No launchable executable present at path?
• Next by thread: Error
• Index(es):
  • Date
  • Thread