On 2019-05-24 19:38+0200 Haio Maio wrote:
Manually-specified variables were not used by the project
MY_VAR
when I call
cmake -DMY_VAR= ...
The goal is
if(NOT DEFINED MY_VAR)
...
else()
...
if()
in order to tell cmake over the command line what to do.
How to achieve this ?
This functional
Hi,
The goal that you have is fully supported by CMake. You have just run
into a bug in CMake, and you should report this to
https://gitlab.kitware.com/cmake/cmake/issues .
Basically at a very high level the name out the add_executable target
`callback_generator` is the same as the internal name t
On 13/05/2019 12:03, Bill Somerville wrote:
Hi folks,
I am struggling to understand what the problem is with this:
find_program (GO go)
set (GOPATH "${CMAKE_CURRENT_BINARY_DIR}/go")
file (MAKE_DIRECTORY ${GOPATH})
set (sources ${CMAKE_CURRENT_SOURCE_DIR}/callback_generator.go)
set (build_comm
Manually-specified variables were not used by the project
MY_VAR
when I call
cmake -DMY_VAR= ...
The goal is
if(NOT DEFINED MY_VAR)
...
else()
...
if()
in order to tell cmake over the command line what to do.
How to achieve this ?
--
Powered by www.kitware.com
Please keep messages on-topi
A naive grep tells me the IAR compiler detection sets CMAKE_CXX_LINK_FLAGS
in its compiler detection. Maybe that'd work for you?
On Fri, May 24, 2019 at 3:48 AM Zehner Paul wrote:
> Hello all,
>
> So, I managed to configure my `Fujitsu-CXX.cmake` file to use the Fujitsu
> C++ compiler with MPI
Hello all,
So, I managed to configure my `Fujitsu-CXX.cmake` file to use the Fujitsu C++
compiler with MPI as well. The problem of not detecting headers of the STL
(like `array`) was due to the fact the C++ standard flag was not set correctly.
I am facing another problem though: the linker need
