-
Notifications
You must be signed in to change notification settings - Fork 262
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
GPURuntime: Don't add include dir for SuiteSparse_Config to interface #370
Conversation
I'll give it a try -- thanks. |
afe05b7
into
DrTimothyAldenDavis:dev2
Getting closer but still strange. Building the Example package gives strange results, reporting /usr/local/include instead of the actual installation folder.
|
It should report this instead:
|
Sometimes CMake doesn't seem to overwrite some files on installation even if it needs to. Could you please upload the generated |
Here's a zip file with the *.cmake files from SuiteSparse_GPURuntime/build folder: SuiteSparse_GPURuntime_cmake_files.zip This file has the contents of the SuiteSparse/lib/cmake/SuiteSparse_GPURuntime folder, after "make local; make install": The latter has this in the SuiteSparse_GPURuntimeTargets.cmake (below). Note that the dynamic library has a different "set_target_properties" than the static library. I found an extraneous double quote in SuiteSparse_GPURuntime/CMakeLists.txt and removed it (PR cf692d9 ). It had no effect on this. I suppose that the Example package might not need to use find_package for these CUDA libraries anyway. I'll try that and see what happens. |
See fe77284 where I've removed the find_package for CHOLMOD_CUDA and SPQR_CUDA, since the find_package (CHOLMOD) and find_package(SPQR) now finds those libraries themselves. |
Maybe fixed in #371? |
I've already merged #371 and the issue is still there. |
It solved the issue for me locally with Does a |
I will double check when I get back to my computer
|
and when building SPQR:
looks great! |
There is no reason I can see why projects that link to this library would need to add the include directory of SuiteSparse_Config to the preprocessor flags.
This will probably also remove the confusing output in the configuration summary.