On 2018-02-26 14:19-0500 Michael Jackson wrote:
In our CMake based project I generate a *.cmake file which I call with the
following bit of code:
add_custom_target(DREAM3D_MKDOCS_GENERATION ALL
COMMAND "${CMAKE_COMMAND}" -P "${docsCmakeFile}"
COMMENT "using mkdocs to generate the docume
cmake -P usually do the right thing. Here you ignore the error because you
only message (STATUS ...)
Try adding message (ERROR ...) or message (FATAL_ERROR ...) when
execute_process producer error and tout custom command should faim.
Le 26 févr. 2018 20:19, "Michael Jackson" a
écrit :
> In our
In our CMake based project I generate a *.cmake file which I call with the
following bit of code:
add_custom_target(DREAM3D_MKDOCS_GENERATION ALL
COMMAND "${CMAKE_COMMAND}" -P "${docsCmakeFile}"
COMMENT "using mkdocs to generate the documentation"
)
Inside the generated file is t
On 2/23/2018 10:59 AM, Anthony Zukaitis wrote:
On windows I found an issue with Visual studio where intel fortran was
attempting to preprocess lowercase .f90 files. Intel's documentation
states that it does not preprocess these files. Looking into the cmake
source code I found:
in Modules/P
found:that was because of a project that was not compiling
Le 26/02/2018 à 09:52, Stéphane Ancelot a écrit :
Hi,
I have got a master CMake file that includes subprojects as follow :
add_subdirectory(proj1)
add_subdirectory(proj2)
src+proj1
+proj2
The main problem is that I can ru
Hi,
I have got a master CMake file that includes subprojects as follow :
add_subdirectory(proj1)
add_subdirectory(proj2)
src+proj1
+proj2
The main problem is that I can run make install in each project
directory, but not from the top CMake directory in src dir
how to propagate install
