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 I'd suspect committers of that file in your source tree. Glad you found it -- stuff like that is frustrating. D On Thu, Jun 18, 2015 at 3:46 PM, Michael Jackson <mike.jack...@bluequartz.net> wrote: > 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 <mike.jack...@bluequartz.net> > wrote: > >> 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 Dart and the Cdash dashboard >> ## ENABLE_TESTING() >> ## INCLUDE(CTest) >> set(CTEST_PROJECT_NAME "DREAM3D") >> set(CTEST_NIGHTLY_START_TIME "01:00:00 UTC") >> >> set(CTEST_DROP_METHOD "http") >> set(CTEST_DROP_SITE "my.cdash.org") >> set(CTEST_DROP_LOCATION "/submit.php?project=DREAM3D") >> set(CTEST_DROP_SITE_CDASH TRUE) >> >> # Use multiple CPU cores to build >> include(ProcessorCount) >> ProcessorCount(N) >> if(NOT N EQUAL 0) >> if(NOT WIN32) >> set(CTEST_BUILD_FLAGS "-j${N}") >> endif(NOT WIN32) >> set(ctest_test_args ${ctest_test_args} PARALLEL_LEVEL ${N}) >> >> endif() >> >> So that explains where it is coming from. Does CMake generate this or does >> my project generate this? >> >> Mike J >> >> On Jun 18, 2015, at 3:40 PM, David Cole <dlrd...@aol.com> wrote: >> >>> 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 >>> <mike.jack...@bluequartz.net> wrote: >>>> 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: >>>> >>>> >>>> >>>> >>>> >>>> Thanks >>>> Mike Jackson >>>> >>>> On Jun 18, 2015, at 3:08 PM, David Cole via CMake <cmake@cmake.org> wrote: >>>> >>>>> 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/CMakeFindEclipseCDT4.cmake:# Try to find out how many CPUs we >>>>> have and set the -j >>>>> Modules/CMakeFindEclipseCDT4.cmake:# Only set -j if we are under UNIX >>>>> and if the make-tool >>>>> Modules/CMakeFindEclipseCDT4.cmake: >>>>> set(_CMAKE_ECLIPSE_INITIAL_MAKE_ARGS "-j${_CMAKE_ECLI >>>>> Modules/CMakeFindEclipseCDT4.cmake:set(CMAKE_ECLIPSE_MAKE_ARGUMENTS >>>>> "${_CMAKE_ECLIPSE_INIT >>>>> Modules/CMakeFindKate.cmake:# Try to find out how many CPUs we have >>>>> and set the -j argumen >>>>> Modules/CMakeFindKate.cmake:# Only set -j if we are under UNIX and if >>>>> the make-tool used a >>>>> Modules/CMakeFindKate.cmake: set(_CMAKE_KATE_INITIAL_MAKE_ARGS >>>>> "-j${_CMAKE_KATE_PROCESSOR >>>>> Modules/CMakeFindKate.cmake:set(CMAKE_KATE_MAKE_ARGUMENTS >>>>> "${_CMAKE_KATE_INITIAL_MAKE_ARGS >>>>> >>>>> And it looks like those try to restrict it to a "make" tool, so they >>>>> shouldn't be using it in the case of xcodebuild... >>>>> >>>>> Mystery. We're missing something. >>>>> >>>>> >>>>> >>>>> On Thu, Jun 18, 2015 at 12:23 PM, Michael Jackson >>>>> <mike.jack...@bluequartz.net> wrote: >>>>>> 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 >>>>>> >>>>>>> On Jun 18, 2015, at 9:56 AM, David Cole <dlrd...@aol.com> wrote: >>>>>>> >>>>>>> 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 evaluation. >>>>>>> >>>>>>> >>>>>>> HTH, >>>>>>> David C. >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 18, 2015 at 8:51 AM, Michael Jackson >>>>>>> <mike.jack...@bluequartz.net> wrote: >>>>>>>> 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 looked through our CTest scripts (Which >>>>>>>> were adapted from VTK’s nightly builds) but I am not seeing anything >>>>>>>> about that flag being explicitly called out. >>>>>>>> >>>>>>>> Could anyone with nightly build experience help us out? >>>>>>>> >>>>>>>> Thanks >>>>>>>> Mike Jackson >>>>>>>> BlueQuartz Software >>>>>>>> -- >>>>>>>> >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Please keep messages on-topic and check the CMake FAQ at: >>>>>>>> http://www.cmake.org/Wiki/CMake_FAQ >>>>>>>> >>>>>>>> Kitware offers various services to support the CMake community. For >>>>>>>> more information on each offering, please visit: >>>>>>>> >>>>>>>> CMake Support: http://cmake.org/cmake/help/support.html >>>>>>>> CMake Consulting: http://cmake.org/cmake/help/consulting.html >>>>>>>> CMake Training Courses: http://cmake.org/cmake/help/training.html >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/cmake >>>>>> >>>>> -- >>>>> >>>>> Powered by www.kitware.com >>>>> >>>>> Please keep messages on-topic and check the CMake FAQ at: >>>>> http://www.cmake.org/Wiki/CMake_FAQ >>>>> >>>>> Kitware offers various services to support the CMake community. For more >>>>> information on each offering, please visit: >>>>> >>>>> CMake Support: http://cmake.org/cmake/help/support.html >>>>> CMake Consulting: http://cmake.org/cmake/help/consulting.html >>>>> CMake Training Courses: http://cmake.org/cmake/help/training.html >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/cmake >>>> >>>> >> > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake