Yeah, I would really like to move our Windows CI to Travis.
Setting up the appveyor took me many days of tinkering. The dependencies were
the hardest part, mostly because not being a Windows person, I have only the
vaguest notion of nuget, chocolatey, and such things. It would be so much
easier if somebody who actually was a Windows programmer wanted to lend a hand.
Also would make it easier if Travis had its windows VM images start out with
all vcproj packages built so we could select them and have almost all the deps
we need ready to go without building them ourselves.
-- lg
> On Dec 4, 2018, at 11:17 PM, Solomon Boulos <[email protected]> wrote:
>
> Travis recently added Windows support, now that they moved this part to GCE:
>
>
> https://blog.travis-ci.com/2018-10-11-windows-early-release
> <https://blog.travis-ci.com/2018-10-11-windows-early-release>
>
> So you could always figure out how to do this by booting up a Windows Server
> 2016 box on GCE with RDP and go from there. Then you’d finally be down to
> just one CI system!
>
> On Tue, Dec 4, 2018 at 22:49 Chris Foster <[email protected]
> <mailto:[email protected]>> wrote:
> As a further concrete example of how this can be done (including
> packaging and uploading build artifacts to S3 for each master build)
> here's the appveyor config for a project of mine:
>
> https://github.com/c42f/displaz/blob/master/appveyor.yml
> <https://github.com/c42f/displaz/blob/master/appveyor.yml>
>
>
> On Wed, Dec 5, 2018 at 9:59 AM Marco Meyer <[email protected]
> <mailto:[email protected]>> wrote:
> >
> > As a suggestion: since you have appveyor set up already you could deploy
> > its build artifacts to github releases. I am using something similar on my
> > bitbucket (pipelines) and it works like a charm for me.
> >
> > https://www.appveyor.com/docs/packaging-artifacts/
> > <https://www.appveyor.com/docs/packaging-artifacts/>
> > https://www.appveyor.com/docs/deployment/github/
> > <https://www.appveyor.com/docs/deployment/github/>
> >
> > Not volunteering thou... I'm neither an expert on appveyor nor a windows
> > guy :) just thought I'd throw that in.
> >
> >
> > -----Original Message-----
> > From: Larry Gritz <[email protected] <mailto:[email protected]>>
> > Reply-to: OpenImageIO developers <[email protected]
> > <mailto:[email protected]>>
> > To: OpenImageIO developers <[email protected]
> > <mailto:[email protected]>>
> > Subject: Re: [Oiio-dev] oiiotool --add troubles
> > Date: Tue, 4 Dec 2018 14:19:30 -0800
> >
> > Sorry, I know that's a big hole for us.
> >
> >
> > It's not even the "hassle", it's truly that I don't have easy access to
> > Windows (nor expertise on it). I would *love* a volunteer who can figure
> > out a good path for us to produce Windows binaries for major releases and
> > store them somewhere (not just once, but taking it on as an ongoing task,
> > or find a way to automate it).
> >
> >
> >
> >
> > On Dec 4, 2018, at 1:52 PM, Sebastian Schoellhammer
> > <[email protected] <mailto:[email protected]>>
> > wrote:
> >
> >
> > Hi Larry,
> >
> >
> > thanks for the swift response - I feel slightly less silly!
> >
> > I did grab whatever windows binary I could get my hands on, as I didn't
> > have Visual Studio to build it.
> >
> > That's the result :-)
> >
> >
> > It would be awesome if there were binaries coming with the source releases
> > but I understand that it's a hassle!
> >
> >
> > Thanks again,
> >
> > seb
> >
> >
> >
> >
> > --
> >
> > Larry Gritz
> >
> > [email protected] <mailto:[email protected]>
> >
> >
> >
> >
> >
> > _______________________________________________
> >
> > Oiio-dev mailing list
> >
> > [email protected] <mailto:[email protected]>
> >
> > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
> > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
> >
> > _______________________________________________
> > Oiio-dev mailing list
> > [email protected] <mailto:[email protected]>
> > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
> > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
> _______________________________________________
> Oiio-dev mailing list
> [email protected] <mailto:[email protected]>
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
> <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
