[llvm-dev] Errors in configuration for LLVM with CMake GUI

[Jonathan Goodwin via llvm-dev]

Paul:

Thanks for the background wrt svn and git version info and the advice to
ensure the tool's executable is in the PATH. Based on the earlier remark
that LLVM is moving completely off SVN support soon, I think it still makes
sense to retry with Git-based source. Hopefully, CMake will have less
trouble finding git to obtain its version info.

>From my research, CMake supports these as equivalent:  cmake -G "Visual
Studio 14" -Thost=x64 and cmake -G "Visual Studio 14 Win64". Evidently
specifying both is also valid.

It's good to know that  -DLLVM_ENABLE_PROJECTS="llvm;clang;lld" works. I
use the CMake-GUI, and click on the CLANG_BUILD_TOOLS and LLD_BUILD_TOOLS,
which is where my advice come from. I gather they are two different ways to
accomplish the same thing.

On Fri, Nov 30, 2018 at 8:38 AM <paul.robinson at sony.com> wrote:

> With regard to the executable path for SVN or Nuget (or anything else), I
> cannot think of why you need to specify it for CMake to build LLVM.
>
>
>
> CMake uses the version control system (SVN or git) to derive part of the
> version string for the build.  Whichever one you use, the location of the
> tool should be on the PATH so that simple "svn status" or "git status"
> commands will work.
>
>
>
> FTR I'm using Visual Studio 2015, with the git "mono repo" and this is my
> CMake invocation:
>
>
>
> cmake -G "Visual Studio 14 Win64" -Thost=x64 -DLLVM_ENABLE_ASSERTIONS=ON ^
>
>   -DLLVM_ENABLE_PROJECTS="llvm;clang;lld" path\to\llvm
>
>
>
> As previously noted, if you are following the SVN instructions, and put
> your clang and lld checkouts under llvm\tools, then you should omit the
> LLVM_ENABLE_PROJECTS definition.
>
> --paulr
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181130/89d3808b/attachment.html>