Re: [CMake] Complaint about if..endif

Does this apply to else(), too? And could you please update the man page? Thanx. Ionutz On Sat, Nov 22, 2008 at 7:53 AM, Philip Lowman [EMAIL PROTECTED] wrote: On Sat, Nov 22, 2008 at 12:17 AM, Robert Dailey [EMAIL PROTECTED] wrote: Hi, Why must endif() contain the same expression as the

Re: [CMake] [Cdash] Not receiving e-mail for failed test?

2008/11/20 Julien Jomier [EMAIL PROTECTED]: Now I receive e-mail. What does __BROKEN__ submission means? Am I (and other submitter) miss-using ctest for submitting, It means that the submission has either warnings, errors and tests then it's broken. The submission itself is fine :) Let

Re: [CMake] cmake and wxwidgets on windows

Hi Miguel, Well, it seems that UNICODE and _UNICODE are platform defined and if these have been defined, then wxUSE_UNICODE is forced. As a wxWidgets user you should set the wxUSE_UNICODE if you need UNICODE support. Now the question remains: Should we set wxUSE_UNICODE in the

Re: [CMake] Visual Studio Warning Level

Bill Hoffman wrote: Robert Dailey wrote: Hi, I've done some googling on how to set warning levels for visual studio projects generated with CMake and I can't say I really enjoy the proposed solutions I've found. Literally this should be a single function call like: cmake_warning_level(

Re: [CMake] ALL_BUILD and ZERO_CHECK

On Fri, 21 Nov 08 23:44, Robert Dailey wrote: Hi, Is there a purpose for these 2 projects? They are generated when I run: cmake -G Visual Studio 9 2008 ZERO_CHECK will rerun cmake. You can/should execute this after changing something on your CMake files. ALL_BUILD is simply a target which

Re: [CMake] Visual Studio Warning Level

On Nov 22, 2008, at 8:01 AM, Vladimir Prus wrote: Bill Hoffman wrote: Robert Dailey wrote: Hi, I've done some googling on how to set warning levels for visual studio projects generated with CMake and I can't say I really enjoy the proposed solutions I've found. Literally this should be

Re: [CMake] Complaint about if..endif

Ioan Calin Borcoman wrote: Does this apply to else(), too? And could you please update the man page? In cmake 2.6.0 and greater the arguments are optional. if(foo AND BAR) ... endif() works just fine without the variable being set. -Bill ___

Re: [CMake] Visual Studio Warning Level

Michael Jackson wrote: On Nov 22, 2008, at 8:01 AM, Vladimir Prus wrote: Bill Hoffman wrote: Robert Dailey wrote: Hi, I've done some googling on how to set warning levels for visual studio projects generated with CMake and I can't say I really enjoy the proposed solutions I've

Re: [CMake] Visual Studio Warning Level

Am Saturday 22 November 2008 15:17:12 schrieb Vladimir Prus: Michael Jackson wrote: On Nov 22, 2008, at 8:01 AM, Vladimir Prus wrote: Bill Hoffman wrote: Robert Dailey wrote: Hi, I've done some googling on how to set warning levels for visual studio projects generated with CMake

Re: [CMake] Visual Studio Warning Level

Hendrik Sattler wrote: Am Saturday 22 November 2008 15:17:12 schrieb Vladimir Prus: Michael Jackson wrote: On Nov 22, 2008, at 8:01 AM, Vladimir Prus wrote: Bill Hoffman wrote: Robert Dailey wrote: Hi, I've done some googling on how to set warning levels for visual studio

Re: [CMake] ALL_BUILD and ZERO_CHECK

On Sat, Nov 22, 2008 at 8:12 AM, Armin Berres [EMAIL PROTECTED]wrote: PS: What I'd reallylike to know is if it is possible to prevent the creation of the Source/Header folders. With source groups it is just possible to put files in a subdirectory, but I want some files directly in the project

Re: [CMake] Visual Studio Warning Level

So it seems that this issue has come up before and it is an obvious feature to implement. In the meantime, can someone offer me the code for a macro I can use to easily and portably set warning levels? Thanks. ___ CMake mailing list CMake@cmake.org

Re: [CMake] Visual Studio Warning Level

On Nov 22, 2008, at 1:13 PM, Robert Dailey wrote: So it seems that this issue has come up before and it is an obvious feature to implement. In the meantime, can someone offer me the code for a macro I can use to easily and portably set warning levels? Thanks pseudo code

Re: [CMake] Convenience lib vs static library

Sean Soria [EMAIL PROTECTED] writes: cmake claims to not support convenience libraries. Isn't building a static library and then linking it into other libraries the same as a convenience library? A convenience library works as an object file at link time: it is included on the final

Re: [CMake] Complaint about if..endif

hi rob, Why must endif() contain the same expression as the associated if() command? i think this could be the most noticed feature of cmake (in the five minute test). as noted, in other posts, you don't have to any more. but i've been thinking of creating another, less verbose, front end for

[CMake] CMake won't clean generated files for Xcode

I am trying to configure a project with CMake that uses the CxxTest testing framework. CxxTest will generate source files that may be added into application that test the software. A macro has been written that will create custom commands for generated the needed source file. However, when

Re: [CMake] CMake won't clean generated files for Xcode

Hi, I've attached my CxxTest module, maybe you find them useful. It is creating the runned files under CMAKE_BUILD_DIR, so there is no CMAKE_SOURCE_DIR pollution (of course, this is useful only if you do out of source builds, but I guess all cmake users do that, right?). The module is based on

Re: [CMake] Convenience lib vs static library

Isn't a static lib still better than nothing? I was thinking at the same thing this morning - why not use static libs and simply don't install them. I agree, this still has the problem of missing lib dependencies that you have to solve by hand (with convenience libs, if you have libB that depends