No description provided.
doc: Mention required workload when building with MSVC #26498
pull hebasto wants to merge 1 commits into bitcoin:master from hebasto:221114-ms-doc changing 1 files +3 −1-
hebasto commented at 2:48 PM on November 14, 2022: member
-
doc: Mention required workload when building with MSVC f97892d21a
-
hebasto commented at 2:49 PM on November 14, 2022: member
Friendly ping @Sjors @sipsorcery
- DrahtBot added the label Docs on Nov 14, 2022
-
sipsorcery commented at 10:47 PM on November 14, 2022: member
ACK f97892d21af9fa1d5c3b07b37e233b0bea0807e7.
-
shaavan commented at 2:10 PM on November 15, 2022: contributor
Do we need all the individual components from the "Desktop development with C++" workload when building with MSVC?
-
hebasto commented at 2:16 PM on November 15, 2022: member
Do we need all the individual components from the "Desktop development with C++" workload when building with MSVC?
No, we don't. The default ones are just enough.
-
jarolrod commented at 2:18 AM on November 22, 2022: member
Correct me if i'm mistaken, but the
Visual Studio Build Tools component, when following the provided link, is only available at the bottom of the page and hidden behind a drop down menu titledTools for Visual Studio. Perhaps mention this here so that someone doesn't give up and end up downloading Visual Studio 2022 in frustration of not finding the target download. -
DrahtBot commented at 2:18 AM on November 22, 2022: contributor
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--021abf342d371248e50ceaed478a90ca-->
Reviews
See the guideline for information on the review process.
Type Reviewers ACK sipsorcery -
hebasto commented at 9:19 AM on November 22, 2022: member
Correct me if i'm mistaken, but the
Visual Studio Build Tools component, when following the provided link, is only available at the bottom of the page and hidden behind a drop down menu titledTools for Visual Studio. Perhaps mention this here so that someone doesn't give up and end up downloading Visual Studio 2022 in frustration of not finding the target download.That's correct. Mind suggesting a better wording aligned with this repo's approach to documenting the use of third-party tools?
- maflcko merged this on Nov 28, 2022
- maflcko closed this on Nov 28, 2022
- hebasto deleted the branch on Nov 28, 2022
- sidhujag referenced this in commit 65027f4f1b on Dec 1, 2022
- bitcoin locked this on Nov 28, 2023