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

ci: revert cargo-c pin, set libdir explicitly #436

Merged
merged 2 commits into from
Jun 19, 2024

Conversation

cpu
Copy link
Member

@cpu cpu commented Jun 19, 2024

This undoes (#435) (but leaves the pkg-config --version print).

The root cause of the behaviour change is now better understood and documented upstream in the changelog (lu-zero/cargo-c#380). We take the recommendation documented there and set --libdir explicitly so our CI job can continue to treat Ubuntu/MacOS the same w.r.t PKG_CONFIG_PATH and LD_LIBRARY_PATH.

cpu added 2 commits June 19, 2024 14:24
With cargo-c 0.10.0+ there are per-platform/system heuristics being used
to generate the libdir that best fits the target system. For the
purposes of our CI job we'd prefer to use a consistent/simple directory
structure so that we can set the PKG_CONFIG_PATH and LD_LIBRARY_PATH env
vars consistently across Ubuntu and MacOS.
@cpu cpu self-assigned this Jun 19, 2024
@cpu cpu requested a review from ctz June 19, 2024 18:39
run: make --file=Makefile.pkg-config PREFIX=${PREFIX} install
# NOTE: We set --libdir explicitly to avoid per-system/distro path components
# that will complicate setting PKG_CONFIG_PATH/LD_LIBRARY_PATH.
run: >
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is > vs | load bearing?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, gotta "love" YAML....

> is "folded" style and will collapse \n into , whereas | will keep the \n's. We want the former in this case so the CARGOFLAGS env var and the command are the same line, as opposed to the usage on L52 where we want two separate lines (one for curl and one for unzip).

I always end up ref'ing https://yaml-multiline.info/ for this.

@cpu cpu merged commit a011d49 into rustls:main Jun 19, 2024
25 checks passed
@cpu cpu deleted the cpu-revert-cargo-c-pin branch June 19, 2024 19:07
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

Successfully merging this pull request may close these issues.

2 participants