[CMake] Dependency checker and SYSTEM includes

Folks, I'm using include_regular_expression(..) in order to reduce the amount of work to be done by dependency checker and I find this command not very flexible in certain cases. I was wondering why not adding some option so that once the directory is included with SYSTEM flag it's not included in

Re: [CMake] Why not showing date/time for each operation in VERBOSE=1 mode?

> Could you change the compiler from gcc to 'time gcc'? > > Additionally perhaps specifying add_custom_command for relevant targets with > PRE_BUILD and POST_BUILD calls to 'date' would be helpful. Thanks for these nice ideas :) -- Best regards, Pavel ___

[CMake] Why not showing date/time for each operation in VERBOSE=1 mode?

Folks, I'm trying to see how misc. gcc flags affect compile times for different compilation units and it would be really nice if cmake's VERBOSE=1 mode showed date/time against each operation it performed. -- Best regards, Pavel ___ Powered by www.kitwa

Re: [CMake] How to make dependency scanner ignore some paths?

> The code is in Source/cmDependsC.cxx. > I think it's already quite optimized, but feel free to have a look at it :-) Thanks, I'll have a look. -- Best regards, Pavel ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://

Re: [CMake] How to make dependency scanner ignore some paths?

On Mon, Jan 11, 2010 at 11:53 PM, Alexander Neundorf wrote: > On Monday 11 January 2010, Pavel Shevaev wrote: >> On Sat, Dec 26, 2009 at 2:20 PM, Pavel Shevaev > wrote: >> > Guys, what is the best way to to make the dependency scanner ignore some >> > paths? &g

Re: [CMake] How to make dependency scanner ignore some paths?

On Sat, Dec 26, 2009 at 2:20 PM, Pavel Shevaev wrote: > Guys, what is the best way to to make the dependency scanner ignore some > paths? Sorry folks, I'm replying to myself So, no advice here? Let me rephrase the original question a bit then: what are the best practices to s

[CMake] How to make dependency scanner ignore some paths?

Guys, what is the best way to to make the dependency scanner ignore some paths? For example, I'm using boost in my project but I really don't want the dependency scanner to take it into account since it changes rarely(or never). For some time I've been using the following trick: include_regular_

Re: [CMake] Unrealistic percent numbers(Ubuntu cmake 2.6-patch0)

Folks, looks like I've solved this problem by changing a bit all "add_subdirectory" commands which pointed to libraries outside the current project's directory. So, instead of this: add_subdirectory(${foo_SOURCE_DIR}/../shared/lib/boost ${foo_BINARY_DIR}) ...now I'm using this: add_subdirectory(

Re: [CMake] ADD_TEST(...) doesn't output any tests into CTestTestfile.cmake (cmake 2.6-patch 0)

On Wed, Mar 4, 2009 at 7:22 PM, David Cole wrote: > Did you call ENABLE_TESTING before any ADD_TEST calls in your > CMakeLists.txt? Yes :( -- Best regards, Pavel ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.k

Re: [CMake] ADD_TEST(...) doesn't output any tests into CTestTestfile.cmake (cmake 2.6-patch 0)

> So,  this should fix the problem: > > add_subdirectory(${foo_SOURCE_DIR}/../shared/lib/boost boost_lib) Thanks, it has worked indeed, however now I'm experiencing the following problem, running "make Experimental" yields this: kurluka ~/foo/build$ make Experimen

Re: [CMake] ADD_TEST(...) doesn't output any tests into CTestTestfile.cmake (cmake 2.6-patch 0)

> Can you create a complete but small example that shows the problem? Ok, I tried to extract the minimal non-working example from my CMakeLists.txt. foo/CMakeLists.txt: == cmake_minimum_required(VERSION 2.6 FATAL_ERROR) project(foo) enable_testing() in

[CMake] ADD_TEST(...) doesn't output any tests into CTestTestfile.cmake (cmake 2.6-patch 0)

Folks, any idea why this can be happening? I have the following lines in my CMakeLists.txt: ... ENABLE_TESTING() INCLUDE(CTest) ADD_TEST(AllTests {$project_SOURCE_DIR}/scripts/runtests) ... I also have properly configured CTestConfig.cmake in the same directory with CMakeLists.txt, however "cd b

Re: [CMake] Install target is not called

> Yes but you may still want to separate BUILD from SOURCE tree > and install in > > ${PROJECT_BINARY_DIR}/bin Thanks, I'll consider this option too. I can't use it at the moment though since users of the app got used to the "bin" directory in the top level of the source tree... > That's right, i

Re: [CMake] Unrealistic percent numbers(Ubuntu cmake 2.6-patch0)

Hmlooks like this topic already popped up in the past - http://www.mail-archive.com/cmake@cmake.org/msg06916.html -- Best regards, Pavel ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/

Re: [CMake] Install target is not called

> If your binary to install is a CMake target (like in your example) > you should use: > > install(targets foo >RUNTIME DESTINATION ${foo_SOURCE_DIR}/bin) > This one didn't work neither :( > moreover installing in ${foo_SOURCE_DIR} is a bit strange, Well, there is a reason for this.

[CMake] Unrealistic percent numbers(Ubuntu cmake 2.6-patch0)

Hi, CMakers :) I'm experiencing very weird percent numbers during the build procedure, something like this: [ 20%] Built target foo [ 50%] Built target bar [150%] Built target baz [170%] Built target wow ... [1000%] Built target hey What can be causing this strange behaviour? Improperly written

[CMake] Install target is not called

Folks, what can be the reason for install target not to be called? I have something like this in my CMakeLists.txt: add_executable(foo src1 src2 src3) target_link_libraries(foo ${libs}) install(PROGRAMS ${foo_BINARY_DIR}/foo DESTINATION ${foo_SOURCE_DIR}/bin ) And for s

Re: [CMake] include_regular_expression question(Ubuntu CMake-2.6-patch0)

On Sun, Feb 15, 2009 at 11:02 PM, Pavel Shevaev wrote: > Sorry folks, I'm replying to myself - I think I've found a solution: > mark directory containing infrequently changing paths using > "set_directory_properties", e.g: > > set_directory_properties(PR

Re: [CMake] include_regular_expression question(Ubuntu CMake-2.6-patch0)

Sorry folks, I'm replying to myself - I think I've found a solution: mark directory containing infrequently changing paths using "set_directory_properties", e.g: set_directory_properties(PROPERTIES INCLUDE_REGULAR_EXPRESSION "^$") -- Best regards, Pavel __

[CMake] include_regular_expression question(Ubuntu CMake-2.6-patch0)

Hi folks, I'm new to CMake and quite happy about it(especially after having tried SCons and WAF), thank you guys, you're doing great job. The only issue bothering me at the moment is "include_regular_expression" command which I can't make work properly. I'm developing quite a large project which