llvm dev - Nov 2018 - Have LLD and Clang in their correct locations, but still can't generate project files for LLVM

I think most people are using ninja to do the build.  You can still use the
Visual Studio generator for the IDE experience while doing build from
ninja.  I know there are a couple of people who build from inside of Visual
Studio, but it's a pretty small number, and I don't think they are
targeting WebAssembly.

On Tue, Nov 27, 2018 at 12:46 PM Osman Zakir via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Is there no one who has already built LLVM for targeting WebAsesembly
> with, using Visual Studio 2017 as the generator and toolchain (x64 of
> course)?
>
> My LLVM root folder is C:/llvm, and LLD and Clang are in
> llvm_root/tools/lld and llvm_root/tools/clang respectively.  If this is as
> it should be, then what's the problem? Would someone please help me
with
> this by also checking the logs I've attached to the first message in
this
> thread?  Thanks in advance.
>
> In llvm/tools/, I see there's also a folder called "msbuild"
which also
> has a .sln file called llvm.sln.  How about if I just try to build that
> (and if needed, would it be okay to just put the preprocessor definition
> LLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly in there for each
> project?)?
> ------------------------------
> *From:* llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of
Osman
> Zakir via llvm-dev <llvm-dev at lists.llvm.org>
> *Sent:* Tuesday, November 27, 2018 4:30 AM
> *To:* llvm-dev at lists.llvm.org
>
> *Subject:* Re: [llvm-dev] Have LLD and Clang in their correct locations,
> but still can't generate project files for LLVM
> Yeah, I don't think that matters.  It did set the toolset architecture
to
> x64.
>
> You know, I attached those log files for a reason.
> ------------------------------
> *From:* Zachary Turner <zturner at google.com>
> *Sent:* Tuesday, November 27, 2018 4:27 AM
> *To:* Osman Zakir
> *Cc:* llvm-dev at lists.llvm.org
> *Subject:* Re: [llvm-dev] Have LLD and Clang in their correct locations,
> but still can't generate project files for LLVM
>
> I don't know if it actually matters, but I think there should not be a
> space after -T.  Usually I would specify it like -Thost=x64.
>
> On Mon, Nov 26, 2018 at 8:53 AM Osman Zakir via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> I ran CMake on the command line with this command:
> "
> cmake .. -DCMAKE_INSTALL_PREFIX=../install_x64 -T host=x64 -G "Visual
> Studio 15 2017 Win64" -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly
> "
>
> And I have LLD and Clang where they should be.  But I still couldn't
> generate project files.  The path to the build and installation directories
> don't have spaces at all this time, either.  I'm attaching the logs
to this
> message.  Please help.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181127/daad747b/attachment-0001.html>

I am evidently one of those rare people successfully building LLVM v7
inside VS 2017 and targeting WebAssembly. Unlike Osman, I build the 32-bit
version, but I suspect I would have no significant trouble switching to
building the 64-bit version.

I use CMake-Gui vs. Osman using Cmake on the command line. This allows me
to use the mouse to select the CLANG_BUILD_TOOLS and LLD_BUILD_TOOLS
options which are also needed to build those tools along with the rest of
LLVM. I do this after the Configure step and before the Generate step.

When that is done, I double click on the generated LLVM.sln file to fire up
Visual Studio. I then right-click on BUILD_ALL to build LLVM, followed by
right-clicking on INSTALL to finish the process a few hours later.

That said, I looked at Osman's log and saw the build was struggling to
locate various include files, which seems a very basic error suggesting
something fundamentally is amiss with how the build is locating LLVM source
files. I know too little about Osman's set up and LLVM's CMake process
to
hazard a guess as to what might be causing that.

On Wed, Nov 28, 2018 at 9:52 AM Zachary Turner via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> I think most people are using ninja to do the build.  You can still use
> the Visual Studio generator for the IDE experience while doing build from
> ninja.  I know there are a couple of people who build from inside of Visual
> Studio, but it's a pretty small number, and I don't think they are
> targeting WebAssembly.
>
> On Tue, Nov 27, 2018 at 12:46 PM Osman Zakir via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Is there no one who has already built LLVM for targeting WebAsesembly
>> with, using Visual Studio 2017 as the generator and toolchain (x64 of
>> course)?
>>
>> My LLVM root folder is C:/llvm, and LLD and Clang are in
>> llvm_root/tools/lld and llvm_root/tools/clang respectively.  If this is
as
>> it should be, then what's the problem? Would someone please help me
with
>> this by also checking the logs I've attached to the first message
in this
>> thread?  Thanks in advance.
>>
>> In llvm/tools/, I see there's also a folder called
"msbuild" which also
>> has a .sln file called llvm.sln.  How about if I just try to build that
>> (and if needed, would it be okay to just put the preprocessor
definition
>> LLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly in there for each
>> project?)?
>> ------------------------------
>> *From:* llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf
of Osman
>> Zakir via llvm-dev <llvm-dev at lists.llvm.org>
>> *Sent:* Tuesday, November 27, 2018 4:30 AM
>> *To:* llvm-dev at lists.llvm.org
>>
>> *Subject:* Re: [llvm-dev] Have LLD and Clang in their correct
locations,
>> but still can't generate project files for LLVM
>> Yeah, I don't think that matters.  It did set the toolset
architecture to
>> x64.
>>
>> You know, I attached those log files for a reason.
>> ------------------------------
>> *From:* Zachary Turner <zturner at google.com>
>> *Sent:* Tuesday, November 27, 2018 4:27 AM
>> *To:* Osman Zakir
>> *Cc:* llvm-dev at lists.llvm.org
>> *Subject:* Re: [llvm-dev] Have LLD and Clang in their correct
locations,
>> but still can't generate project files for LLVM
>>
>> I don't know if it actually matters, but I think there should not
be a
>> space after -T.  Usually I would specify it like -Thost=x64.
>>
>> On Mon, Nov 26, 2018 at 8:53 AM Osman Zakir via llvm-dev <
>> llvm-dev at lists.llvm.org> wrote:
>>
>> I ran CMake on the command line with this command:
>> "
>> cmake .. -DCMAKE_INSTALL_PREFIX=../install_x64 -T host=x64 -G
"Visual
>> Studio 15 2017 Win64"
-DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly
>> "
>>
>> And I have LLD and Clang where they should be.  But I still
couldn't
>> generate project files.  The path to the build and installation
directories
>> don't have spaces at all this time, either.  I'm attaching the
logs to this
>> message.  Please help.
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181128/a25be1a4/attachment.html>

Do I have to use a flag to tell it where the LLVM include files are?  And would
it be easier to do that in the CMake GUI?  Please tell me how you had it find
the include files if that may help me.
________________________________
From: Jonathan Goodwin <jondgoodwin at gmail.com>
Sent: Wednesday, November 28, 2018 6:24 AM
To: zturner at google.com
Cc: Osman Zakir; llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Have LLD and Clang in their correct locations, but still
can't generate project files for LLVM

I am evidently one of those rare people successfully building LLVM v7 inside VS
2017 and targeting WebAssembly. Unlike Osman, I build the 32-bit version, but I
suspect I would have no significant trouble switching to building the 64-bit
version.

I use CMake-Gui vs. Osman using Cmake on the command line. This allows me to use
the mouse to select the CLANG_BUILD_TOOLS and LLD_BUILD_TOOLS options which are
also needed to build those tools along with the rest of LLVM. I do this after
the Configure step and before the Generate step.

When that is done, I double click on the generated LLVM.sln file to fire up
Visual Studio. I then right-click on BUILD_ALL to build LLVM, followed by
right-clicking on INSTALL to finish the process a few hours later.

That said, I looked at Osman's log and saw the build was struggling to
locate various include files, which seems a very basic error suggesting
something fundamentally is amiss with how the build is locating LLVM source
files. I know too little about Osman's set up and LLVM's CMake process
to hazard a guess as to what might be causing that.

On Wed, Nov 28, 2018 at 9:52 AM Zachary Turner via llvm-dev <llvm-dev at
lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
I think most people are using ninja to do the build.  You can still use the
Visual Studio generator for the IDE experience while doing build from ninja.  I
know there are a couple of people who build from inside of Visual Studio, but
it's a pretty small number, and I don't think they are targeting
WebAssembly.

On Tue, Nov 27, 2018 at 12:46 PM Osman Zakir via llvm-dev <llvm-dev at
lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
Is there no one who has already built LLVM for targeting WebAsesembly with,
using Visual Studio 2017 as the generator and toolchain (x64 of course)?

My LLVM root folder is C:/llvm, and LLD and Clang are in llvm_root/tools/lld and
llvm_root/tools/clang respectively.  If this is as it should be, then what's
the problem? Would someone please help me with this by also checking the logs
I've attached to the first message in this thread?  Thanks in advance.

In llvm/tools/, I see there's also a folder called "msbuild" which
also has a .sln file called llvm.sln.  How about if I just try to build that
(and if needed, would it be okay to just put the preprocessor definition
LLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly in there for each project?)?
________________________________
From: llvm-dev <llvm-dev-bounces at lists.llvm.org<mailto:llvm-dev-bounces
at lists.llvm.org>> on behalf of Osman Zakir via llvm-dev <llvm-dev at
lists.llvm.org<mailto:llvm-dev at lists.llvm.org>>
Sent: Tuesday, November 27, 2018 4:30 AM
To: llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>

Subject: Re: [llvm-dev] Have LLD and Clang in their correct locations, but still
can't generate project files for LLVM
Yeah, I don't think that matters.  It did set the toolset architecture to
x64.

You know, I attached those log files for a reason.
________________________________
From: Zachary Turner <zturner at google.com<mailto:zturner at
google.com>>
Sent: Tuesday, November 27, 2018 4:27 AM
To: Osman Zakir
Cc: llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
Subject: Re: [llvm-dev] Have LLD and Clang in their correct locations, but still
can't generate project files for LLVM

I don't know if it actually matters, but I think there should not be a space
after -T.  Usually I would specify it like -Thost=x64.

On Mon, Nov 26, 2018 at 8:53 AM Osman Zakir via llvm-dev <llvm-dev at
lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
I ran CMake on the command line with this command:
"
cmake .. -DCMAKE_INSTALL_PREFIX=../install_x64 -T host=x64 -G "Visual
Studio 15 2017 Win64" -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly
"

And I have LLD and Clang where they should be.  But I still couldn't
generate project files.  The path to the build and installation directories
don't have spaces at all this time, either.  I'm attaching the logs to
this message.  Please help.
_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181128/f686636f/attachment.html>

@Jonathan Goodwin: Do I have to use a flag to tell it where the LLVM include
files are?  And would it be easier to do that in the CMake GUI?  Please tell me
how you had it find the include files if that may help me.
________________________________
From: Jonathan Goodwin <jondgoodwin at gmail.com>
Sent: Wednesday, November 28, 2018 6:24 AM
To: zturner at google.com
Cc: Osman Zakir; llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Have LLD and Clang in their correct locations, but still
can't generate project files for LLVM

I am evidently one of those rare people successfully building LLVM v7 inside VS
2017 and targeting WebAssembly. Unlike Osman, I build the 32-bit version, but I
suspect I would have no significant trouble switching to building the 64-bit
version.

I use CMake-Gui vs. Osman using Cmake on the command line. This allows me to use
the mouse to select the CLANG_BUILD_TOOLS and LLD_BUILD_TOOLS options which are
also needed to build those tools along with the rest of LLVM. I do this after
the Configure step and before the Generate step.

When that is done, I double click on the generated LLVM.sln file to fire up
Visual Studio. I then right-click on BUILD_ALL to build LLVM, followed by
right-clicking on INSTALL to finish the process a few hours later.

That said, I looked at Osman's log and saw the build was struggling to
locate various include files, which seems a very basic error suggesting
something fundamentally is amiss with how the build is locating LLVM source
files. I know too little about Osman's set up and LLVM's CMake process
to hazard a guess as to what might be causing that.

On Wed, Nov 28, 2018 at 9:52 AM Zachary Turner via llvm-dev <llvm-dev at
lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
I think most people are using ninja to do the build.  You can still use the
Visual Studio generator for the IDE experience while doing build from ninja.  I
know there are a couple of people who build from inside of Visual Studio, but
it's a pretty small number, and I don't think they are targeting
WebAssembly.

On Tue, Nov 27, 2018 at 12:46 PM Osman Zakir via llvm-dev <llvm-dev at
lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
Is there no one who has already built LLVM for targeting WebAsesembly with,
using Visual Studio 2017 as the generator and toolchain (x64 of course)?

My LLVM root folder is C:/llvm, and LLD and Clang are in llvm_root/tools/lld and
llvm_root/tools/clang respectively.  If this is as it should be, then what's
the problem? Would someone please help me with this by also checking the logs
I've attached to the first message in this thread?  Thanks in advance.

In llvm/tools/, I see there's also a folder called "msbuild" which
also has a .sln file called llvm.sln.  How about if I just try to build that
(and if needed, would it be okay to just put the preprocessor definition
LLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly in there for each project?)?
________________________________
From: llvm-dev <llvm-dev-bounces at lists.llvm.org<mailto:llvm-dev-bounces
at lists.llvm.org>> on behalf of Osman Zakir via llvm-dev <llvm-dev at
lists.llvm.org<mailto:llvm-dev at lists.llvm.org>>
Sent: Tuesday, November 27, 2018 4:30 AM
To: llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>

Subject: Re: [llvm-dev] Have LLD and Clang in their correct locations, but still
can't generate project files for LLVM
Yeah, I don't think that matters.  It did set the toolset architecture to
x64.

You know, I attached those log files for a reason.
________________________________
From: Zachary Turner <zturner at google.com<mailto:zturner at
google.com>>
Sent: Tuesday, November 27, 2018 4:27 AM
To: Osman Zakir
Cc: llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
Subject: Re: [llvm-dev] Have LLD and Clang in their correct locations, but still
can't generate project files for LLVM

I don't know if it actually matters, but I think there should not be a space
after -T.  Usually I would specify it like -Thost=x64.

On Mon, Nov 26, 2018 at 8:53 AM Osman Zakir via llvm-dev <llvm-dev at
lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
I ran CMake on the command line with this command:
"
cmake .. -DCMAKE_INSTALL_PREFIX=../install_x64 -T host=x64 -G "Visual
Studio 15 2017 Win64" -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly
"

And I have LLD and Clang where they should be.  But I still couldn't
generate project files.  The path to the build and installation directories
don't have spaces at all this time, either.  I'm attaching the logs to
this message.  Please help.
_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181128/0b1b84a1/attachment.html>