Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with jpeg dependency on Windows #2

Closed
hadim opened this issue Aug 30, 2016 · 18 comments
Closed

Issue with jpeg dependency on Windows #2

hadim opened this issue Aug 30, 2016 · 18 comments

Comments

@hadim
Copy link
Member

hadim commented Aug 30, 2016

The qt version that conda provides (even with conda-forge enabled) depends on jpeg-8d. This dependency prevents me to install the new opencv 3.1.0 (see conda-forge/opencv-feedstock#27).

The repo seems to update the jpeg dep to 9. See https://github.com/conda-forge/qt-feedstock/blob/master/recipe/meta.yaml#L55

How can I access to the build of this repo ? I can't find them with conda search qt --channel conda-forge

@jakirkham
Copy link
Member

This is only built on Linux. There are no Windows or OS X builds. On the OS X side, the blocker is CI limitations. Not sure what the Window blocker is (possibly also CI limitations).

@hadim
Copy link
Member Author

hadim commented Aug 30, 2016

Ok.

@ccordoba12
Copy link
Contributor

We could try to build this for Windows, but I don't have time to do it right now :-)

@ccordoba12 ccordoba12 changed the title Issue with jpeg dependency Issue with jpeg dependency on Windows Aug 30, 2016
@patricksnape
Copy link

@ccordoba12 Do we have a working recipe for QT somewhere? In my experience the Appveyor guys are pretty responsive/happy to increase builder capabilities for open source package builds.

@ccordoba12
Copy link
Contributor

It's here in the repo :-)

@patricksnape
Copy link

😊 Whoops! OK just need a PR that kicks off a build that we can refer to (which will presumably fail due to timeouts).

@ocefpaf
Copy link
Member

ocefpaf commented Sep 3, 2016

@patricksnape and @ccordoba12 if we can get a working recipe we should discuss the possibility to build it outside AppVeyor. Maybe we should put together a vagrant config for this first.

I am a zero on Windows and vagrant so I won't be able to help much there...

@patricksnape
Copy link

@ocefpaf Build it where? How would we even know it works?

@ocefpaf
Copy link
Member

ocefpaf commented Sep 3, 2016

@ocefpaf Build it where?

There are many people willing to donate hardware for this. We need only to find a way to ensure the vagrant config is compatible.

How would we even know it works?

By testing!

@patricksnape
Copy link

I understand that someone would run it but the question is how they demonstrate that it actually works. That sounds like an extremely ambitious sub-project to me - since by the time we'd got it working I imagine we'd nearly have our own version of Appveyor... Especially if we want that hardware to get kicked off by PRs!

@ocefpaf
Copy link
Member

ocefpaf commented Sep 3, 2016

That sounds like an extremely ambitious sub-project to m

It is.

since by the time we'd got it working I imagine we'd nearly have our own version of Appveyor...

Indeed.

Especially if we want that hardware to get kicked off by PRs!

That would be the dream 😄

The thing is. we are already at the limit with AppVeyor. If anyone wants to try asking for more please go ahead. But we already contact them more than once and got all the resources they could offer already.

@patricksnape
Copy link

Ah well then this seems more like we should just be setting up some general system for Windows/vagrant builds (essentially building our own CI) and achieving that before using QT as our guinea pig?

@ocefpaf
Copy link
Member

ocefpaf commented Sep 3, 2016

Ah well then this seems more like we should just be setting up some general system for Windows/vagrant builds (essentially building our own CI) and achieving that before using QT as our guinea pig?

Why? Qt's issues on Windows makes it the perfect guinea pig for testing this and, if successful, be used in other long builds. Either way please add your opinions to the meeting agenda: https://conda-forge.hackpad.com/conda-forge-meetings-2YkV96cvxPG

We already have a few topics on long builds and I am very interested you hearing more from you.

PS: If you want to attend the next meeting, and I encourage you to, please also answer the doodle regarding the time of the meeting.

@patricksnape
Copy link

I can do the 9th - I filled in the doodle.

@ocefpaf
Copy link
Member

ocefpaf commented Sep 3, 2016

I can do the 9th - I filled in the doodle.

Awesome! Thanks!!

Note that google hangout has a 10 people limit but do not go away if we reach that limit the time you try to connect. I will gladly switch places with you in the meeting so you can participate. We need more Windows voices there!

@msarahan
Copy link
Member

msarahan commented Sep 3, 2016

This is already in the works on the Continuum side. Some mix of Gitlab CI driving vagrant/docker/virtualbox. I created this issue as a rallying point: conda-archive/build_infrastructure#1

The point will be less to create a general appveyor/travis/circle replacement, and more to provide a way to build our specific desires, and have a way for everyone to contribute build server time, since that is much more straightforward than financial arrangements.

@msarahan
Copy link
Member

msarahan commented Sep 3, 2016

Also, if we anticipate more than 10 people, we can try WebEx, or perhaps bluejeans.

@ocefpaf
Copy link
Member

ocefpaf commented Dec 13, 2016

This should be fixed now. Thanks to all for the support and help solving this.

Next step... Qt 5 😄

@ocefpaf ocefpaf closed this as completed Dec 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants