Thanks. It works now. After tripple-checking I found the culprit - the
good'ol'typo classic mistake... The error message was leading me to a
different direction, so I didn't immediately found the error. Perhaps "path
not found" instead of "path not accessible" would be better? Something to
remember
> using NSTask, or something else?
Woops, missed your subject line; NSTask, got it. But yes, I would see
if you're able to read the executable as plain data, using NSData's
dataWithContentsOfFile: to make sure the path is in fact accessible.
___
Cocoa-d
The current recommendation is to store helper executables in the MacOS
directory, rather than the Resources directory of your main bundle.
That said, I'm unaware of any enforcement of this that would actually
prevent you from executing it.
How are you sure that the path is correct? Are you able to
I'm trying to run an executable from within an .app bundle's
Contents/Resources folder (the executable is a standard command line
utility) and I end up with "path not accessible" error. If I copy the
executable outside the bundle, it works. I can launch the executable from
terminal as expected. I a
