search for: 20syntax

...uot; to #include <> or change header file inclusions to use relative paths. I > don't see any advantages of one over the other but what we have today is not > strictly correct :-) #include <> is for system headers: http://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html#Include%20Syntax While LLVM is slowly moving that direction, we are not yet considered to be required by the "system". -Chris -- http://llvm.cs.uiuc.edu/ http://www.nondot.org/~sabre/Projects/

...; or change header file inclusions to use > > relative paths. I don't see any advantages of one over the other but what > > we have today is not strictly correct :-) > > #include <> is for system headers: > http://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html#Include%20Syntax > > While LLVM is slowly moving that direction, we are not yet considered to > be required by the "system". Yes they define as "system" headers files that declare interfaces to parts of the OS (cpp info, section Header Files). Of couse what is defined as OS is not me...

LLVMers, I'm running into a fair bit of confusion as I start to *use* LLVM to build my own compiler. The issues relate to what is in a given .a or .o file, why linking takes so long, and getting LLVM header files to include correctly, and the lack of viable "install" target. I'll deal with each of these in turn: For my own project, I've added an AC_CHECK_LIB line to check