[cfe-dev] Paths to system header files

[Pedro Delgado Perez via cfe-dev]

Sorry, Jacob, no idea on how to use your solution in my code. Manuel, nothing is written in your message I think...

My code is something like this:
static cl::OptionCategory MyToolCategory("My tool options"); int main(int argc, const char **argv) {
   CommonOptionsParser [ http://clang.llvm.org/doxygen/classclang_1_1tooling_1_1CommonOptionsParser.html ] OptionsParser(argc, argv, MyToolCategory);   ClangTool [ http://clang.llvm.org/doxygen/classclang_1_1tooling_1_1ClangTool.html ] Tool(OptionsParser.getCompilations(),                  OptionsParser.getSourcePathList());   return Tool.run [ http://clang.llvm.org/doxygen/classclang_1_1tooling_1_1ClangTool.html#acec91f63b45ac7ee2d6c94cb9c10dab3 ](newFrontendActionFactory<SyntaxOnlyAction>().get()); }
What I was doing by the moment is to process argv before creating the object OptionsParser and then include internal Clang headers, but I guess I can't do that when using Json compilation database. Could you help me with that? Otherwise, is there a way to ship in the executable all the necessary headers so that the user does not require to have clang installed?

Thanks.



El día 26 feb 2016 10:37, Pedro Delgado Perez <pedro.delgadoperez at mail.uca.es> escribió:
> 
> Hello,
> 
> Perhaps this question has been asked before, but I couldn't find a proper solution for this issue. When I produce an executable and use it in another machine, sometimes Clang is not able to find system header files (for instance "limits.h") because the paths to find these headers are relative to the location of the Clang libraries.
> 
> All the same, when I'm using FIXED COMPILATION, I'm able to automatically retrieve the paths to system headers of the machine where the executable is being run. I mean, I retrieve the paths and add them after "--" to the command through the option -isystem. However, when I'm using JSON COMPILATION DATABASE, I can't do that, so in this case I don't know how to solve this issue.
> 
> What is the appropriate manner to handle this matter of the paths to system header files?
> 
> Thanks.
> 
> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20160226/d3f1b0b5/attachment.html>