Re: [CMake] Getting Location of This File

On Fri, Jul 24, 2015 at 9:30 PM, Daniel Dilts wrote: > Yes, ${CMAKE_CURRENT_SOURCE_DIR} has the path to the CMakeLists.txt file > that has the include() command. Is there a variable with the path of the > file referenced by the include() command? > Could define such a variable before the include

Re: [CMake] Getting Location of This File

Yes, ${CMAKE_CURRENT_SOURCE_DIR} has the path to the CMakeLists.txt file that has the include() command. Is there a variable with the path of the file referenced by the include() command? On Fri, Jul 24, 2015 at 7:40 PM, J Decker wrote: > ${CMAKE_SOURCE_DIR} - path of the root cmake file calle

[CMake] Using cmake on the MSYS2 platform(s)

Recently, I have found two useful resources () and ) giving advice on how to use cmake with MSYS2 and its collection of packages compiled with either the the mingw-w64-i68

Re: [CMake] Getting Location of This File

${CMAKE_SOURCE_DIR} - path of the root cmake file called ${CMAKE_CURRENT_SOURCE_DIR} - path of the current cmakelists On Fri, Jul 24, 2015 at 3:02 PM, Daniel Dilts wrote: > I have a set of CMake commands that I want to place in a single file and > have other projects use it. The commands in th

[CMake] Getting Location of This File

I have a set of CMake commands that I want to place in a single file and have other projects use it. The commands in the file must affect the scope that references it, so the declared functions, include_directories, etc. must affect things in the scope that includes it. I attempted to place these

Re: [CMake] Rerun CMake partially in Visual Studio

On 7/24/2015 3:01 AM, Nagy-Egri Máté Ferenc via CMake wrote: May I ask what you mean by ‘editors’? Do you mean GUI editors to managing CMake projects? Máté Yes, things like QtCreator. Or future IDEs that might use CMake as a build system. -Bill -- Powered by www.kitware.com Please keep m

[CMake] Running a program post-build

Hello. This is my first time using cmake. How do I get a program that is built to run in 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

[CMake] Is add_definitions() still recommended?

Starting with CMake 3.1, and going forward, is add_definitions() still recommended if you have preprocessor definitions you want included in all projects? The evolution of CMake appears to discourage setting global state in favor of relying more on target properties (for includes, definitions, and

Re: [CMake] using ctest launchers leads to empty warning/error messages on the dashboard

On 07/24/2015 10:23 AM, Matthias Kretz wrote: set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON") Is that in your ctest -S script? Do you also have set(CTEST_USE_LAUNCHERS ON) in the same script? Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://

Re: [CMake] using ctest launchers leads to empty warning/error messages on the dashboard

On Friday 24 July 2015 10:23:48 Matthias Kretz wrote: > set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON") > > I don't get any output on the CDash dashboard anymore. AFAICT the Build > directory in Testing/tag/ is removed but never recreated. I.e. if I call Maybe the better lead: I made the UseLauncher

Re: [CMake] using ctest launchers leads to empty warning/error messages on the dashboard

OK, this patch is bogus. Because cmCTestBuildHandler::LaunchHelper::LaunchHelper should call MakeDirectory already if this->Handler->UseCTestLaunch is true. Makes my test results even more strange then. On Friday 24 July 2015 11:28:13 Matthias Kretz wrote: > On Friday 24 July 2015 10:23:48 Matt

Re: [CMake] using ctest launchers leads to empty warning/error messages on the dashboard

On Friday 24 July 2015 10:23:48 Matthias Kretz wrote: > set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON") > > I don't get any output on the CDash dashboard anymore. AFAICT the Build > directory in Testing/tag/ is removed but never recreated. With the following patch I get output back to the dashboard:

[CMake] using ctest launchers leads to empty warning/error messages on the dashboard

Hi, using set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON") I don't get any output on the CDash dashboard anymore. AFAICT the Build directory in Testing/tag/ is removed but never recreated. I.e. if I call CTEST_LAUNCH_LOGS=./not-existing-directory make the launcher output is not stored to disk.

Re: [CMake] Rerun CMake partially in Visual Studio

May I ask what you mean by ‘editors’? Do you mean GUI editors to managing CMake projects? Máté Feladó: Bill Hoffman Elküldve: ‎csütörtök‎, ‎2015‎. ‎július‎ ‎23‎. ‎16‎:‎38 Címzett: cmake@cmake.org On 7/23/2015 8:45 AM, David Cole via CMake wrote: > Nope. > > CMake has no way of knowing