-
Notifications
You must be signed in to change notification settings - Fork 427
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
support stdlib() jinja function #4999
Conversation
Let's add a test and get this in. |
Test added; I tried to copy an existing test for the compiler-jinja. Could someone trigger the tests please? |
I'm not sure if GHA is having problems or if it's a rights issue, but I cannot inspect any of the failing (or passing) test runs - the logs straight up fail to load (raw logs too). I'll try to have a look again tomorrow. |
Thanks for the fixes, now I can also see the test results. :) |
Cannot inspect the failing test runs, again... 😑 |
Finally was able to inspect the logs, and all the failures are either flaky or unrelated to this PR. Could someone take a look perhaps? 🙃 |
Just saw #5013; presumably we're too late to catch that release-train? 😑 |
@h-vetinari I'm sorry yeah, we're pretty close to the end of the month as is, but I'm sure we'll do a follow-up release! (don't have to wait for 2 months) |
Due to the order in which cbc.yaml is parsed.
Should we add docs in this PR or should it be done in a separate PR? |
It should be the same PR. |
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.
Should we add docs in this PR or should it be done in a separate PR?
It should be the same PR.
Done; I added it to the page describing {{ compiler(<lang>) }}
, directly below. Happy to move it elsewhere if that's not the best place.
In principle, this facility would make it possible to also express the | ||
dependence on separate stdlib implementations (like ``musl`` instead of | ||
``glibc``), or to remove the need to assume that a C++ compiler always needs to | ||
add a run-export on the C++ stdlib -- it could then be left up to packages | ||
themselves whether they need ``{{ compiler('cxx') }}`` or not. |
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.
The paragraph is a bit forward-looking in nature. It's not exactly what we need in the first iteration, but possible future uses that are enabled by it. I don't mind deleting it, but thought I'd add it for completeness.
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.
Gah, this should have said "whether they need {{ stdlib('cxx') }}
or not." of course.
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.
Just was reading the docs for this and saw a something to point out
Could someone trigger the CI workflow here (and ideally: review the PR)? It would be a pity if this missed another cycle. |
Could someone please let us know what is still needed here? |
Gentle ping here :) |
YOLO don't hate me. |
Thanks all! 🙏 |
Description
Checklist - did you ...
news
directory (using the template) for the next release's release notes?Fixes #4981
Continuation of #4996, as requested.
cc @chenghlee, @mbargull, @beckermr