I suspect that ninja thinks its on a posix system because you compiled
it in cygwin. Try building it in a windows "terminal". I routinely use
cmake and ninja on windows with the msvc toolchain and it works great
but I use msys instead of cygwin.
Hopefully that helps you.
Frank
On 8/3/2015 12
You could argue bug or feature depending on your point of view. (I'd lean
toward bug, as it is rather unexpected...) However, it has been that way
for quite some time, (ever since function was added?), so it may require a
new policy to fix, since some function calls from inside functions may be
acc
Is this a known thing, or a bug (I'm using cmake 3.1.0):
I create this CMakeLists.txt:
cmake_minimum_required(VERSION 3.1.0)
project(ArgTest)
function(FOO one two)
message(STATUS "extra args are ${ARGN}")
message(STATUS "third arg is ${ARGV2}")
endfunction()
function(BAR one)
I compiled Ninja on cygwin from git. That now works fine it seems.
I am trying to compile for msvc. However, when cmake runs, I get:
[1/123] Building CXX object
'libACESclip\CMakeFiles\ACESclip.dir\src\ACESclipWriter.cpp.obj'ninja:
fatal: unknown deps type 'msvc'
$ ninja --version
1.6.0.git
OK, I finally have a build of boost I can rely on which enables me to
try this out for you again.
Using the following source tree, I am able to get a successful build &
test of Safe Numerics, other than a couple of warnings, and it
actually submits to the CDash dashboard, no problem.
Source tree
Hello,
I have a piece of C++ and Fortran software that I'm porting to the CMake
build system. On my TeamCity continuous integration server I observe a
weird behaviour: whenever I modify a CMakeLists.txt in a way that might
mean ZERO_CHECK has something to update, building the ZERO_CHECK hangs
unti
