[Scons-users] Is there a plan to support visual studio 2017 in the next release of Scons?

[Dean Glazeski]

That's true, but I don't know if I would go that far. Some folks aren't
going to install 2017 at which point you'd make SCons useless for Windows
developers.  You also lose some query modes if you start using the legacy
mode of vswhere.  I would keep the old discovery methods until those old
versions are no longer supported.

On Wed, Jun 28, 2017, 17:26 Bill Deegan <bill at baddogconsulting.com> wrote:

> Dean,
>
> Also looks like it finds all installs of VS on the system?
> So might work to replace all existing logic used to find install?
>
> _Bill
>
> On Wed, Jun 28, 2017 at 4:21 PM, Dean Glazeski <dnglaze at gmail.com> wrote:
>
>> I did the original pull request and have done some work integrating one
>> of my other tools to use vswhere.  I just need to find a slice of time to
>> update that pull request to rely on vswhere to locate VS2017.  That might
>> have a better chance of inclusion than relying on another library to do the
>> COM lookup.  At least I believe that's the current hold up.
>>
>> vswhere is actually pretty nice because you can pull out installation
>> information as JSON so it's pretty simple to load it all up.
>>
>> On Wed, Jun 28, 2017 at 2:57 PM Russel Winder <russel at winder.org.uk>
>> wrote:
>>
>>> On Tue, 2017-06-27 at 03:46 +0000, Napat Parkpien wrote:
>>> > Hi,
>>> >
>>> > My team is migrating to visual studio 2017, but current release of
>>> scons
>>> > is not support it.
>>> > Is there a way to support vs2017 in current release?
>>> > Or will it support in the next version?
>>> >
>>>
>>> SCons is a FOSS project with no paid workers. So even if a feature is
>>> important, it relies on volunteers to step up to create pull requests.
>>>
>>> An excellent way for other projects wanting new features in SCons is, as
>>> you
>>> have done, raise the point on this email list. This may then lead to
>>> someone
>>> volunteering to create a pull request, or it may not. In the case of
>>> not, it
>>> really requires the proposer to resource creating the pull request ether
>>> by
>>> getting someoe internal to do it or by funding someone external to do it.
>>>
>>> Clearly this point about SCons and VS2017 is important for SCons, I think
>>> Bill has responded on this. However, that gives us agreement that it is
>>> on
>>> the roadmap, but it doesn't neessarily mean it will get done – unless
>>> someone for whom the problem is important steps up and provides a pull
>>> request.
>>>
>>> Is there any chance you team can chip in by making VS2017 and SCons
>>> compatible? SCons version 3.0 is in alpha but that makes i an excellent
>>> time
>>> to get a puul request in.
>>>
>>>
>>> --
>>> Russel.
>>>
>>> =============================================================================
>>> Dr Russel Winder     t:+44 20 7585 2200 <+44%2020%207585%202200>
>>>  voip:sip:
>>> russel.winder at ekiga.net
>>> 41 Buckmaster Road   m:+44 7770 465 077 <+44%207770%20465077>
>>> xmpp:russel at winder.org.uk
>>> London SW11 1EN, UK  w: www.russel.org.uk
>>> skype:russel_winder_______________________________________________
>>> Scons-users mailing list
>>> Scons-users at scons.org
>>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>>
>>
>> _______________________________________________
>> Scons-users mailing list
>> Scons-users at scons.org
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>
>>
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20170628/8d0d12d6/attachment.html>