Hi John,
>
> Op 11-aug.-2015 16:37 schreef "Stefan Fuhrmann"
> <stefan.fuhrmann_at_wandisco.com <mailto:stefan.fuhrmann_at_wandisco.com>>:
> >
> > On Mon, Aug 10, 2015 at 3:40 AM, Stefan <luke1410_at_posteo.de
> <mailto:luke1410_at_posteo.de>> wrote:
> >>
> >> Hi,
> >>
> >> I'm wondering whether it would be reasonable to release another
> 1.7-build.
> >>
> >> 1.7.21 added support to build 1.7 using Visual Studio 2015. However
> there seemed to have been an oversight with neon, which misses the
> platformtoolset-setting in the project file (see: [PATCH] Fix SVN 1.7
> build issues with VS >2010).
> >>
> >> This leads to a linker issue, when u try to build SVN 1.7 out of
> the box using VS >= 2013.
> >>
> >> In the light of 1.7 no longer being supported it still might be a
> good idea to release a final 1.7 build so at least the stated VS 2015
> is not broken forever for 1.7.
> >>
> >> If it's going to be released, then I'd also propose to apply the
> correctness-patch (see: [PATCH] correct ToolsVersion in VS project
> files) which also corrects the ToolsVersion-parameter for VS >= 2013.
> >
> >
> > I fine with canning 1.7.22 in favor of a "truly golden" 1.7.23.
> > After all, we rolled 1.7.22 for a similar reason not because
> > of actual user code breakage.
> >
> > That said, it may require extra testing effort on Windows
> > (at least testing that vs2015 and vs2013 work) and I'd
> > rather have our Windows devs comment on that.
> >
> > -- Stefan^2.
>
> I can test on vs2013. If necessary I can also upgrade my environment
> to vs 2015, but I'd prefer to keep 2013 for now (and I don't think I
> can use them both alongside each other).
>
Just so you know: Using VS 2015 and VS 2013 alongside one another is
supported and works quite well (have it running here too -- actually
I've set up VS 2010, 2012, 2013 and 2015 all on the same machine).
Regards,
Stefan
Received on 2015-08-11 23:28:40 CEST