Displaying 3 results from an estimated 3 matches for "addpath".
Did you mean:
add_path
2013 Feb 19
0
[LLVMdev] LLVM/Clang 3.1: Add a new include path in a clang C++ based parser
Hi,
I'm having troubles to add a custom include path to a clang based C++
parser.
I'd like to properly support this opencv code under Linux:
...
#include "cv.h"
#include "highgui.h"
...
This is what I'm using:
TheCompInst->getHeaderSearchOpts().AddPath(StringRef("/usr/include/opencv"),clang::frontend::Quoted
,false, true, false, false, false);
Note: I have tried also with clang::frontend::Angled without success.
Can you see the problem? Could you please say me where can I find some
Clang 3.1 based related example?
Many thanks in adv...
2013 Feb 19
0
[LLVMdev] LLVM/Clang 3.1: Add a new include path in a clang C++ based parser
Hi,
I'm having troubles to add a custom include path to a clang based C++
parser.
I'd like to properly support this opencv code under Linux:
...
#include "cv.h"
#include "highgui.h"
...
This is what I'm using:
TheCompInst->getHeaderSearchOpts().AddPath(StringRef("/usr/include/opencv"),clang::frontend::Quoted
,false, true, false, false, false);
Note: I have tried also with clang::frontend::Angled without success.
Can you see the problem? Could you please say me where can I find some
Clang 3.1 based related example?
Many thanks in adv...
2006 Mar 05
1
[LLVMdev] Possible solution to a llvm-ld bug
...ng a error if I used -L switch when linking using the following command line:
llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib -lcrtend
I believe I've tracked down the problem; in the "main" of tools/llvm-ld.cpp
the call to ParseCommandLineOptions is after the TheLinker.addPaths(LibPaths)
statement so the -L command line parameter is ignored.
My fix was to move the ParseCommandLineOptions to the beginning of the main routine.
Cheers,
Wink Saville