Thanks. Now I have another build problem. If I move my command-line tool (actually, it's a cocoa app bundle without UI) under Resources, then the ant build process will move this file
MyWOApp.woa/Contents/Resources/MyTools.app/Contents/Resources/Info.plist to MyWOApp.woa/Contents/Resources/Info.plist which leaves both my wo/cocoa apps in corrupt Info.plist state. I look the build.xml without finding anything related to the Info.plist. Why is that happen? Regards, yllan On Mon, Oct 17, 2011 at 3:54 PM, Johann Werner <[email protected]> wrote: > Hi yllan, > > I would put that into the 'Resources' directory and use > > WOResourceManager.pathURLForResourceNamed( > command-line-tool-name, // name of your tool > null, // null if you put this into your app project > null); // null as you are not interested in localized resources > > jw > > > Am 17.10.2011 um 09:31 schrieb Yung-Luen Lan: > >> Hi, >> >> I have some external command-line tools written by Objective-C that >> needs to be invoked in my wo app. >> >> Of course I could put them in somewhere like /usr/local/bin, etc. >> >> But I want to embed these command-line tools inside my wo app bundle >> so that people don't forget to copy the command-line tools when >> install the wo app. However, getting path of NSBundle is deprecated >> API. Which directory should I put these tools in and how do I get the >> path when I want to call them? >> >> The app is a woa bundle so don't have to take jar into account. >> >> Any comment? >> >> Regards, >> yllan > > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
