The first two items make available to an SCons end-user all of the msvc batch file options available to command-line users. Implementation of Item 2 in the current SCons code base is not as straightforward as Items 1 and 3 and has been deferred to a later date. In the interest of full disclosure: the author also has a code branch ready implementing Items 1 and 3 above but has not updated the requisite documentation yet. Passing a user-defined environment (i.e., ENV-like) dictionary to be used in lieu of SCons msvc detection or user-specified script.Passing user-defined arguments when using the normal SCons msvc detection,.Passing user-defined arguments to the user-defined script specified via MSVC_USE_SCRIPT,.
There are three potential enhancements to msvc usage that would enhance the user experience: With the recent PR proposing adding arguments to user-defined script/batch files (MSVC_USE_SCRIPT can pass in args #4102), perhaps it is worthwhile to revive the discussion had earlier in PR #4063.
0 kommentar(er)
