diff options
author | FranklinDM <mrmineshafter17@gmail.com> | 2022-09-17 17:48:50 +0800 |
---|---|---|
committer | Moonchild <moonchild@palemoon.org> | 2022-10-23 21:30:17 +0000 |
commit | d8ef6bf7af085c252027fd3cfc6106ca69c61df4 (patch) | |
tree | 50dda6cd0fb3268d1987b43daea425b03025e5db /python | |
parent | 825fb3a207f21254f4f0a65f6433d6a9650050aa (diff) | |
download | uxp-d8ef6bf7af085c252027fd3cfc6106ca69c61df4.tar.gz |
Issue #1956 - Look for Visual Studio's path directly in the mozdebug module
This change modifies the mozdebug module to include a special case for Visual Studio when looking for its path.
This also removes the workaround implemented in dcb027a7184442e140aad1921a5f26fe9135c1da which can break debugging in certain installations of Visual Studio 2015.
Diffstat (limited to 'python')
-rw-r--r-- | python/mozbuild/mozbuild/mach_commands.py | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/python/mozbuild/mozbuild/mach_commands.py b/python/mozbuild/mozbuild/mach_commands.py index 38a98b7432..a6d704300b 100644 --- a/python/mozbuild/mozbuild/mach_commands.py +++ b/python/mozbuild/mozbuild/mach_commands.py @@ -1245,11 +1245,6 @@ class RunProgram(MachCommandBase): if debug or debugger or debugparams: if 'INSIDE_EMACS' in os.environ: self.log_manager.terminal_handler.setLevel(logging.WARNING) - # vswhere tells us the exact path of the "devenv.exe" debug executable, but our build machinery - # insists on searching the PATH for it regardless. Just work around it rather than overhauling mozdebug. - if sys.platform.startswith('win'): - tempvar = subprocess.check_output(['vswhere', '-property', 'installationPath']) - os.environ["PATH"] += os.pathsep + tempvar.replace("\\", "\\").strip() + "\\Common7\\IDE" import mozdebug if not debugger: |