Damn. send the unfinished message, I'll repeat what I had, and type the
rest:
Hej,
A quick glance doesn't show anything out of the ordinary, except that
* I'd prevent any use of `..` in your folder references (by using things
like $ and
$
* I think it is more or less standard practice now to
Hej,
A quick glance doesn't show anything out of the ordinary, except that
* I'd prevent any use of `..` in your folder references (by using things
like $ and
$
* I think it is more or less standard practice now to _not_ use
'include_directories', but instead use target_include_directories()
* you
Some additional info.
Here is my cmakelists.txt for the vector3_scalar module:
PROJECT(vector3_scalar)
SET(CMAKE_MACOSX_RPATH 1)
INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}/../common)
SET(HEADER_FILES ${CMAKE_CURRENT_SOURCE_DIR}/../common/common_structs.h)
SET(SRC_FILES ${CMAKE_CURRENT_SOURC
This could be caused by CUDA generating dependencies and then needing to
load them at the next configure step.
For our automated builds, where we don't rely on dependencies during
development (e.g. build one main target from scratch then throw it away),
we set the CMAKE_SUPPRESS_REGENERATION optio
I am having some trouble with my cmake build. I recently redesigned the
physical layout of my files so that it'll be a bit easier to maintain in
the long run.
I have my project structure setup like this.
MAIN_PROJECT/
project/main.c # this is the executable
resources/...# a folder filled with
