-
Notifications
You must be signed in to change notification settings - Fork 18
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
flexible dependency detection #93
Comments
Sorry for the delay. I think this would work cleanly if gauxc was fetchcontent'ed because then |
Hmm, ok. How do you guys handle your superbuild dependency tree (i.e. how do you ensure that dependencies are seen and propagated throughout the configure)? I'm happy to add something that makes this easier (short of adding psi-specific configure logic) |
Yeah, it looks a little weird in the FetchContent era, but (using libxc as an example) we create a dummy target So, right, I couldn't think of a tidy way to improve your #95 for us. I figured I'd make a I haven't actually tried this, so please lmk if it needs to be tested b/c getting locked into a release and can't be changed easily or something. |
We don't have hard release structure at the moment (though I suppose we should start doing that...), so there's no issues there. I would like to make sure that this works in your build system though, as it would be the main user of any non-FetchContent configure path |
Ok, I think David Poole and I need to look at the Psi4+GauXC buildsys psi4-side together, so we'll add this patch and report back. Will next week work with your timeframe? |
Yep! |
Background: Most Psi4 builds (by devs, users, and packagers) detect pre-built installations of its dependency packages, rather than building them with FetchContent (hereafter FC), including gau2grid (g2g).
FetchContent(... FIND_PACKAGE)
if that'll help.The text was updated successfully, but these errors were encountered: