scons launcher and scons dist don't rebuild #13372
Description
TL;DR
scons launcher or scons dist commands don't seem to be able to pick up code changes after first execution. In other words, they can build successfully for the first time, but they cannot rebuild as they don't appear to see that code has changed.
As to why this can be useful, in my example, I have NVDA build environment on my personal laptop, but I am trying to debug an issue with MS WOrd, which is only installed on my work laptop. I cannot build NVDA on work laptop, nor can I install MS Word on my personal laptop. As a result I need to frequently repeat the cycle of making code change, rebuild and test on work laptop.
Steps to reproduce:
The following steps use scons launcher command but all the same applies to scons dist as well.
- Get a fresh copy of NVDA:
> git clone --recursive https://github.com/nvaccess/nvda.git
> ...
> cd nvda
- Build launcher:
> scons launcher
... many lines of actual building process omitted
scons: done building targets.
- Check that launcher was built successfully:
> output\nvda_snapshot_source-master-6310b86.exe
- Adding the following lines in core.py in def main right before
app.MainLoop():
import tones
tones.beep(1000, 1000)
- Running NVDA from source to make sure beep can be heard:
> runnvda.bat
- Rebuild launcher:
> scons launcher
...
scons: `launcher' is up to date.
scons: done building targets.
- It appears scons didn't see any changes and didn't do anything, but let's try to run launcher again to see whether the beep can be heard:
$ output\nvda_snapshot_source-master-6310b86.exe
Actual behavior:
scons launcher doesn't see code changes and does not rebuild after code change. After my attempt to rebuild, no beep is heard when launching launcher.
Expected behavior:
scons launcher should be able to see code changes and rebuild launcher with code changes. Beep should be heard when launching launcher.
System configuration
NVDA installed/portable/running from source:
Running from source
NVDA version:
Commit 6310b86
Windows version:
Windows 11
Name and version of other software in use when reproducing the issue:
N/A
Other information about your system:
N/A
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
N/A