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/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]>
Reply-to: OpenImageIO developers <[email protected]>
To: OpenImageIO developers <[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]> 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 [email protected]
_______________________________________________Oiio-dev mailing
[email protected]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
