Re: [CMake] Recursively include target include directories only

On Thu, Jun 18, 2015 at 4:24 PM, Dan Liew wrote: > Hi, > > On 18 June 2015 at 12:16, Robert Dailey wrote: >> On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew wrote: Can you explain what you mean by "strong" and "weak" symbols? >>> >>> >>> Google is your friend >>> >>> https://en.wikipedia.org/wik

Re: [CMake] Recursively include target include directories only

Hi, On 18 June 2015 at 12:16, Robert Dailey wrote: > On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew wrote: >>> Can you explain what you mean by "strong" and "weak" symbols? >> >> >> Google is your friend >> >> https://en.wikipedia.org/wiki/Weak_symbol >> >> http://stackoverflow.com/questions/2290587

Re: [CMake] Support for Concurrent Fortran 77 Compiler

On 06/18/2015 04:01 PM, Ette, Anthony (CDS) wrote: > rts1-4:/home/bzpl46/test2> cmake -G "Unix Makefiles" > -- The Fortran compiler identification is CCur > -- Check for working Fortran compiler: /usr/ccs/bin/cf77 > -- Check for working Fortran compiler: /usr/ccs/bin/cf77 -- works Great! Thanks

Re: [CMake] Support for Concurrent Fortran 77 Compiler (was: fortran compiler failed to compile simple test program)

> Please try building CMake from commit 7cd539b1 to see if it detects the > compiler id as "CCur". Once that works we can look at updating the flags > used for the compiler. Looks like this patch (which includes the commit to remove -rdynamic from GNU fortran compilers - f43defaec4e8610e90886a

Re: [CMake] Running CTest with Xcode build results in Error

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

Re: [CMake] Running CTest with Xcode build results in Error

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

Re: [CMake] Running CTest with Xcode build results in Error

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

Re: [CMake] Running CTest with Xcode build results in Error

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

Re: [CMake] Recursively include target include directories only

Did you read through the pointed to stack overflow question and answers? Is the information there misleading or incorrect?, ... because it seems to say there is a way to do it with MSVC... On Thu, Jun 18, 2015 at 3:16 PM, Robert Dailey wrote: > On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew w

Re: [CMake] Running CTest with Xcode build results in Error

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

Re: [CMake] Recursively include target include directories only

On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew wrote: >> Can you explain what you mean by "strong" and "weak" symbols? > > > Google is your friend > > https://en.wikipedia.org/wiki/Weak_symbol > > http://stackoverflow.com/questions/2290587/gcc-style-weak-linking-in-visual-studio Normally Google is my

Re: [CMake] Running CTest with Xcode build results in Error

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/

[CMake] Unable to set configuration name with a hyphen char

Hi. I try to set a custom configurations like "Debug-Demo" and "Release-Demo". I had used a snippet from wiki: http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_specify_my_own_configurations_.28for_generators_that_allow_it.29_.3F with additional modifying DEBUG_CONFIGURATIONS, because the "Debug-Demo

Re: [CMake] Recursively include target include directories only

> Can you explain what you mean by "strong" and "weak" symbols? Google is your friend https://en.wikipedia.org/wiki/Weak_symbol http://stackoverflow.com/questions/2290587/gcc-style-weak-linking-in-visual-studio -- Powered by www.kitware.com Please keep messages on-topic and check the CMake F

Re: [CMake] Support for Concurrent Fortran 77 Compiler (was: fortran compiler failed to compile simple test program)

On 06/18/2015 08:44 AM, Brad King wrote: > We may be able to extract that while compiling the compiler identification > source file. Try modifying Modules/CMakeDetermineFortranCompiler.cmake > and extending the list in CMAKE_Fortran_COMPILER_ID_TEST_FLAGS with "-v". > Then run CMake on the tiny CM

Re: [CMake] Running CTest with Xcode build results in Error

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

Re: [CMake] Recursively include target include directories only

On Thu, Jun 18, 2015 at 1:57 AM, Dan Liew wrote: >> The reason I'm asking this question is because of how I handle unit >> tests in CMake right now. Instead of just defining an executable >> target for the test and then adding a link dependency on the library >> containing the class or set of clas

Re: [CMake] Running CTest with Xcode build results in Error

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

[CMake] Running CTest with Xcode build results in Error

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

Re: [CMake] fortran compiler failed to compile simple test program

On 06/17/2015 11:07 AM, Ette, Anthony (CDS) wrote: > Please see the response below about uniquely identifying cf77. > > In order to identify the compiler as cf77, do something akin to the following: > $ echo ' PROGRAM V' > /tmp/nil.f > $ echo ' END' >> /tmp/nil.f > $ cf77 -v -o /dev/null

Re: [CMake] alternative method for setting CMAKE_TOOLCHAIN_FILE?

> Is there an alternative method for setting the CMAKE_TOOLCHAIN_FILE variable > other than, for example: > > cmake -D CMAKE_TOOLCHAIN_FILE=... > > Perhaps an environment variable or something similar? You always have the option to set an environment variable and then read it at the top of your

[CMake] alternative method for setting CMAKE_TOOLCHAIN_FILE?

Hello, Is there an alternative method for setting the CMAKE_TOOLCHAIN_FILE variable other than, for example: cmake -D CMAKE_TOOLCHAIN_FILE=... Perhaps an environment variable or something similar? Thanks, Justin -- Powered by www.kitware.com Please keep messages on-topic and check the CMa