-
Notifications
You must be signed in to change notification settings - Fork 407
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
CMake namespaces (and other modern cmake cleanup) #1924
Labels
Feature Request
Create new capability; will potentially require voting
Projects
Comments
Related to #674 |
jjwilke
changed the title
CMake namespaces
CMake namespaces (and other modern cmake cleanup)
Dec 6, 2018
Separate libs builds did not work
was the only thing set, leading to a bunch of undefined references on kokkos containers |
jjwilke
pushed a commit
to jjwilke/kokkos
that referenced
this issue
Dec 6, 2018
jjwilke
pushed a commit
to jjwilke/kokkos
that referenced
this issue
Dec 7, 2018
jjwilke
pushed a commit
to jjwilke/kokkos
that referenced
this issue
Dec 14, 2018
jjwilke
pushed a commit
to jjwilke/kokkos
that referenced
this issue
Dec 17, 2018
ndellingwood
added
the
Feature Request
Create new capability; will potentially require voting
label
Feb 1, 2019
6 tasks
@jjwilke Is that still an issue? |
Not still an issue. Separate libs and single lib should still be working. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Best practice (AFAIK) is to namespace targets so that CMake knows the name is intended to be a CMake target, generating getter error messages:
This seems easy enough to add - but I suppose could break a lot of code that expect the target
kokkos
with no namespace. Is it worth exporting both the current un-namspaced target for (compatibility) and a namespaced-target (for good practice)?The text was updated successfully, but these errors were encountered: