Re: Xcode doesn't set executable bit for built executable
Re: Xcode doesn't set executable bit for built executable
- Subject: Re: Xcode doesn't set executable bit for built executable
- From: "Eric Wang" <email@hidden>
- Date: Thu, 16 Mar 2006 02:42:59 -0500
You're right Fritz. Not having the execute permission set for my
plug-in bundle "executable" doesn't affect my host application's
ability to run and load the code contained in the bundle. However, I'm
still confused as to why out of several plug-in projects, this is the
only one that produces an output file that doesn't have the execute
bit set. I'm concerned that I might've corrupted the Xcode project
file and that is why it's producing results different from all my
other projects.
The INSTALL_MODE_FLAG isn't set in any of my projects so I don't think
that is what's causing it. The build settings for all my projects are
basically the same except for things that are dependent on the name of
the project.
Hopefully this is just something harmless and not indicative of
something that will force me to create a new project and re-import all
my files down the road.
Thanks for your help,
Eric Wang
On 3/15/06, Fritz Anderson <email@hidden> wrote:
> On 15 Mar 2006, at 12:47 AM, Eric Wang wrote:
>
> > My application makes use of multiple Cocoa bundles as plug-ins. I have
> > one bundle project whose corresponding executable is always built with
> > rw-r--r-- (chmod 644) permissions. All the other bundle projects are
> > correctly built with rwxr-x-r-x (chmod 755) permissions. They show up
> > as Unix Executable Files when I get info on them in the Finder. All
> > the projects have the same build settings except for things like the
> > product name, etc.
> >
> > I've tried cleaning the problematic project, deleting the Xcode
> > caches, logging out and logging back in with no effect. I didn't
> > really see anything about this in the archives. Does anyone know why
> > this is happening? Is my project file corrupt?
>
> I must be very confused about UNIX file permissions, or the
> architecture of plugins.
>
> I had always assumed that the x bit in the permissions meant that the
> file in question was to be treated as a primary, or root, executable;
> for instance, something that it would make sense to execute from the
> command line.
>
> By that assumption, I wouldn't know why one would want a dynamically-
> loaded library to be marked as executable -- there's no main entry
> point to execute, nor anything sensible for the plugin to do without
> a host application. The library may be referred to as "an
> executable," but that's a different sense of the word, meant to
> contrast the file with files that contain no code.
>
> That said, you might want to look up INSTALL_MODE_FLAG via the Help-
> >Show Build Settings Notes menu item.
>
> -- F
> --
> Fritz Anderson -- http://www.manoverboard.org/
> Consulting Programmer -- http://resume.manoverboard.org/
> Step into Xcode, Now Available -- http://six.manoverboard.org/
>
>
>
_______________________________________________
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