From: Joe on 6 Jan 2010 23:32 I've got a small application that I would like to release as beta and it's coming nicely, except I've never packaged an XCode app before. My application is really two projects, one creates a shared library, and the other is the application. It also requires a project directory with some example files that users can learn with. Can anyone point me to anything that would help me understand how XCode projects should be properly distributed? Any help much appreciated.
From: Tom Harrington on 7 Jan 2010 13:32 In article <2010010622320916807-invalid(a)emailaccount>, Joe <invalid(a)email.account> wrote: > I've got a small application that I would like to release as beta and > it's coming nicely, except I've never packaged an XCode app before. > > My application is really two projects, one creates a shared library, > and the other is the application. It also requires a project directory > with some example files that users can learn with. > > Can anyone point me to anything that would help me understand how XCode > projects should be properly distributed? > > Any help much appreciated. Assuming the app uses the shared lib, you should put the library inside the app's bundle, because users shouldn't have to deal with it. The application and the folder of sample files can go on the same disk image. Alternately, put the sample files within the app bundle and, on first run, have the app offer to copy them someplace where the user can find them. -- Tom "Tom" Harrington Independent Mac OS X developer since 2002 http://www.atomicbird.com/
|
Pages: 1 Prev: Can't Create a NOTE In Apple Mail? Where are Notes Stored? Next: mail "boxes" |