Skip to content

Conversation

@amit-rastogi
Copy link
Contributor

@amit-rastogi amit-rastogi commented May 31, 2020

Updated the build instructions as part of #761 in ReadMe.md to use the vcpkg submodule present in this STL repository instead of separately cloning. The user can alternatively, use a separate installation of vcpkg.

Both the build steps mentioned below have been updated -

  1. How To Build With The Visual Studio IDE
  2. How To Build With A Native Tools Command Prompt

Fixes #761.

Updated the build instructions in ReadMe.md to use the vcpkg submodule present in this STL repository. The user can alternatively, use a separate installation of vcpkg. Both the build steps given below have been updated -
1. How To Build With The Visual Studio IDE
2. How To Build With A Native Tools Command Prompt
@amit-rastogi amit-rastogi requested a review from a team as a code owner May 31, 2020 19:45
Updated ReadMe.md with the following steps as per review comments-

cd STL
git submodule update --init -- vcpkg/
@CaseyCarter CaseyCarter added the documentation Related to documentation or comments label Jun 3, 2020
Updated ReadMe.md as per review comments mainly -
-removed vcpkg submodule init for IDE build step. 
-updated vcpkg init command for Command Prompt build step
-updated example path of vcpkg specified to cmake to use the repository submodule path
1. reverted back to using command prompt for cloning the STL repository, init of vcpkg and boost math installation in case of build steps using IDE.
2. added --progress option to submodule update of vcpkg as mentioned in microsoft#805
@StephanTLavavej StephanTLavavej added the decision needed We need to choose something before working on this label Jul 8, 2020
@StephanTLavavej
Copy link
Member

Tagging as decision needed because as @Chronial noted, changing the global configuration for vcpkg to point to a repo-local submodule may not be desirable. We'll need to avoid this problem, probably by changing only the command-line instructions to use the submodule.

@cbezault cbezault removed the decision needed We need to choose something before working on this label Jul 29, 2020
@CaseyCarter CaseyCarter removed their assignment Aug 12, 2020
@ghost ghost deleted a comment from msftclas Aug 19, 2020
After microsoft#1124 was merged the steps to get started were simplified to not need `vcpkg integrate`.
Copy link
Contributor

@CaseyCarter CaseyCarter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This all looks good - just a minor mechanical tweak that I'll merge.

According to https://github.github.com/gfm/#code-spans , we don't need
4 backticks; 2 will work. We can also get the space trimmed away - we
need a single space before and after for that to work. Finally,
capitalize Ctrl.

Drop the mention of adding `boost-math:arm-windows boost-math:arm64-windows`
to the `vcpkg.exe install` command - this requires ARM/ARM64 support to
be installed in VS, it has to be performed as a separate
`vcpkg.exe install` command (because it requires `boost-build:x86-windows`,
installed by the first command), this isn't mentioned in the
command-line instructions, and it is unnecessary for most users.

We can also drop "Assuming you are targeting x86 and x64," so this
exactly matches the command-line phrasing.
@StephanTLavavej
Copy link
Member

Thanks! I pushed two changes: a small Markdown cleanup, and removing pre-existing ARM/ARM64 wording that wasn't quite right.

  1. According to https://github.github.com/gfm/#code-spans , we don't need 4 backticks; 2 will work. We can also get the space trimmed away - we need a single space before and after for that to work. Finally, capitalize Ctrl.

  2. Drop the mention of adding boost-math:arm-windows boost-math:arm64-windows to the vcpkg.exe install command - this requires ARM/ARM64 support to be installed in VS, it has to be performed as a separate vcpkg.exe install command (because it requires boost-build:x86-windows, installed by the first command), this isn't mentioned in the command-line instructions, and it is unnecessary for most users. We can also drop "Assuming you are targeting x86 and x64," so this exactly matches the command-line phrasing.

I've filed #1211 to track explaining ARM/ARM64 properly; that shouldn't hold up this PR, which now nicely aligns the IDE and command-line instructions.

@BillyONeal
Copy link
Member

As long as someone actually ran through this from a clean box and checked that it worked that sounds good to me

@CaseyCarter
Copy link
Contributor

As long as someone actually ran through this from a clean box and checked that it worked that sounds good to me

I ran through everything but the ARM/ARM64 bits that we excised and had success.

@StephanTLavavej StephanTLavavej self-assigned this Aug 21, 2020
@StephanTLavavej StephanTLavavej merged commit a293fad into microsoft:master Aug 22, 2020
@StephanTLavavej
Copy link
Member

Thanks for improving the "getting started" experience for new users, and congratulations on your first microsoft/STL commit! 🎉 😸

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Related to documentation or comments

Projects

None yet

Development

Successfully merging this pull request may close these issues.

README.md: Use the vcpkg submodule instead of separately cloning

8 participants