Windows build instructions out of date - VS Community Edition 2019 no longer available
Categories
(Firefox Build System :: General, defect)
Tracking
(firefox96 fixed)
| Tracking | Status | |
|---|---|---|
| firefox96 | --- | fixed |
People
(Reporter: jwatt, Assigned: mhentges)
References
Details
Attachments
(1 file)
https://firefox-source-docs.mozilla.org/setup/windows_build.html#install-visual-studio
The instructions say to install the Community edition of Visual Studio 2019. However, the MS page that's linked to now only makes VS 2022 available.
|
Reporter | |
Comment 1•3 years ago
|
||
The build completes, runs and seems to function after installing VS Community 2022 with the following two items from the "Individual components" tab. (These versions of the components were selected by default after selecting the 'Desktop development with C++' and 'Game development with C++' workloads, as per our docs.)
- Windows 10 SDK (10.0.19041.0)
- C++ ATL for latest v143 build tools (x86 & x64)
The other available versions for those components were:
- Windows 10 SDK (10.0.18362.0)
- Windows 10 SDK (10.0.20348.0)
- Windows 11 SDK (10.0.22000.0)
- C++ ATL for v141 build tools (x86 & x64)
- C++ v14.29 (16.11) ATL for v142 build tools (x86 & x64)
- C++ v14.30 (17.0) ATL for v143 build tools (x86 & x64)
So to be clear, the versions of these components mentioned in our build documentation are not available in VS Community 2022.
|
Assignee | |
Comment 2•3 years ago
|
||
FWIW, it looks we can still download Visual Studio 2019 from here.
However, I'm interested in bumping our dependency versions - look at these release notes, I'm sure we'll want to leverage some of the new goodies at some point in the future.
There's risk of breakage here, but I'm thinking that we can do the following:
- Change from recommending that users install all of VS to just install VS build tools
- Bump recommendation from 2019 -> 2022
- Bump components that should be selected (up to
10.0.22000.0, since its issues have been resolved, I believe) - Add a temporary "note" to the docs saying "we've recently bumped the Windows tooling versions, if you run into issues report a bug/ask in #build, and the solution might be to downgrade to <link to 2019>".
|
|
Assignee | |
Updated•3 years ago
|
|
|
Assignee | |
Comment 3•3 years ago
|
||
Two things to note after the above comment:
- The Windows SDK
10.0.19041is selected by default, so until we need a newer one, I think recommending the default one is acceptable - If we move the "build tools", there's no option for "Game Development with C++". However, I'm able to do a full build despite not having it - perhaps it's not needed anymore? Its recommendation within the docs traces back to (somewhere on) MDN, so I can't get the full history.
|
|
Assignee | |
Comment 4•3 years ago
|
||
- Recommend the Build Tools over the full Community IDE install
- Bump Windows 10 SDK, C++ ATL version
- Remove "Game development with C++" workload, because it doesn't seem
to be required anymore - I'm leaning on review and natural
developer-testing to confirm this assumption.
|
|
Reporter | |
Comment 5•3 years ago
|
||
(In reply to Mitchell Hentges [:mhentges] 🦀 from comment #4)
- Remove "Game development with C++" workload, because it doesn't seem
to be required anymore
Bas, perhaps you know the history there, or can loop in someone who might?
|
|
Assignee | |
Comment 6•3 years ago
|
||
I'm going to land this patch since it's been sitting for a bit, but we can make adjustments if Bas has recommendations 👍
|
||
Comment 8•3 years ago
|
||
| bugherder | ||
|
||
Comment 9•3 years ago
|
||
(In reply to Jonathan Watt [:jwatt] from comment #5)
(In reply to Mitchell Hentges [:mhentges] 🦀 from comment #4)
- Remove "Game development with C++" workload, because it doesn't seem
to be required anymoreBas, perhaps you know the history there, or can loop in someone who might?
Yes, that hasn't been used for years, that was because without that not all the required DirectX materials would be included, but that has not been the case for years.
Description
•