However, XCode immediately tells me it can't find the header files.
If you are CLI proof, add the --verbose flag to gcc to learn what gcc/
g++ searches and about the differences between:
#include "eo"
#include "eo.h"
#include <eo> and
#include <eo.h>
(i.e. error: eo: No such file or directory.) The example program
compiles fine with the makefile that came with the library.
The Xcode-type way is to go to preferences and to add /usr/local/
include to the known source trees, IIRC. As you can edit about any
flag Xcode passes to the undelying CLI tools, you can add a -I
directive as well. See all the settings when you double click your
target and/or your project.
... I have to do anything special to get the libraries to link as
well?
Add the library to the project like you'd add a source file or a
framework. Xcode will pick it up and pass the appropriate flags to
the linker.
_______________________________________________
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
