>
>
> Sadly that's part of the problem. Very few people actually use the Visual
> Studio generator for building, so a lot of times when we get people with
> issues, nobody knows how to help (or the person that does know doesn't see
> the thread). So they get a response like "hmm, not many people
On Tue, Oct 9, 2018 at 12:49 AM Csaba Raduly wrote:
> On Sun, Oct 7, 2018 at 10:51 PM Zachary Turner via cfe-dev
> wrote:
>
> > 1) Run CMake twice, generating to separate output directories. Once
> using -G "Visual Studio 15 2017" and once using -G Ninja, each to different
> directories.
> >
>
On Sun, Oct 7, 2018 at 10:51 PM Zachary Turner via cfe-dev
wrote:
> 1) Run CMake twice, generating to separate output directories. Once using -G
> "Visual Studio 15 2017" and once using -G Ninja, each to different
> directories.
>
> 2) Open the VS one. You have full IDE support.
>
> 3) Instea
On Mon, Oct 8, 2018 at 12:29 PM wrote:
> I build with the VS project. I find it more convenient to do that than
> have VS and a cmd window open to run ninja. Especially when I’ve got more
> than 1 copy of VS open looking at different release trains. I wouldn’t mind
> using ninja to build, but onl
ect: Re: [lldb-dev] [cfe-dev] Should we stop supporting building with
Visual Studio?
On Mon, Oct 8, 2018 at 11:54 AM Stephen Kelly via cfe-dev
mailto:cfe-...@lists.llvm.org> > wrote:
> 3) Even if you do pass -Thost=x64 to CMake, it will apparently still
> fail sometimes. S
> On Oct 8, 2018, at 8:09 AM, Zachary Turner via lldb-dev
> wrote:
>
> I haven't heard of anyone using the Xcode generated project. In fact, LLDB
> maintains its own hand-created Xcode project precisely because the CMake one
> is considered "unusable". That said, I don't personally use Xco
On Mon, Oct 8, 2018 at 11:54 AM Stephen Kelly via cfe-dev <
cfe-...@lists.llvm.org> wrote:
>
> > 3) Even if you do pass -Thost=x64 to CMake, it will apparently still
> > fail sometimes. See this thread for details:
> > http://lists.llvm.org/pipermail/cfe-dev/2018-October/059609.html. It
> > seem
On Mon, Oct 8, 2018 at 7:42 AM Greg Bedwell wrote:
> Thanks for raising this.
>
> This is a topic I've been interested in for a while too, as I've had to do
> a few of those lite.site.cfg fix-ups that you mention (in fact I have one
> sitting unreviewed at https://reviews.llvm.org/D40522 although
> (in fact I have one sitting unreviewed at https://reviews.llvm.org/D40522
> although
>> I've not pinged it in a long time so I'll need to double check that it's
>> still an issue).
>>
>
Actually, ignore that. It's a slightly different issue that I had
mismembered as being related to https://re
Yes i listed 5 steps, but 2 of them (#2 and #5) are exactly what you
already do.
#1 I only actually do every couple of weeks, which is an improvement over
building inside VS. when you build inside vs you have to close and reopen
the solution every time you sync, which is really slow. You don’t act
Thanks for raising this.
This is a topic I've been interested in for a while too, as I've had to do
a few of those lite.site.cfg fix-ups that you mention (in fact I have one
sitting unreviewed at https://reviews.llvm.org/D40522 although I've not
pinged it in a long time so I'll need to double chec
On Sun, Oct 7, 2018 at 4:51 PM Zachary Turner via cfe-dev
wrote:
>
> This has been on my mind for quite some time, but recently it's been popping
> up more and more seeing some of the issues people have run into.
>
> Before people get the wrong idea, let me make one thing clear. **I am not
> pr
What would the variable do? Ninja and VS are generators, the only way to
specify them is with the -G option to cmake. If you use the VS generator,
there's no way I'm aware of to make it use ninja instead of MSBuild when
you hit Ctrl+Shift+B.
That said, type ninja in a command prompt is not a ter
13 matches
Mail list logo
