Link to issue number:

Fixes #13290
Related to this thread on nvda-devel by @MarcoZehe

Summary of the issue:

PR #13226 started building nVDA in parallel. While this offers significant speed improvements the way in which we were generating COMInterfaces was not thread safe. The issue was caused by the fileinput module which redirects stdout to a given file and this cannot be done in multiple threads at the same time. Also, as discovered by @MarcoZehe in the thread linked above when stdout is redirected to a file some other build step which is executing in a separate thread can write to it and the text which should be shown on screen ends up in the COMInterface file.

Description of how this pull request fixes the issue:

Were not using fileinput anymore - the IDE friendly content is generated in memory and then written to the file afterwards.

Testing strategy:

Made sure that COMInterfaces can be generated from a clean checkout.

Known issues with pull request:

None known

Change log entries:

None needed.

Code Review Checklist:

• Pull Request description:
  • description is up to date
  • change log entries
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• API is compatible with existing add-ons.
• Documentation:
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English