-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Install pkg-config file on Windows #48
Conversation
…nda-forge-pinning 2023.04.10.21.29.25
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 ( |
Pipelines failed on Python @conda-forge-admin, please restart ci |
Fails consistently: same architecture–Python combination. Actually looking at the logs this time: import fails (and runtime paths cannot be set) because modules are not built. Modules are not built because CMake bails out due to version mismatch (3.8.16 interpreter with 3.8.15 libs). As far as I can see, there are no |
I realize there are some gratuitous changes in this PR which could be cleaned up, but is there a more fundamental reason preventing this from being merged? I believe having something like this would make building packages against |
Merged upstream, stevengj/nlopt#534; will wait for next release. |
Checklist
conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)