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

Allow specifying custom profiles #44

Merged
merged 6 commits into from
May 13, 2023
Merged

Conversation

afnanenayet
Copy link
Contributor

Allow for users to specify a specific profile. I have a ci-specific profile, so it would be useful to be able to set a different profile in the action config.

Allow for users to specify a specific profile.
@taiki-e
Copy link
Owner

taiki-e commented May 9, 2023

Thanks for the PR!

The --profile option affect the directory from which the built binaries are output, so you have to adjust /release below.

target_dir="${target_dir}/release"

aarch64_target_dir="${target_dir}/aarch64-apple-darwin/release"
x86_64_target_dir="${target_dir}/x86_64-apple-darwin/release"

target_dir="${target_dir}/${target}/release"

See this code in cargo-llvm-cov for the directory name used.

The `release` profile was hardcoded and will fail if we change the
profile.
@afnanenayet
Copy link
Contributor Author

Good catch, thanks

main.sh Outdated Show resolved Hide resolved
Set the default profile env var to "release" if it's not supplied.
Address feedback about handling special Cargo profiles.
main.sh Outdated Show resolved Hide resolved
Use the profile name provided by the user, always. We separate out a new
variable for the profile directory name for clarity, and so we use the
correct profile as requested by the user.
main.sh Outdated Show resolved Hide resolved
We were not supposed to change the name of the field we're pulling.
Copy link
Owner

@taiki-e taiki-e left a comment

Choose a reason for hiding this comment

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

Thanks!

@taiki-e taiki-e merged commit 1589187 into taiki-e:main May 13, 2023
@taiki-e
Copy link
Owner

taiki-e commented May 13, 2023

Published in 1.14.0.

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