[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [swarm-hackers] header directory structure

From: Bill Northcott
Subject: Re: [swarm-hackers] header directory structure
Date: Wed, 9 Jul 2008 10:01:26 +1000

On 09/07/2008, at 4:34 AM, Scott Christley wrote:
This sort of layout is easy to build, compatible with makefile build methods and usable in Xcode drag and drop style. The existing configure machinery will do the right stuff in the Makefiles.

Ok, I see how that works now. Though I guess you still need a -I flag to get the include path, you cannot just add the framework to Xcode and it works automatically?

That should just work in Xcode. In Cocoa code, you would use #import <Swarm/defobj.h> This looks in Swarm.framework/Headers where it finds defobj.h via the symlinks.

Within Swarm and Swarm model code we have #include <defobj/defobj.h> which is found through the '-I /Library/Swarm.framework/Versions/ Current/include' option setup by configure.

Everyone is happy, and the sources stay the same.

        Headers -> Versions/Current/Headers
        Resources -> Versions/Current/Resources
        Swarm -> Versions/Current/Swarm
                Current -> A

IMO That is just a simpler version of my scheme, which I only copied from others. No originality is claimed.

Thought: Do we have any architecture dependent headers?? Yes right now. Will we have them in the new build Scott is doing? If so, how do we arrange them?

Currently I don't think these are needed on Mac, I let the system libraries handle the different architectures.

It would be very pleasing if that were right. I can see that model code does not need to use arch dependent headers, but I not quite convinced about the Swarm library build.

Any thoughts about the symlinks under /usr/local. Several packages including Tcl/Tk use them on MacOS.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]