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

Enable additional arguments in build_common.sh #236

Merged
merged 2 commits into from
Jul 18, 2023
Merged

Conversation

wmaxey
Copy link
Member

@wmaxey wmaxey commented Jul 17, 2023

Description

closes #171

Allows passing options into build_[test].sh scripts.

Might be a little hacky.

Checklist

  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

@wmaxey wmaxey requested review from a team as code owners July 17, 2023 23:26
@wmaxey wmaxey requested review from jarmak-nv, ericniebler and jrhemstad and removed request for a team July 17, 2023 23:26
@wmaxey wmaxey changed the title Enable overriding which NVCC is used in the ci scripts. Enable additional arguments in build_common.sh Jul 17, 2023
@wmaxey
Copy link
Member Author

wmaxey commented Jul 18, 2023

I have tested the extra options locally. The CCCL project is able to configure and build with a custom path to NVCC.

echo "The PARALLEL_LEVEL environment variable controls the amount of build parallelism. Default is the number of cores."
echo "Example: PARALLEL_LEVEL=8 $0 g++-8 14 \"70\" "
echo "Example: $0 clang++-8 17 \"70;75;80-virtual\" "
echo "Possible options: "
echo " -nvcc: path/to/nvcc"
Copy link
Collaborator

Choose a reason for hiding this comment

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

What do you think about making this option more general and calling it --cuda_compiler to enable us to later set up clang-cuda builds?

Copy link
Member Author

Choose a reason for hiding this comment

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

What do you think about making this option more general and calling it --cuda_compiler to enable us to later set up clang-cuda builds?

I didn't do that only because there was some existing NVCC logic that comes later.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yeah, I guess we'll just cross that bridge when we get there.

@jarmak-nv jarmak-nv removed their request for review July 18, 2023 14:54
fi

# Begin processing unsets after option parsing
set -u
Copy link
Collaborator

Choose a reason for hiding this comment

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

Oh, I see.

@wmaxey wmaxey merged commit b3bf3c2 into main Jul 18, 2023
368 checks passed
@miscco miscco deleted the fea/enable_other_nvcc branch March 7, 2024 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[FEA]: Allow selecting NVCC on CI commandline
3 participants