[CMake] Using Eclipse CDT, CMake resets Eclipse project configuration frequently

Hi, I have created an out-of-source build tree (on Windows), with the installation directory as a subfolder of the build trees. The idea is that the compiled binary requires some DLL's, images, 3D models and configuration files, at a location relative to the executable. If the files are

Re: [CMake] Using Eclipse CDT, CMake resets Eclipse project configuration frequently

On 26. Jan, 2009, at 12:24, Jonatan Bijl wrote: Hi, I have created an out-of-source build tree (on Windows), with the installation directory as a subfolder of the build trees. The idea is that the compiled binary requires some DLL's, images, 3D models and configuration files, at a location

Re: [CMake] Buggy progress reporting

Gopala Krishna wrote: On Mon, Jan 26, 2009 at 2:29 AM, Bill Hoffman bill.hoff...@kitware.com wrote: The progress reporting only supports one make at a time in the build tree. -Bill Is there any documentation somewhere on how the percentage reporting is implemented ? If not it would really

Re: [CMake] Using Eclipse CDT, CMake resets Eclipse project configuration frequently

My personal suggestion would be to use the plain MakeFiles generator and then inside eclipse create a C++ Makefile project. You can then point the project settings at the build directory to find the makefile and also tell eclipse to use make all install as the build command instead of

Re: [CMake] Buggy progress reporting

Bill Hoffman bill.hoff...@kitware.com writes: Gopala Krishna wrote: On Mon, Jan 26, 2009 at 2:29 AM, Bill Hoffman bill.hoff...@kitware.com wrote: The progress reporting only supports one make at a time in the build tree. -Bill Is there any documentation somewhere on how the percentage

[CMake] Build-order in Visual Studio

Hello, is it possible to influence the build-order of MSVC from CMakeLists.txt-files? The top-level CMakeLists.txt looks like this: ADD_SUBDIRECTORY(lib1) ADD_SUBDIRECTORY(lib2) ADD_SUBDIRECTORY(lib3) ADD_SUBDIRECTORY(lib4) ADD_SUBDIRECTORY(prog) prog depends on the libs. lib3 depends on lib1

Re: [CMake] Buggy progress reporting

On 26. Jan, 2009, at 15:05, Jesper Eskilson wrote: Bill Hoffman bill.hoff...@kitware.com writes: Gopala Krishna wrote: On Mon, Jan 26, 2009 at 2:29 AM, Bill Hoffman bill.hoff...@kitware.com wrote: The progress reporting only supports one make at a time in the build tree. -Bill Is

Re: [CMake] Build-order in Visual Studio

Micha, Use *target_link_librarieshttp://www.cmake.org/cmake/help/cmake2.6docs.html#command:target_link_libraries * and *add_dependencieshttp://www.cmake.org/cmake/help/cmake2.6docs.html#command:add_dependencies * to fix project build order. 2009/1/26 Micha Renner micha.ren...@t-online.de

Re: [CMake] Buggy progress reporting

Michael Wild them...@gmail.com writes: On 26. Jan, 2009, at 15:05, Jesper Eskilson wrote: Bill Hoffman bill.hoff...@kitware.com writes: Gopala Krishna wrote: On Mon, Jan 26, 2009 at 2:29 AM, Bill Hoffman bill.hoff...@kitware.com wrote: The progress reporting only supports one make at a

Re: [CMake] Build-order in Visual Studio

Am Montag, den 26.01.2009, 16:22 +0200 schrieb Dmytro Ovdiienko: Micha, Use target_link_libraries and add_dependencies to fix project build order. I think, that this doesn't work in the case here. For target_link_libraries I need a library. If prog is first in build process then there are

[CMake] test executable failing only when run in ctest

I've come across a test on the VXL dashboard that seems to segfault only on some test machines. http://www.cdash.org/CDash/testSummary.php?project=12name=bvxm_test_apm_processorsdate=2009-01-26 One of the failing machines is mine (Mac_OS_X-10.5.6_unix_make). When I run the same test

Re: [CMake] test executable failing only when run in ctest

Matthew Leotta wrote: I've come across a test on the VXL dashboard that seems to segfault only on some test machines. http://www.cdash.org/CDash/testSummary.php?project=12name=bvxm_test_apm_processorsdate=2009-01-26 One of the failing machines is mine (Mac_OS_X-10.5.6_unix_make). When I

[CMake] Will CMP0003 OLD become deprecated?

Hi all, I am currently migrating a project to CMake, and have been linking targets to project libraries using full paths (i.e., embracing the NEW CMP0003 policy of CMake = 2.6). However, my co-workers are reluctant to embrace this because the old CMP0003 policy has not yet yielded incorrect

Re: [CMake] Will CMP0003 OLD become deprecated?

Adolfo Rodríguez wrote: Hi all, I am currently migrating a project to CMake, and have been linking targets to project libraries using full paths (i.e., embracing the NEW CMP0003 policy of CMake = 2.6). However, my co-workers are reluctant to embrace this because the old CMP0003 policy has

Re: [CMake] test executable failing only when run in ctest

Brad, Thanks, but I'm not sure if I completely understand your suggestion. Let me clarify. If I run the test executable ./bvxm_test_all I get no errors and no segfault. I know how to debug this, but there is nothing to debug. If in the same directory I run ctest then the test

Re: [CMake] test executable failing only when run in ctest

Matthew Leotta wrote: Brad, Thanks, but I'm not sure if I completely understand your suggestion. Let me clarify. If I run the test executable ./bvxm_test_all I get no errors and no segfault. I know how to debug this, but there is nothing to debug. If in the same directory I run

Re: [CMake] Will CMP0003 OLD become deprecated?

Adolfo Rodríguez wrote: I am currently migrating a project to CMake, and have been linking targets to project libraries using full paths (i.e., embracing the NEW CMP0003 policy of CMake = 2.6). However, my co-workers are reluctant to embrace this because the old CMP0003 policy has not yet

Re: [CMake] test executable failing only when run in ctest

On Jan 26, 2009, at 3:04 PM, Brad King wrote: Matthew Leotta wrote: Brad, Thanks, but I'm not sure if I completely understand your suggestion. Let me clarify. If I run the test executable ./bvxm_test_all I get no errors and no segfault. I know how to debug this, but there is nothing

Re: [CMake] test executable failing only when run in ctest

On Jan 26, 2009, at 3:29 PM, Matthew Leotta wrote: On Jan 26, 2009, at 3:04 PM, Brad King wrote: Matthew Leotta wrote: Brad, Thanks, but I'm not sure if I completely understand your suggestion. Let me clarify. If I run the test executable ./bvxm_test_all I get no errors and no

Re: [CMake] test executable failing only when run in ctest

Matthew Leotta wrote: On Jan 26, 2009, at 3:04 PM, Brad King wrote: add_test(run_xterm xterm) $ ctest -R run_xterm Then run gdb and the test inside the xterm to see if it fails. It could be an environment difference. -Brad It runs fine from within xterm when xterm is launched as a

[CMake] Problem with FindwxWidgets.cmake

Hi, I'm currently using CMake 2.6.2 and the FindwxWidgets.cmake module that comes pre-packaged with the installation doesn't seem to properly work on windows. I set CMAKE_PREFIX_PATH so that it would be able to find the wxWidgets in a custom location. It does find wxWidgets_ROOT_DIR, but does not

[CMake] Alternative IDL compiler, and adding non-present sources

Hi all! Issue 1: Porting an old project to CMake I realized there's no way to modify the predefined behavior when one adds an IDL file to a Visual Studio project, which is associating it to midl. In our project we'd rather need to execute a different IDL compiler (TAO_IDL), but declaring an