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

Tribits macro assumes build directory is in top level source directory #654

Closed
bartgol opened this issue Feb 24, 2017 · 3 comments
Closed
Labels
Enhancement Improve existing capability; will potentially require voting
Milestone

Comments

@bartgol
Copy link
Contributor

bartgol commented Feb 24, 2017

At line 511 of cmake/tribits.cmake you can see

ADD_SUBDIRECTORY(${CMAKE_BINARY_DIR}/../${SUBPACKAGE_DIR})

This is assuming that the build directory is a subfolder of the kokkos top level source dir. If it's not the case, cmake does not find ${SUBPACKAGE_DIR} and errors out.

I would replace that line with

ADD_SUBDIRECTORY(${CMAKE_SOURCE_DIR}/${SUBPACKAGE_DIR})

allowing the user to build the library wherever he wants.

Of course, unless I am missing some crucial detail about the tribits working flow...

@crtrott
Copy link
Member

crtrott commented Feb 24, 2017

We can try this. the tribits.cmake is actually just a stubs for real tribits, so it only affects pure cmake builds.

@crtrott
Copy link
Member

crtrott commented Feb 24, 2017

I assign Greg, who has been working on pure cmake related stuff.

@gmackey
Copy link
Contributor

gmackey commented Mar 17, 2017

This issue will be fixed with the new cmake build. The build directory can be wherever the user wants.

@hcedwar hcedwar added the Enhancement Improve existing capability; will potentially require voting label Apr 5, 2017
@hcedwar hcedwar added this to the 2017-April-end milestone Apr 5, 2017
@crtrott crtrott modified the milestones: 2017-April-end, 2017-June-end Apr 26, 2017
@crtrott crtrott closed this as completed May 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Improve existing capability; will potentially require voting
Projects
None yet
Development

No branches or pull requests

4 participants