@Charlie, we have two separate solution: first one for VS 2010 and second
one for VS 2013.
I think it would be better to mark VS 2010 as obsolete and remove it from
master forever. As far as I know David P. Anderson still use VS 2010 for
development. VS 2013 can be potentially upgraded to VS 2015 or VS 2017 but
we have two problems:
1 - Windows pre-built thirdparty components should be rebuilt with new
version too (VS 2015 or VS 2017). The only one person who can do this (as
far as I know) is Rom. Also he is probably the only one who have the
complete sources of those components. I can do this job (update third-party
sources to newer versions and build with the needed version of VS (I have
VS 2013, VS 2015, VS 2017 installed) but we need to decide where we can
store these binaries (existing git repo is not good because it is too big
now, some ftp or public cloud will be probably better).
2 - I tried to build BOINC using VS 2015 and got several compilation
errors. I can handle them but just let you know that just upgrade will lead
to broken build.

Thanks

Best regards,
Vitalii Koshura

2017-08-02 5:16 GMT+03:00 Charlie Fenton <charl...@ssl.berkeley.edu>:

> I almost forget: I believe that the translations need to be updated in the
> 7.8 branch before tagging 7.8.1.
>
> @Christian: Can you take care of this? I believe you have been working on
> the Transifex stuff.
>
> Cheers,
> --Charlie
>
> On Aug 1, 2017, at 7:11 PM, Charlie Fenton <charl...@ssl.berkeley.edu>
> wrote:
> > I just merged my July 21 fix for the Windows 10 Manager crashes into the
> client_release/7/7.8 branch. If we want to get a new public version
> released, we need to keep moving alpha testing forward.
> >
> > Are there any other changes in GIT master that should be ported into the
> 7.8 branch before we tag and build BOINC 7.8.1 and release it for alpha
> testing? (The way Rom and I have always ported individual commits is to
> cherry pick from master into the 7.8 branch.)
> >
> > Should the new keyword stuff be included in the 7.8.1 builds? If so, it
> is important that the Windows projects be updated for all supported
> versions of Visual Studio and ported to the 7.8 branch before tagging
> 7.8.1, as well as my commits 039fd90 (7/16/17) and 11b6ccc (7/31/17). Is
> anyone other than me still using VS 2010 for local Windows builds?
> >
> > Opinions? Thoughts? Volunteers to do the porting and tagging?
> >
> > Cheers,
> > --Charlie
> >
>
> _______________________________________________
> boinc_dev mailing list
> boinc_dev@ssl.berkeley.edu
> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to