Skip to content

Commit 5df20d9

Browse files
michaelDCurranmichaelDCurran
authored
Merge f855ae0 into f14d344 
2 parents f14d344 + f855ae0 commit 5df20d9

4 files changed

Lines changed: 43 additions & 24 deletions

File tree

‎.vsconfig‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
{
2+
"version": "1.0",
3+
"components": [
4+
"Microsoft.VisualStudio.Workload.NativeDesktop",
5+
"Microsoft.VisualStudio.Component.Windows11SDK.22621",
6+
"Microsoft.VisualStudio.Component.VC.Llvm.ClangToolset",
7+
"Microsoft.VisualStudio.Component.VC.Llvm.Clang",
8+
"Microsoft.VisualStudio.Component.VC.Tools.x86.x64",
9+
"Microsoft.VisualStudio.Component.VC.Tools.ARM64EC",
10+
"Microsoft.VisualStudio.Component.VC.Tools.ARM64",
11+
"Microsoft.VisualStudio.Component.VC.ATL",
12+
"Microsoft.VisualStudio.Component.VC.ATL.ARM64"
13+
]
14+
}

‎appveyor.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
# Many more options available, see docs:
33
# https://www.appveyor.com/docs/appveyor-yml/
44

5-
os: Visual Studio 2019
5+
os: Visual Studio 2022
66
version: "{branch}-{build}"
77

88
branches:

‎projectDocs/dev/createDevEnvironment.md‎

Lines changed: 26 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -26,35 +26,37 @@ git pull
2626
```
2727

2828
## Supported Operating Systems
29-
Although NVDA can run on any Windows version starting from Windows 7 Service pack 1, building NVDA from source is currently limited to only Windows 10 and above.
29+
Although NVDA can run on any Windows version starting from Windows 8.1, building NVDA from source is currently limited to only Windows 10 and above.
3030

3131
## Dependencies
3232
The NVDA source depends on several other packages to run correctly.
3333

3434
### Installed Dependencies
3535
The following dependencies need to be installed on your system:
3636

37-
* [Python](https://www.python.org/), version 3.11, 32 bit
38-
* Use latest minor version if possible.
39-
* Microsoft Visual Studio 2019 or 2022:
40-
* To replicate the production build environment, use the [version of Visual Studio 2019 that AppVeyor is using](https://www.appveyor.com/docs/windows-images-software/#visual-studio-2019).
41-
* When you do not use the Visual Studio IDE itself, you can download the [build tools](https://aka.ms/vs/16/release/vs_BuildTools.exe)
42-
* When you are intending to use the Visual Studio IDE (not required for NVDA development), you can download [the community version](https://aka.ms/vs/16/release/vs_Community.exe), which is also used by appveyor
43-
* The Professional and Enterprise versions are also supported
44-
* Preview versions are *not* supported
45-
* When installing Visual Studio 2019, you need to enable the following:
46-
* In the list on the Workloads tab
47-
* in the Windows grouping:
48-
* Desktop development with C++
49-
* Then in the Installation details tree view, under Desktop for C++, Optional, ensure the following are selected:
50-
* MSVC v142 - VS 2019 C++ x64/x86 build tools
51-
* Windows 11 SDK (10.0.22000.0)
52-
* C++ ATL for v142 build tools (x86 & x64)
53-
* C++ Clang tools for Windows
54-
* On the Individual components tab, ensure the following items are selected:
55-
* MSVC v142 - VS 2019 C++ ARM64 build tools
56-
* C++ ATL for v142 build tools (ARM64)
57-
* If installing Visual Studio 2022: choose all the same above components as for 2019, but V143 variants, rather than V142.
37+
#### Python
38+
[Python](https://www.python.org/), version 3.11, 32 bit.
39+
40+
To replicate the production build environment, use the 3.11.x minor version of Python that [AppVeyor uses for the Visual Studio 2022 environment](https://www.appveyor.com/docs/windows-images-software/#python).
41+
42+
#### Microsoft Visual Studio
43+
* Microsoft Visual Studio 2022
44+
* To replicate the production build environment, use the [version of Visual Studio 2022 that AppVeyor is using](https://www.appveyor.com/docs/windows-images-software/#visual-studio-2022).
45+
* When you do not use the Visual Studio IDE itself, you can download the [build tools](https://aka.ms/vs/17/release/vs_BuildTools.exe)
46+
* When you are intending to use the Visual Studio IDE (not required for NVDA development), you can download [the community version](https://aka.ms/vs/17/release/vs_Community.exe), which is also used by AppVeyor
47+
* The Professional and Enterprise versions are also supported
48+
* Preview versions are *not* supported
49+
* When installing Visual Studio, additional components must be included
50+
* You can automatically fetch these using [NVDAs .vsconfig](../../.vsconfig) using the [import feature of the VS installer](https://learn.microsoft.com/en-us/visualstudio/install/import-export-installation-configurations?view=vs-2022#import-a-configuration)
51+
* In the list on the Workloads tab, in the Desktop grouping:
52+
* Desktop development with C++.
53+
* Once selected, ensure "C++ Clang tools for Windows" is included under the optional grouping.
54+
* On the Individual components tab, ensure the following items are selected:
55+
* Windows 11 SDK (10.0.22621.0)
56+
* MSVC v143 - VS 2022 C++ ARM64 build tools
57+
* MSVC v143 - VS 2022 C++ x64/x86 build tools
58+
* C++ ATL for v143 build tools (x86 & x64)
59+
* C++ ATL for v143 build tools (ARM64)
5860

5961
### Git Submodules
6062
Some of the dependencies are contained in Git submodules.
@@ -74,13 +76,14 @@ For reference, the following run time dependencies are included in Git submodule
7476
* [Microsoft Detours](https://github.com/microsoft/Detours), commit `4b8c659f549b0ab21cf649377c7a84eb708f5e68`
7577
* brlapi Python bindings, version 0.8.5 or later, distributed with [BRLTTY for Windows](https://brltty.app/download.html), version 6.6
7678
* lilli.dll, version 2.1.0.0
77-
* [Python interface to FTDI driver/chip](http://fluidmotion.dyndns.org/zenphoto/index.php?p=news&title=Python-interface-to-FTDI-driver-chip)
79+
* Python interface to FTDI driver/chip
7880
* [Nullsoft Install System](https://nsis.sourceforge.io), version 3.08
7981
* [Java Access Bridge 32 bit, from Zulu Community OpenJDK build 13.0.1+10Zulu (13.28.11)](https://github.com/nvaccess/javaAccessBridge32-bin)
8082
* [wil](https://github.com/microsoft/wil/)
8183
* [Microsoft UI Automation Remote Operations Library, forked from @microsoft by @michaeldcurran](https://www.github.com/michaeldcurran/microsoft-ui-uiautomation/)
8284
* Commit 224b22f3bf9e
8385
* The fork specifically adds support for CallExtension / IsExtensionSupported to the high-level API, see pr microsoft/microsoft-ui-uiautomation#84 and #95.
86+
* [NVDA DiffMatchPatch](https://github.com/codeofdusk/nvda_dmp)
8487

8588
Additionally, the following build time dependencies are included in the miscDeps git submodule:
8689

‎user_docs/en/changes.t2t‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,8 @@ Please refer to [the developer guide https://www.nvaccess.org/files/nvda/documen
5454

5555
- Note: this is an Add-on API compatibility breaking release.
5656
Add-ons will need to be re-tested and have their manifest updated.
57+
- Building NVDA now requires Visual Studio 2022.
58+
Please refer to the [NVDA docs https://github.com/nvaccess/nvda/blob/release-2024.1/projectDocs/dev/createDevEnvironment.md] for the specific list of Visual Studio components. (#14313)
5759
- Added the following extension points:
5860
- ``treeInterceptorHandler.post_browseModeStateChange``. (#14969, @nvdaes)
5961
- ``speech.speechCanceled``. (#15700, @LeonarddeR)

0 commit comments

Comments
 (0)