Skip to content
This repository was archived by the owner on Sep 13, 2021. It is now read-only.

Conversation

@fredrikaverpil
Copy link
Owner

Here are the deps used in the official repo's appveyor.yml: https://github.com/OpenImageIO/oiio/blob/master/appveyor.yml#L52

@fredrikaverpil
Copy link
Owner Author

fredrikaverpil commented Jan 28, 2019

@SidneyGuenther do you think we should add these too?

I see he also builds qt5-base, which will make the build take a lot longer.

@SidneyGuenther
Copy link
Collaborator

SidneyGuenther commented Jan 28, 2019

@SidneyGuenther do you think we should add these too?

I think we could try to add them but if they're adding more problems and build errors we should wait until somebody requests a feature of oiio which requires one of these dependencies.

I see he also builds qt5-base, which will make the build take a lot longer.

This we should definitely just add if somebody requests it I guess.

@fredrikaverpil
Copy link
Owner Author

fredrikaverpil commented Jan 28, 2019

Okay, sounds good. I will wait with merging this just a bit, giving us a chance to debug Python 3.7 first.

So, a blocker: #7

@fredrikaverpil fredrikaverpil added the enhancement New feature or request label Jan 28, 2019
@fredrikaverpil
Copy link
Owner Author

Okay, resuming this one. Although I think we should leave this unmerged until we have Linux builds too... so we can see what issues might come from these additions.

@fredrikaverpil fredrikaverpil changed the title Add dependencies as seen in oiio appveyor.yml WIP: Add dependencies as seen in oiio appveyor.yml Jan 29, 2019
@fredrikaverpil
Copy link
Owner Author

The redundant dependencies already stated in the CONTROL files have been removed. I am now only adding whatever was specified in the official oiio repo's .appveyor.yml now.

@fredrikaverpil
Copy link
Owner Author

@SidneyGuenther sigh, seems like there is some issues when adding these extras on Ubuntu ...of course!

@fredrikaverpil
Copy link
Owner Author

Oops, my mistake!

@fredrikaverpil
Copy link
Owner Author

@SidneyGuenther What say you?
Should we merge this?

I think so, unless you feel this somehow can be a burden maintainability wise.

* Enable GitHub release

* Add GitHub release notes

* Improve GitHub release naming

* Use better wheel names

* Remove date from wheel

* Only publish release for master branch

* Use + as separator

* Use + as separator

* Use + as separator
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants