-
Notifications
You must be signed in to change notification settings - Fork 70
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
Add CMake build for C++ and scikit-build infrastructure for Python package installation #514
Conversation
…th from legate_core target
…re package's config
… instead of cloning
…erent from last time we built
for more information, see https://pre-commit.ci
…net_dir and --conduit flags in case cunumeric builds legate_core instead of finding it
@trxcllnt Are the recent changes in CI responsible for the test failure, or is it something else? |
@marcinz do we need to rebuild the CI images after merging that PR earlier? |
So the problem is that we need the modified Github workflow from the conda build PRs. |
install.py
Outdated
if exists(join(legate_dir, "lib", "cmake", "legate_core")): | ||
cmake_flags += ["-Dlegate_core_ROOT=%s" % legate_dir] | ||
elif exists(join(legate_dir, "legate_core-config.cmake")): | ||
if exists(join(legate_dir, "legate_core-config.cmake")): |
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.
I think just
if legate_dir:
cmake_flags += ["-Dlegate_core_ROOT=%s" % legate_dir]
We'll find out if we did it right once we see how CI works post-merge :-P
Clone of #311 with special branch name so CI will test the legate.core and cunumeric PR's together.