From: Matt Rogers <mattr94@gmail.com>
To: Sibi Siddharthan <sibisiddharthan.github@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: Sat, 29 May 2021 20:14:28 -0400 [thread overview]
Message-ID: <CAOjrSZtRH-sqh8RJm3W00dUWTbT-xcpzDWCQFt=3CNaVnOyVWQ@mail.gmail.com> (raw)
In-Reply-To: <CAKiG+9UeT70S3_jNXUbx2KCM6UDUxPKMizFX_fUiioDo-zmp+Q@mail.gmail.com>
(resending because client reconfigured to not use plaintext)
Reading through the documentation, Visual Studio seems to support
CmakePresets.json [1] for handling configuration of cmake options. It
might be worth it to keep the defaults as is. But provide a variable
for forcing vcpkg and a CMakePresets.json for Visual Studio
(and other such tools) to use.
This is nice since Visual Studio users wouldn't need to rely on the
slower Visual Studio * generators to run their builds, while leaving
non Visual Studio users still able to easily run builds. So maybe there's
a way for everyone to be happy?
1: https://devblogs.microsoft.com/cppblog/cmake-presets-integration-in-visual-studio-and-visual-studio-code/
--
Matthew Rogers
next prev parent reply other threads:[~2021-05-30 0:14 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 [this message]
2021-05-30 10:52 ` Philip Oakley
2021-05-30 13:22 ` Matt Rogers
2021-05-30 14:29 ` Sibi Siddharthan
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='CAOjrSZtRH-sqh8RJm3W00dUWTbT-xcpzDWCQFt=3CNaVnOyVWQ@mail.gmail.com' \
--to=mattr94@gmail.com \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=philipoakley@iee.email \
--cc=sibisiddharthan.github@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).