Visual Studio 2017 Support
Issue #15
resolved
I know this one is a bit on the tricky side, but I know both SCons and parts do not have support for this release of Visual Studio. I did some digging into what is wrong and it turns out the Microsoft dropped registry support in exchange for targeting something called setup package. The reason for this has to do with the potential for more than one installation of VS2017 on a given system. This will probably complicate things going into the future.
Something interesting that I did encounter is that CMake does have some support for VS2017 discovery. You can checkout this file from their source tree that is doing the COM API work to discover VS. I can only assume SCons and parts will need to do something similar.
Comments (5)
-
reporter
-
reporter
Pull request is up to get this integrated into SCons. I have a change to get 2017 enabled in parts as well, but waiting for SCons. See: https://bitbucket.org/scons/scons/pull-requests/425/enable-initial-visual-studio-2017-support/diff.
-
- changed status to resolved
So we have some support for vs 2017 thanks to Dean patch. I am going to say this is resolved, and that it can be improved on as we find issues
-
Hi! Thanks for the patch, it works great! However it needs a fix for the case when VS 2017 is not installed and COM-interface is not available. The fix is pretty trivial:
https://bitbucket.org/c0ff/scons/commits/f7e94602b3eb8ee2bed40deca8d9dbdd40c7a8d5
-
reporter
I've updated my pull request on SCons to reflect that exception catch.
- Log in to comment
I did some reading into WAF and found that they have some support for VS2017. I'm not 100% sure this is how to roll out support, but it appears it works for them: https://github.com/waf-project/waf/commit/d86f2ccd17261cd83cae1d425852e72fa6e3b048. Be sure to check a follow on commit because their detection of the dev command changes to a different location. Interesting stuff.