Revision history [back]
The build command runs in a separate process before the debug process so can't be used to set the env directly for that process (i.e. setting the env in the build process itself won't do it), but it could set the env in a way that is then inherited by the debug process (such as system/user-wide).
To create one, go into Project Properties under the Debug/Execute tab and set the Build Command. You may want to set up the command first in the OS Commands tool and then select it from the Build Command property.
Another idea is to write an extension script that uses GetEnvironment/SetEnvironment on CAPIProject to set the env directly into Wing's Project Properties, and then execute that before debugging (either via a key binding, added menu item, or write the script so that it also starts debugging with the debug-continue or debug-file commands, via CAPIApplication's ExecuteCommand).
The build command runs in a separate process before the debug process so can't be used to set the env directly for that process (i.e. setting the env in the build process itself won't do it), but it could set the env in a way that is then inherited by the debug process (such as system/user-wide).
To create one, go into Project Properties under the Debug/Execute tab and set the Build Command. You may want to set up the command first in the OS Commands tool and then select it from the Build Command property.
Another idea is to write an extension script that uses GetEnvironment/SetEnvironment on CAPIProject to set the env directly direcly into Wing's Project Properties, and then execute that before debugging (either via a key binding, added menu item, or write the script so that it also starts debugging with the debug-continue or debug-file commands, via CAPIApplication's ExecuteCommand).