-
-
Notifications
You must be signed in to change notification settings - Fork 754
Open
Labels
audience/nvda-devPR or issue is relevant to NVDA / Add-on developersPR or issue is relevant to NVDA / Add-on developerscomponent/documentationcomponent/synthDriverHostp5https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Description
Related issues, PRs or discussions
What is the current state of the codebase?
The 32-bit synth driver host introduced in #19432 is not built with scons. Rather, one runs the setup-runtime.py script in runtime-builders/synthDriverHost32. However, this fact doesn't seem to be documented anywhere.
Why are changes required?
Developers shouldn't have to look at the GitHub actions workflow to find out how to build the synth driver host.
What technical changes are required?
None. This issue is purely requesting documentation.
Are the proposed technical changes API breaking?
There aren't any with which to break an API.
Are there potential risks or issues with the proposed implementation?
Not really. Care should probably be taken to explain the prerequisites for building the synth driver host runtime, since they differ from those for building the rest of NVDA.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
audience/nvda-devPR or issue is relevant to NVDA / Add-on developersPR or issue is relevant to NVDA / Add-on developerscomponent/documentationcomponent/synthDriverHostp5https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.