On Jun 4, 2012, at 15:32, Manuel Klimek wrote: > On Fri, Jun 1, 2012 at 1:10 PM, Erik Verbruggen <[email protected]> wrote: > > On May 24, 2012, at 19:07, Manuel Klimek wrote: > > > Author: klimek > > Date: Thu May 24 12:07:18 2012 > > New Revision: 157396 > > > > URL: http://llvm.org/viewvc/llvm-project?rev=157396&view=rev > > Log: > > Adds a tutorial for how to write clang plugins. > > Sorry for the late reply, but it would be really nice if you could add a > paragraph which mentions the libraries used for linking (for all those people > who want (have?) to use esoteric build systems)... > > Hm, since this is a dynamic library, doesn't it basically not require linking > anything in at compile time, but the right symbols to be available in the > clang executable at runtime? Or did you have something else in mind?
I link with: clang++ -headerpad_max_install_names -arch x86_64 -o qt-checker main.o -L/data/clang-llvm/llvm-3.1-install/lib -lpthread -lm -lLLVMCore -lLLVMSupport -lclangTooling -lclangAST -lclangFrontend -lclangSerialization -lclangSema -lclangAnalysis -lclangBasic -lclangEdit -lclangLex -lclangParse -Wl,-undefined,dynamic_lookup -L../checkers -lcheckers I get: dyld: lazy symbol binding failed: Symbol not found: __ZN5clang6driver6DriverC1EN4llvm9StringRefES3_S3_bRNS_17DiagnosticsEngineE Referenced from: /data/git/qtcheckers/app/qt-checker Expected in: dynamic lookup Etc. For clang plug-ins it works, but apparently not for tooling executables... -- Erik.
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
