Thanks for the link. Now the question becomes, if we move helper tools into a new Contents/Helpers folder are they covered by codesign? Would the problem mentioned in that post persist if we used Contents/MacOS/Tools instead? Sub paths must be supported since it's part of the inspector window. Time for some testing...
Kevin On Wed, May 20, 2009 at 1:21 PM, Jerry Krinock <je...@ieee.org> wrote: > > On 2009 May 19, at 18:21, Kevin LaCoste wrote: > > I found some sample code that includes a helper tool and yes, it's in the >> "Contents/MacOS" folder. >> > > Yes, but there are issues with this. Read: > > http://www.cocoabuilder.com/archive/message/cocoa/2009/3/26/233141 > > My privileged helper tool is in Contents/MacOS, because I didn't want to > hack BetterAuthorizationSample. But I put my other helpers in > Contents/Helpers. > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/cocoa-dev/klacoste%40zenvilla.com > > This email sent to klaco...@zenvilla.com > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
