Hi,

Another option is to just drag and drop the .m and .h icons from the main project to new project. This gives you the option of making a new copy or using a link to the originals.

I often use the link method, having a Master app that is used to develop and test the object, then when it passes all my tests, link it to the production apps.

cheers
Kevin

On Mon, Jul 6, 2009 at 4:23 PM, Alexander Bokovikov<openwo...@uralweb.ru> wrote:
Hi, All,

Maybe it's a dummy question, but I can't find a way to share some ObjC
classes with several XCode projects. I've created a set of Cocoa classes (.h and .m files) What I'd like to get is the ability to write something like
this:

#import <MyDir/MyClass.h>

I don't want to distribute these classes, as a framework, but I would like just to link them directly into every executable, which refers them. As I heard, a static library, having ObjC classes inside, may cause some problems
in linking. Therefore I yet didn't try this way.

My question is: can I copy these shared files (.h + .m) into some system
directory to make them being visible for any Cocoa project through the
import directive, like above?

If no, then what is the correct way to go besides manual inclusion of the
same files into every XCode project?

-Thanks.
_______________________________________________

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/mnemonic.fx%40gmail.com

This email sent to mnemonic...@gmail.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

Reply via email to