On Thu, Mar 21, 2019 at 12:31 PM Michael Paquier <mich...@paquier.xyz> wrote:
> On Thu, Mar 21, 2019 at 09:47:02AM +0900, Michael Paquier wrote: > > When it comes to support newer versions of MSVC, we have come up > > lately to backpatch that down to two stable versions but not further > > down (see f2ab389 for v10 and v9.6), so it looks sensible to target > > v11 and v10 as well if we were to do it today, and v11/v12 if we do it > > in six months per the latest trends. > > By the way, you mentioned upthread that all the branches can compile > with MSVC 2017, but that's not actually the case for 9.5 and 9.4 if > you don't back-patch f2ab389 further down. > The commit f2ab389 is later back-patch to version till 9.3 in commit 19acfd65. I guess that building the windows installer for all the versions using the same visual studio is may be the reason behind that back-patch. Regards, Haribabu Kommi Fujitsu Australia
