CMake does not generate it.
You may have received it as a "suggestion" from CDash when you set the
project up, and then you put it in your top level source tree and
forget about it usually.
But I don't think CDash would suggest using -j with "if(NOT WIN32)
logic" (although I could be wrong)... so
And I will follow that up quickly with ".. it was buried down in our project….".
Thanks for the help.
Mike J.
On Jun 18, 2015, at 3:45 PM, Michael Jackson
wrote:
> Found the source. the generated CTestConfig.cmake is the following:
>
>
> ## This file should be placed in the root directory o
Found the source. the generated CTestConfig.cmake is the following:
## This file should be placed in the root directory of your project.
## Then modify the CMakeLists.txt file in the root directory of your
## project to incorporate the testing dashboard.
## # The following are required to uses Da
The error shown in your CDash build error output page could be coming
from something that is built within your project as an
ExternalProject.
Do you have any of those?
Have you grepped your source tree for -j yet?
On Thu, Jun 18, 2015 at 3:17 PM, Michael Jackson
wrote:
> I will have to admit t
I will have to admit that I don't pretend to completely understand the CMake
file that I am using as I started with something from VTK and changed things to
work with our project and setup. I will attach the files to the email. Maybe
you can see something that I am missing:
BuildDREAM3D.sh
De
Are you using Eclipse or Kate?
Did you do a grep -E "\-j" on all of the files included by the script
that drives the build? (And in your source tree?)
The only -j possibilities that look likely in CMake itself are shown
in the git grep results from a CMake checkout:
$ git grep -E "\-j"
Modules/
Nope. Neither one of those are on my environment. I am also running at Root for
this build and I have a clean .bashrc for both accounts. There must be
something in my chest.cmake file that makes CTest think it is running with a
makefile generator.
Should I post my various files?
Mike Jackson
Is there a MAKEFLAGS or CTEST_BUILD_FLAGS in your environment?
Where does the -j16 come from? (CTest should not be injecting that
unless you are telling it to somehow, so it either comes from one of
your scripts, or your environment...)
grep for just "\-j" -- the value 16 may come from a variable
We have a nightly build for our project as reported here
http://my.cdash.org/viewBuildError.php?buildid=781789 which is producing an
error. The short of it is that CTest is using xcodebuild (which is correct) but
is trying to pass the “-j16” style that normal “MakeFiles” would use. I have
looke
