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

CMake namespaces (and other modern cmake cleanup) #1924

Closed
jjwilke opened this issue Dec 4, 2018 · 5 comments
Closed

CMake namespaces (and other modern cmake cleanup) #1924

jjwilke opened this issue Dec 4, 2018 · 5 comments
Assignees
Labels
Feature Request Create new capability; will potentially require voting

Comments

@jjwilke
Copy link

jjwilke commented Dec 4, 2018

Best practice (AFAIK) is to namespace targets so that CMake knows the name is intended to be a CMake target, generating getter error messages:

target_link_libraries(mylib Kokkos::kokkos)

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)?

@jjwilke
Copy link
Author

jjwilke commented Dec 4, 2018

Related to #674

@jjwilke jjwilke changed the title CMake namespaces CMake namespaces (and other modern cmake cleanup) Dec 6, 2018
@jjwilke
Copy link
Author

jjwilke commented Dec 6, 2018

Separate libs builds did not work

LINK_TARGETS=kokkoscore

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 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 ndellingwood added the Feature Request Create new capability; will potentially require voting label Feb 1, 2019
@Char-Aznable
Copy link
Contributor

@jjwilke Is your branch cmake-1924 supposed to tackle the issue mentioned here and those in #674? If so, can you give a big picture of how it works?

@ndellingwood ndellingwood added this to the 2019 April milestone Feb 7, 2019
@crtrott crtrott removed this from the 2019 April milestone Aug 21, 2019
@jjwilke jjwilke added this to the 3.0 Release milestone Sep 4, 2019
@masterleinad masterleinad added this to To do in Milestone: Release 3.0 via automation Oct 3, 2019
@dalg24
Copy link
Member

dalg24 commented Oct 7, 2019

Separate libs builds did not work

@jjwilke Is that still an issue?

@jjwilke
Copy link
Author

jjwilke commented Oct 7, 2019

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
Labels
Feature Request Create new capability; will potentially require voting
Projects
No open projects
Development

No branches or pull requests

6 participants