All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sibi Siddharthan <sibisiddharthan.github@gmail.com>
To: Matt Rogers <mattr94@gmail.com>
Cc: Philip Oakley <philipoakley@iee.email>,
	Git List <git@vger.kernel.org>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Danh Doan <congdanhqx@gmail.com>
Subject: Re: [RFH] CMake: detect if being run via Visual Studio, independent of build generator?
Date: Sun, 30 May 2021 19:59:26 +0530	[thread overview]
Message-ID: <CAKiG+9WwRHz-5JDPe6KL763kVfRP7vX5HgtDMiX-S1Je5+oWfg@mail.gmail.com> (raw)
In-Reply-To: <CAOjrSZuzgBs8camWdUjEU+JOjRYwv3MVjRgnyW50pchq6rpYsQ@mail.gmail.com>

On Sun, May 30, 2021 at 6:52 PM Matt Rogers <mattr94@gmail.com> wrote:

>
> I think the best middle of the line solution would be to just provide a manual
> knob for turning vcpkg support on/off here and offer configurations in
> CMakePresets.json for both situations.  The only downside here is that I believe
> a lot of IDE's are aggressive about running the cmake configuration step and may
> try to install vcpkg even if it is unnecessary.  But automatic
> generation can generally
> be turned off by users I guess.

I agree. I would suggest vcpkg should be used by default for Windows platforms.
This way IDE's won't complain and command line users can straight up
disable this behaviour.

Thank You,
Sibi Siddharthan

  reply	other threads:[~2021-05-30 14:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29 15:00 [RFH] CMake: detect if being run via Visual Studio, independent of build generator? Philip Oakley
2021-05-29 15:49 ` Matt Rogers
2021-05-29 16:25   ` Philip Oakley
2021-05-29 18:33     ` Sibi Siddharthan
2021-05-29 20:31       ` Philip Oakley
2021-05-29 22:14         ` Sibi Siddharthan
2021-05-30  0:14           ` Matt Rogers
2021-05-30 10:52             ` Philip Oakley
2021-05-30 13:22               ` Matt Rogers
2021-05-30 14:29                 ` Sibi Siddharthan [this message]
2021-05-30 15:24                   ` Philip Oakley
2021-05-30 22:26                     ` Philip Oakley
2021-05-31  0:01                       ` Matt Rogers
2021-05-31 17:12                         ` Philip Oakley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKiG+9WwRHz-5JDPe6KL763kVfRP7vX5HgtDMiX-S1Je5+oWfg@mail.gmail.com \
    --to=sibisiddharthan.github@gmail.com \
    --cc=congdanhqx@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=mattr94@gmail.com \
    --cc=philipoakley@iee.email \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.