I'm trying to package my header-only C++ template library as a
framework for maximum compatibility and ease of deployment.
Alternatively any method that is fairly easy to implement for library
users i.e. minimizes the number of fiddly build settings that needed to
be set.
All public headers are in a folder. All internal etc. headers are in a
subfolder. The public headers should be included like this
#include <macstl/vec.h>
This is compatible with Apple's framework inclusion scheme, and will
work if people install the library headers in /usr/includes like most
Unices do.
But here's the wrinkle -- as a header-only library, there is no dylib
created. When a client then adds a reference to my framework, it
compiles OK but fails at the link stage because of the absence of a
dylib.
So...
1. Can I put a static lib stub or some other trickery in place of the
dylib and the linker work?
2. In the get info for a file ref, what is the difference between the
file type "wrapper.framework" and "wrapper.framework.static"?
3. Any other file type e.g. folder or wrapper will do this? i.e. a sort
of "this is a system header directory" which causes a folder reference
to be considered for the -I system includes compiler option??
4. Any other clues and advice to achieve what I want?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
