(original) (raw)

I mentioned the command I used in of my messages in this thread. And of course I used clang++.exe to do it, not "LLVM". I just meant I was using LLVM toolchain on the Developer Command Prompt for VS 2017\. Anyway, I'm trying again to build LLVM now. I do have the MSVC compiler toolchain, but I want to try using the LLVM toolchain in Visual Studio since it's possible to do so.

From: David Greene
Sent: Thursday, December 13, 2018 12:18 AM
To: Osman Zakir
Cc: llvm-dev@lists.llvm.org
Subject: Re: \[llvm-dev\] Using LLD to link against third-party libraries? How?
Osman Zakir writes:

\> LLVM on a Developer Command Prompt.

I don't know what you mean by that. "LLVM" isn't a command. Can you
post the exact command you use to link?

\> The ones I want to fix first are the ones from Boost and Jinja2Cpp. I
\> saw some from those as well.

I'm not at all familiar with Jinja2Cpp. Is it possible it needs some
explicit template instantiations?

\> If there any standard library ones missing, could it be because I
\> couldn't get it to build libcxx? I did try to include that, but it
\> seems to be missing. What should I do?

Are you saying you tried to build libc++ and couldn't? I don't know
what C++ standard library clang uses by default on Windows. If you
don't have a C++ standard library nothing will work.

I would concentrate on the standard library symbols first, because the
way that works is well-understood by everyone here. Once you get that
working you may find a lot of the other stuff goes away.

\-David