Uninstall can usually be done by removing /Library/Developer but sadly this still leaves header files and such that were added to /System/Library/Frameworks. So if you don't have gl.h in /System/Library/Frameworks it's because you never installed CLT. Installing CLT will also populate things like gl.h from OpenGL framework. macOS comes with Framework runtimes installed but not headers (analogous to -dev packages in linux land). Without it is possible but you need to be a build guru or a masochist.īe aware CLT has some subtle artifacts.

But things like building your own free software, homebrew, macports, all just work easier with CLT. If you only intend to use Xcode IDE-driven development, then there is no need for CLT. This is analogous to Xcode's typical /Applications/Xcode.app location.ĬLT is only required for unix-style development. The actual 'application' home of CLT is actually tucked away in /Library/Developer. CLT is the 'unix' way to build stuff - that is tools, SDK, etc, is all placed in locations found in /usr or /System/Library. What The Fun is going on with Apple toolchains?Īpple tools coming from Apple's developer site come in 2 flavours Xcode and Command Line Tools (CLT). The filesystem layout does not include OpenGL as a parent to file.h just in case you go around snooping. Using frameworks, the include directive always is prefixed with framework's name, in this case OpenGL. This is like the -l option for libraries but for apple frameworks only #include This is like -L option for libraries but for apple frameworks only -f option Use the -v option for gcc/clang to show sub-process launch args and include/framework search paths -F option Use the -H option for gcc/clang and it will show you pathnames of resolved header files -v option Just to add a few tidbits that might help in issues such as these: -H option

Mac os opengl support