As for the syntax of your #includes, you have two choices. Generally,
OS X system frameworks are included as:
#include <Cocoa/Cocoa.h>#include <OpenAL/al.h>
But portable libraries may recommend doing flat namespaces because not
everybody uses the same directory name. For example, the OpenAL spec
doesn't define where headers are located. Linux puts them in
<AL/al.h>, OS X does <OpenAL/al.h>, and Windows doesn't put them in
any directory so it is <al.h>. In theory, somebody else could screw
this up even more and put it in <AL1.1/al.h>. Thus the 'portable'
CMake is really clever about the two cases, so if you have the usage
first case, you want to do:
In the second case you want to do:
CMake will set the include paths correctly depending on which style you
This is an edited version of helpful posts from Mike Jackson and Eric
Wing. -Drew Wagner
This page was initially populated by conversion from its original location in another wiki.