Can someone who has access to the Windows AutoTester machines please update them to VS2017? It's free.

C++ interop needs modern C++ compilers: https://auto-tester.puremagic.com/pull-history.ghtml?projectid=1&repoid=2&pullid=2346

On Monday, 26 November 2018 at 18:18:37 UTC, Manu wrote:
> Can someone who has access to the Windows AutoTester machines please update them to VS2017? It's free.
>
> C++ interop needs modern C++ compilers: https://auto-tester.puremagic.com/pull-history.ghtml?projectid=1&repoid=2&pullid=2346

Please contact Brad for this, e.g.

https://github.com/braddr/d-tester/issues

On Monday, 26 November 2018 at 18:18:37 UTC, Manu wrote:
> Can someone who has access to the Windows AutoTester machines please update them to VS2017? It's free.
>
> C++ interop needs modern C++ compilers: https://auto-tester.puremagic.com/pull-history.ghtml?projectid=1&repoid=2&pullid=2346

Its probably easier and waaaay faster to update our Appveyor configurations since they have VS2017 images available. Actually looks like we'd need to add one for druntime (& phobos but that can wait) since only dmd has an appveyor.yml at the moment.

On Mon, Nov 26, 2018 at 6:10 PM Nicholas Wilson via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
>
> On Monday, 26 November 2018 at 18:18:37 UTC, Manu wrote:
> > Can someone who has access to the Windows AutoTester machines please update them to VS2017? It's free.
> >
> > C++ interop needs modern C++ compilers: https://auto-tester.puremagic.com/pull-history.ghtml?projectid=1&repoid=2&pullid=2346
>
> Its probably easier and waaaay faster to update our Appveyor configurations since they have VS2017 images available. Actually looks like we'd need to add one for druntime (& phobos but that can wait) since only dmd has an appveyor.yml at the moment.

I have no preference for how this is solved... but my stdcpp work is all blocked on this, so it'd be good if vested interests could decide on a solution.

On Tuesday, 27 November 2018 at 02:12:35 UTC, Manu wrote:
> On Mon, Nov 26, 2018 at 6:10 PM Nicholas Wilson via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
>>
>> On Monday, 26 November 2018 at 18:18:37 UTC, Manu wrote:
>> > Can someone who has access to the Windows AutoTester machines please update them to VS2017? It's free.
>> >
>> > C++ interop needs modern C++ compilers: https://auto-tester.puremagic.com/pull-history.ghtml?projectid=1&repoid=2&pullid=2346
>>
>> Its probably easier and waaaay faster to update our Appveyor configurations since they have VS2017 images available. Actually looks like we'd need to add one for druntime (& phobos but that can wait) since only dmd has an appveyor.yml at the moment.
>
> I have no preference for how this is solved... but my stdcpp work is all blocked on this, so it'd be good if vested interests could decide on a solution.

Then lets go with Appveyor then. It should be pretty easy to copy across  the dmd appveyor.{sh,yml} to druntime, change the VS versions and dependent paths and dyke out anything thats not really necessary (e.g. testing/building phobos). I'd do this ,but I don't have VS2017 and someone else would have to review/merge it.

I wonder what compiler versions the buildkite agents run? Could possibly use those to test linux.

On Tuesday, 27 November 2018 at 04:52:54 UTC, Nicholas Wilson wrote:
> Then lets go with Appveyor then. It should be pretty easy to copy across  the dmd appveyor.{sh,yml} to druntime, change the VS versions and dependent paths and dyke out anything thats not really necessary (e.g. testing/building phobos). I'd do this ,but I don't have VS2017 and someone else would have to review/merge it.

I added druntime to AppVeyor, s.t. appveyor config is all that's needed and AppVeyor should be run as soon as there's an appveyor.yml

However, you might want to use a different account (or pay for more concurrent agents) as AppVeyor can already get quite slow on dmd. Alternatively, we could start migrating the builds to Buildkite Windows agents, but that's a long-term project and requires someone with Windows skills.

> I wonder what compiler versions the buildkite agents run? Could possibly use those to test linux.

e.g.

> gcc --version
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609

(on all agents from Martin)

gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516

(on my agents)

On 2018-11-27 12:06, Seb wrote:

> I added druntime to AppVeyor, s.t. appveyor config is all that's needed and AppVeyor should be run as soon as there's an appveyor.yml
> 
> However, you might want to use a different account (or pay for more concurrent agents) as AppVeyor can already get quite slow on dmd. Alternatively, we could start migrating the builds to Buildkite Windows agents, but that's a long-term project and requires someone with Windows skills.

Not sure if it helps but Travis CI got support for Windows (early release) last month [1].

[1] https://blog.travis-ci.com/2018-10-11-windows-early-release

-- 
/Jacob Carlborg