Skip to content

createDevEnvironment.md

Latest commit

 

History

History
133 lines (95 loc) · 6.71 KB

createDevEnvironment.md

File metadata and controls

133 lines (95 loc) · 6.71 KB

Create NVDA Development Environment

Getting the Source Code

The NVDA project uses the git version control system for its source code and documentation.

The NVDA repository is located at https://github.com/nvaccess/nvda.

If you plan on contributing to NVDA, you will need to fork and clone the repository.

After forking the repository into your user account (YOUR-USERNAME), clone with --recursive to fetch all required submodules.

git clone --recursive https://github.com/YOUR-USERNAME/nvda.git

Keeping the fork in sync

When you fork the repository, GitHub will create a copy of the master branch. However, this branch will not be updated when the NV Access master branch is updated. To ensure your work is always based on the latest commit in the nvaccess/nvda master branch, it is recommended that your master branch be linked to the nvaccess/nvda master branch, rather than the master branch in your GitHub fork. You can do this from the command line as follows:

# Add a remote for the NV Access repository.
git remote add nvaccess https://github.com/nvaccess/nvda.git
# Fetch the NV Access branches.
git fetch nvaccess
# Switch to the local master branch.
git checkout master
# Set the local master to use the NV Access master as its upstream.
git branch -u nvaccess/master
# Update the local master.
git pull

Supported Operating Systems

At a minimum, running and building NVDA from source requires Windows 10 (Version 1507). We recommend Windows 11 to work with features under active support, and if you need to use Windows 10, use Version 22H2.

Dependencies

The NVDA source depends on several other packages to run correctly.

Installed Dependencies

The following dependencies need to be installed on your system:

Python

Python, version 3.13.13, 64-bit. Install the python version listed in .python-versions

uv

uv is used as package and project manager.

Microsoft Visual Studio

  • Microsoft Visual Studio 2022 or 2026
  • When installing Visual Studio, additional components must be included:
    • You can automatically fetch these using NVDAs .vsconfig using the import feature of the VS installer.
    • In the list on the Workloads tab, in the Desktop grouping:
      • Desktop development with C++.
        • Once selected, ensure "C++ Clang tools for Windows" is included under the optional grouping.
    • On the Individual components tab, ensure the following items are selected:
      • Windows 11 SDK (10.0.26100.x)
      • MSVC v143 - VS 2022 C++ ARM64/ARM64EC build tools
      • MSVC v143 - VS 2022 C++ x64/x86 build tools
      • C++ ATL for v143 build tools (x86 & x64)
      • C++ ATL for v143 build tools (ARM64/ARM64EC)

Git Submodules

Some of the dependencies are contained in Git submodules. If you didn't pass the --recursive option to git clone, you will need to run git submodule update --init. Whenever a required submodule commit changes (e.g. after git pull), you will need to run git submodule update. If you aren't sure, run git submodule update after every git pull, merge or checkout.

Run time dependencies

Build time dependencies

The following build time dependencies are included in the miscDeps git submodule:

VS Code

  • If you use Visual Studio Code as your integrated development environment, you get the benefit of our prepopulated workspace configuration, which is included as a submodule. If you do not wish to use the pre-populated VS Code workspace configuration, you can unregister the .vscode submodule.

    git submodule deinit .vscode

    If you change your mind, you can re-enable it at any time.

    git submodule init .vscode

Python dependencies

NVDA and its build system also depend on an extensive list of Python packages. They are all listed with their specific versions in the pyproject.toml file in the root of this repository. However, the build system takes care of fetching these itself when needed. These packages will be installed into an isolated Python virtual environment within this repository, and will not affect your system-wide set of packages.

Other dependencies

The following dependencies aren't needed by most people: