visual studio - Clang+LLVM static library linking error on Windows - Why would the symbols be different? -


after compiling clang , llvm following instruction on llvm website try linking built static libs in test app. code built v110 of vs toolset. im getting linker errors of type "error lnk2001" , "error lnk2019".

the app appears put libs in bucket symbol resolution. verbose linker output can see being dismissed:

1> unused libraries: ... 1> c:\sdk\llvm\debug\lib\clangtooling.lib ...

digging little deeper have found symbols in error message , ones in libs not quite same.

-here example-

linker error =>

*unresolved external symbol "public: int __cdecl clang::tooling::clangtool::run(class clang::tooling::toolaction )" (?run@clangtool@tooling@clang@@qeaahpeavtoolaction@23@@z) referenced in function main

...giving "?run@clangtool@tooling@clang@@qeaahpeavtoolaction@23@@z" symbol name.

now using "dumpbin /symbols" on built version of clangtooling.lib =>

*fda 00000000 undef notype () external | ?run@clangtool@tooling@clang@@qaehpavtoolaction@23@@z (public: int __thiscall clang::tooling::clangtool::run(class clang::tooling::toolaction ))

... can see the symbol im looking called "?run@clangtool@tooling@clang@@qaehpavtoolaction@23@@z"

there subtle difference near beginning of address. here again side side comparison.

?run@clangtool@tooling@clang@@qeaahpeavtoolaction@23@@z << error message

?run@clangtool@tooling@clang@@qaehpavtoolaction@23@@z << dumpbin output

why these not match?

thanks

so turns out llvm/clang libraries had built 32 bit while test project building 64 bit. have successful built test project using 32 bit binaries. notes on answer unresolved externals in c++: visual c++ mangles method signature differently mangled method in dll describe issue in more detail.

*note else looking linking llvm libs. cmake documentation llvm/clang (found here http://llvm.org/docs/cmake.html) makes sound defaults 64 bit on 64 bit system. on windows7 64bit/visualstudio11 (at least on machine) isnt case. haven't yet found option support 64 bit compilation cmake menu. seems option embed 32 bit apps.


-

Comments

Post a Comment

Popular posts from this blog

how to proxy from https to http with lighttpd -

i have internal site (192.168.2.1) accessible http on different server run public web-server using lighttpd. can make internal site accessible outside work follows $http["host"] == "internal.example.com" { ... proxy.server = ( "" => ( "internal" => ( "host" => "192.168.2.1", "port" => 8000 ) ) } this works, use https outside world. question is, how can proxy going https http ? i've tried this: $server["socket"] == ":443" { $http["host"] == "internal.example.com" { ... proxy.server = ( "" => ( "internal" => ( "host" => "http://192.168.2.1", "port" => 8000 ) ) } } but doesn't seem wor...
Read more

android - Automated my builds -

i have multiple app , android project want automated in build , release sequence. have ant script build , create apk of app. want have 1 script or ant file start build sequence app. maybe don't konw search, can't find easy documentation on ant. the point of use jenkins ant (or maven, i'm not sure of difference between them now) automated build sequence when people commit on project. any int appreciated maven dependencies (over ant) don't need pass around jars. recommend maven on ant day. syntax , overall process easier understand, @ end of both build tools. if able to, more recommend upgrading gradle. easy create different build types , create them ./gradlew assemble here project jake wharton can see power of gradle. there release , debug build, can make lot more if like. https://github.com/jakewharton/u2020 here android docs gradle http://tools.android.com/tech-docs/new-build-system/user-guide . if can't find looking here, check out main grad...
Read more

python - Flask migration error -

i've got application build on flask , wanted create new migration today. when run $python manage.py db upgrade i got message raise util.commanderror('only single head supported. ' alembic.util.commanderror: single head supported. script directory has multiple heads (due branching), must resolved manually editing revision files form linear sequence. run alembic branches see divergence(s). so run command $alembic branches no config file 'alembic.ini' found, or file has no '[alembic]' section any clue on about? the error messages coming alembic, use command form alembic <command> , integrating flask coming flask-migrate, need use form python manage.py db branches . to resolve multiple branches, make 1 of branches point down other branch upgrade graph straight line. see alembic's docs on branches: http://alembic.readthedocs.org/en/latest/branches.html
Read more