Skip to content

Latest commit

 

History

History
103 lines (85 loc) · 7.03 KB

createDevEnvironment.md

File metadata and controls

103 lines (85 loc) · 7.03 KB
Raw

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 should fork and clone the repository.

Use the --recursive option when performing git clone to fetch the required git submodules we use.

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 nvaccess master branch is updated. To ensure your work is always based on the latest commit in the nvaccess master branch, it is recommended that your master branch be linked to the nvaccess 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 nvaccess branches.
git fetch nvaccess
# Switch to the local master branch.
git checkout master
# Set the local master to use the nvaccess master as its upstream.
git branch -u nvaccess/master
# Update the local master.
git pull

Supported Operating Systems

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.

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.11, 32 bit.

To replicate the production build environment, use the 3.11.x minor version of Python that AppVeyor uses for the Visual Studio 2022 environment.

Microsoft Visual Studio

  • Microsoft Visual Studio 2022
    • To replicate the production build environment, use the version of Visual Studio 2022 that AppVeyor is using.
    • When you do not use the Visual Studio IDE itself, you can download the build tools
    • When you are intending to use the Visual Studio IDE (not required for NVDA development), you can download the community version, which is also used by AppVeyor
    • The Professional and Enterprise versions are also supported
    • Preview versions are not supported
  • 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.22621.0)
      • MSVC v143 - VS 2022 C++ ARM64 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.

For reference, the following run time dependencies are included in Git submodules:

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

The following dependencies aren't needed by most people, and are not included in Git submodules:

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 requirements.txt 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.