-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
FIX: Patch PyQt's configure.py to always assume a shared python. #45
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin please rerender |
…nda-forge-pinning 2019.01.29
|
||
language: generic | ||
|
||
os: osx | ||
osx_image: xcode6.4 | ||
osx_image: xcode9.4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Last time we discovered this was the problem, i.e. we need xcode6.4
here for PyQt to compile correctly. So please revert this change and try again (it seems that image is still available).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it.. This was changed by the re-render
command. Should the instructions be updated to reflect this issue as well?
To fix the failures on Azure/Linux, please add this file https://github.com/conda-forge/qtawesome-feedstock/blob/master/recipe/yum_requirements.txt to the recipe dir. I don't know about the failures on Azure/macOS. You'll have to fix those by yourself. |
@conda-forge-admin please rerender |
…nda-forge-pinning 2019.01.29
@ccordoba12 I did some quick investigation and the support for yum_requirements.txt was added 3 days ago to conda-smithy (conda-forge/conda-smithy@1826839) and there is not yet a version released. |
@conda-forge-admin please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to re-render for you, but it looks like there was nothing to do. |
(I rebuilt the bot) |
…nda-forge-pinning 2019.01.29
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
So both Travis and Azure fail with the same problem, and I don't know how to fix it. @conda-forge/core, have you seen this problem before? |
@ccordoba12 would this be the case of the xcode version? |
No, before the compilation completely failed due to that xcode versión. Now it only fails with QtTest. |
@hhslepicka, ok, I was wrong: changing back to xcode 6.4 do really fix things in Travis. Azure is broken because it uses a more recent xcode version, I'd say. @conda-forge/core, what do you think we should do about this? |
@ccordoba12, no problem at all... i was just testing it to make sure! |
@ccordoba12 and @conda-forge/core any news here? |
Travis will get broken in a rerender as well. It's using 10.10 sdk (although CONDA_BUILD_SYSROOT is set to 10.9), but with the latest it will use 10.14 sdk and break |
@isuruf in this case what would be the recommendation? |
@ccordoba12 could it be the case that
|
@conda-forge-admin, please rerender |
…nda-forge-pinning 2019.03.11
Probably related... Not sure how to address it as it seems to me that after forcing the install of the new SDK we should probably run Any ideas @ccordoba12 and @conda-forge/core |
Folks, |
@hhslepicka - would that break compatibility with other conda-forge packages? |
@scopatz I don't think I would have the answer for your question (maybe other senior members of this recipe will be able to) but AFAIK, the current available package was not done with Xcode 9.4. |
You are risking a lot by not using the same libc++. Strongly recommend not to do that. The thing I dont get is why so much time is being spent on qt 5.6 when there's been two lts releases since then. Can anyone explain that? |
@mingwandroid I would love to use a newer version if available as long as the new version includes the plugins properly (Qt Designer and other pieces). |
If pieces are missing that's a bug. Qt 5.6 on the other hand is full of bugs, missing features and known security issues. Hence 5.9 then 5.12. |
@mingwandroid that is exactly the bug that I am trying to fix here. I'm fighting the missing designer plugin bug for a while (AnacondaRecipes#1)
A fix to my previous statements: I saw it wrong... the package from |
Glad your issue is fixed. I'm more likely to spend time on Qt 5.12 than ensuring the designer plugin is bundled with Anaconda Distribution's Qt 5.6 (no chance) or Qt 5.9 (some chance) packages. I will try to make sure the plugin is correctly packaged though at that time. No new software is compiled using Xcode on Anaconda Defaults nor on conda-forge. Historically yes, but we didn't keep track of that very well. We use our own compilers now and compile everything with them specifically because compiler runtimes from Apple tend not to be compatible with custom compilers which we need for openmp support. And building from source is good too! |
Ray, I think no one wants to put the time and energy needed to compile new Qt versions, including me. I can't speak for the other contributors but in my case a) I have a lot of work with Spyder itself to become the Qt maintainer here; and b) there's no gain in helping conda-forge to compile Qt when Anaconda provides quite good Qt packages thanks to you. How do you think we could improve the situation for conda-forge? |
Not really fixed... i thought it was but I was looking at the wrong place. |
I will close this PR as there is no clear path forward. |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering) (thanks @CJ-Wright )Solves #44.
This is an attempt to fix issue #44 in which Python now being a static binary makes the
configure.py
script at PyQt to fail to locate the Python shared library which is always packaged even with the static python.Attn. @conda-forge/pyqt