Re: [CMake] Making ALL_BUILD be Visual Studio's "startup project"

On Mon, Nov 24, 2008 at 2:45 PM, Tyler Roscoe <[EMAIL PROTECTED]> wrote: > On Mon, Nov 24, 2008 at 02:22:22PM -0500, [EMAIL PROTECTED] wrote: > > In a certain project where we started using CMake about five years ago, > > it used to be that when we opened the Visual Studio 6.0 workspace > > create

Re: [CMake] ALL_BUILD and ZERO_CHECK

On Mon, Nov 24, 2008 at 9:44 AM, Armin Berres <[EMAIL PROTECTED]>wrote: > On Mon, 24 Nov 08 08:38, Philip Lowman wrote: > > Works for me. Puts files in the root of the "bar" project: > > > > PROJECT(foo) > > SOURCE_GROUP("" FILES bar.h bar.cc) > > ADD_EXECUTABLE(bar bar.h bar.cc) > > Ah, ok. What

[CMake] Mercurial support for ctest

Hi, Attached is a patch to add the support for mercurial (hg) to ctest (to apply to CMake 2.6.2 release or 2.6.0). The first step consisted in finding the equivalent mercurial command and the correct way to parse the output (to enable the Coutinuous). Here are some of the points which may need a

Re: [CMake] ALL_BUILD and ZERO_CHECK

From: "Robert Dailey" <[EMAIL PROTECTED]> > Ah, okay. If it manages synchronization between the CMakeLists.txt files and > the vcproj files I can understand the need for them. I guess I should have > first asked what they are for instead of immediately trying to get rid of > them :) Oh darn, my lo

Re: [CMake] ALL_BUILD and ZERO_CHECK

> Robert Dailey wrote: > > The only trouble these projects are causing me is clutter. There is no > > functional purpose for them as far as I know, which is another reason > > why I do not like them. > > You could try this: > > set(CMAKE_SUPPRESS_REGENERATION TRUE) > > I think that will get rid

Re: [CMake] How to specify library dependencies?

On Nov 24, 2008, at 5:08 PM, Robert Dailey wrote: On Mon, Nov 24, 2008 at 4:02 PM, Michael Jackson <[EMAIL PROTECTED] > wrote: On Nov 24, 2008, at 4:29 PM, Robert Dailey wrote: On Mon, Nov 24, 2008 at 2:41 PM, Michael Jackson <[EMAIL PROTECTED] > wrote: typically you do: add_executable(ma

Re: [CMake] Unit testing in CMake

Le Mon, 24 Nov 2008 16:06:06 -0600, "Robert Dailey" <[EMAIL PROTECTED]> a écrit : > Hi, > > I'm reading this wiki > articleon how to > perform tests using CMake. However, the tests I'm wanting to run > aren't already built. I need to be able to

Re: [CMake] How to specify library dependencies?

On Mon, Nov 24, 2008 at 4:02 PM, Michael Jackson < [EMAIL PROTECTED]> wrote: > > On Nov 24, 2008, at 4:29 PM, Robert Dailey wrote: > > On Mon, Nov 24, 2008 at 2:41 PM, Michael Jackson < >> [EMAIL PROTECTED]> wrote: >> typically you do: >> >> add_executable(main main.cpp) >> target_link_libraries

[CMake] Unit testing in CMake

Hi, I'm reading this wiki articleon how to perform tests using CMake. However, the tests I'm wanting to run aren't already built. I need to be able to use CMake to first compile the test and then run it afterwards. How would I handle this behavio

Re: [CMake] How to specify library dependencies?

On Nov 24, 2008, at 4:29 PM, Robert Dailey wrote: On Mon, Nov 24, 2008 at 2:41 PM, Michael Jackson <[EMAIL PROTECTED] > wrote: typically you do: add_executable(main main.cpp) target_link_libraries(main a) and CMake _usually_ picks the correct library for the given platform (a.lib, a.so, a

Re: [CMake] How to specify library dependencies?

On Monday 24 November 2008, Robert Dailey wrote: > On Mon, Nov 24, 2008 at 2:41 PM, Michael Jackson < > > [EMAIL PROTECTED]> wrote: > > typically you do: > > > > add_executable(main main.cpp) > > target_link_libraries(main a) > > > > and CMake _usually_ picks the correct library for the given plat

Re: [CMake] How to specify library dependencies?

On Mon, Nov 24, 2008 at 2:41 PM, Michael Jackson < [EMAIL PROTECTED]> wrote: > typically you do: > > add_executable(main main.cpp) > target_link_libraries(main a) > > and CMake _usually_ picks the correct library for the given platform > (a.lib, a.so, a.dylib... ) > > Is that what you were asking

Re: [CMake] How to specify library dependencies?

On Nov 24, 2008, at 3:10 PM, Robert Dailey wrote: Hi, I need to be able to specify directories that the linker will search to be able to find libraries it is to link against. For this, the solution I've found is LINK_DIRECTORIES(). Next, I need to be able to specify library files that th

Re: [CMake] ALL_BUILD and ZERO_CHECK

On Mon, Nov 24, 2008 at 2:14 PM, Hendrik Sattler <[EMAIL PROTECTED]>wrote: > Am Monday 24 November 2008 17:36:10 schrieb Bill Hoffman: > > Robert Dailey wrote: > > > You guys have managed to steal my thread and get completely off topic. > > > > > > Can anyone answer my original question please? >

[CMake] How to specify library dependencies?

Hi, I need to be able to specify directories that the linker will search to be able to find libraries it is to link against. For this, the solution I've found is LINK_DIRECTORIES(). Next, I need to be able to specify library files that the executable will link against. I have no idea how to do th

Re: [CMake] ALL_BUILD and ZERO_CHECK

Am Monday 24 November 2008 17:36:10 schrieb Bill Hoffman: > Robert Dailey wrote: > > You guys have managed to steal my thread and get completely off topic. > > > > Can anyone answer my original question please? > > ZERO_CHECK is essential to the build working. ALL_BUILD is useful as > it creates

Re: [CMake] ALL_BUILD and ZERO_CHECK

On Mon, Nov 24, 2008 at 12:28 PM, Bill Hoffman <[EMAIL PROTECTED]>wrote: > Robert Dailey wrote: > > >> The only trouble these projects are causing me is clutter. There is no >> functional purpose for them as far as I know, which is another reason why I >> do not like them. >> > You could try this:

Re: [CMake] Making ALL_BUILD be Visual Studio's "startup project"

On Mon, Nov 24, 2008 at 02:22:22PM -0500, [EMAIL PROTECTED] wrote: > In a certain project where we started using CMake about five years ago, > it used to be that when we opened the Visual Studio 6.0 workspace > created by CMake, the ALL_BUILD project was conveniently defined as the > "startup proje

[CMake] Link in object files generated by another tool

Is it possible to link in an object file generated by another tool? I want to create a custom command that generates an object file that I could then link into a library or executable later. Is this possible from CMake? Thanks, James ___ CMake mailing

[CMake] Making ALL_BUILD be Visual Studio's "startup project"

In a certain project where we started using CMake about five years ago, it used to be that when we opened the Visual Studio 6.0 workspace created by CMake, the ALL_BUILD project was conveniently defined as the "startup project" already, meaning that all one had to do was to click the "Build" butt

Re: [CMake] ALL_BUILD and ZERO_CHECK

On Mon, Nov 24, 2008 at 12:05 PM, Bill Hoffman <[EMAIL PROTECTED]>wrote: > Bill Hoffman wrote: > >> Robert Dailey wrote: >> >> >>> I'm pretty sure I can create a visual studio solution with a single >>> project that builds exactly what I'm having CMake build for me. When I >>> manually create this

Re: [CMake] ALL_BUILD and ZERO_CHECK

Robert Dailey wrote: The only trouble these projects are causing me is clutter. There is no functional purpose for them as far as I know, which is another reason why I do not like them. You could try this: set(CMAKE_SUPPRESS_REGENERATION TRUE) I think that will get rid of ZERO_CHECK, but I

Re: [CMake] ALL_BUILD and ZERO_CHECK

Bill Hoffman wrote: Robert Dailey wrote: I'm pretty sure I can create a visual studio solution with a single project that builds exactly what I'm having CMake build for me. When I manually create this visual studio solution I never create a ZERO_CHECK project or an ALL_BUILD project and eve

Re: [CMake] ALL_BUILD and ZERO_CHECK

On Mon, Nov 24, 2008 at 10:36 AM, Bill Hoffman <[EMAIL PROTECTED]>wrote: > Robert Dailey wrote: > > You guys have managed to steal my thread and get completely off topic. >> >> Can anyone answer my original question please? >> >> > ZERO_CHECK is essential to the build working. ALL_BUILD is usef

Re: [CMake] ALL_BUILD and ZERO_CHECK

Robert Dailey wrote: I'm pretty sure I can create a visual studio solution with a single project that builds exactly what I'm having CMake build for me. When I manually create this visual studio solution I never create a ZERO_CHECK project or an ALL_BUILD project and everything works perfect

Re: [CMake] Convenience lib vs static library

On Sunday 23 November 2008, Ioan Calin Borcoman wrote: > Would it be possible to add support for libtool in a cmake module? I > understand that this would be against cmake's policy of not depending > on external apps, but it could be a transient solution until full > fledged support for convenience

Re: [CMake] How to properly write a Module/Config.cmake file

On 24.11.08 18:23:09, Ioan Calin Borcoman wrote: > Why not provide a pkg-config .pc file that can be used by your users? > > The syntax of .pc files is quite simple and your user can use > pkg_check_module once the .pc is installed (or even use some some > other build system that knows how to hand

Re: [CMake] How to properly write a Module/Config.cmake file

On 24.11.08 17:00:43, Pablo Yanez Trujillo wrote: > Hi > > I'm reading > http://www.cmake.org/cmake/help/cmake2.6docs.html#command:find_package for > the usage of FIND_PACKAGE, but > I'm not interested in using the FIND_PACKAGE command but to write a Module so > that anybody is able to use > FI

Re: [CMake] ALL_BUILD and ZERO_CHECK

Robert Dailey wrote: You guys have managed to steal my thread and get completely off topic. Can anyone answer my original question please? ZERO_CHECK is essential to the build working. ALL_BUILD is useful as it creates the correct depend chain. There is no way to turn these off. -Bil

Re: [CMake] Output directory

I dump all my apps in the CMAKE_BUILD_DIR with: set(EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR}) On Mon, Nov 24, 2008 at 6:23 PM, Robert Dailey <[EMAIL PROTECTED]> wrote: > Is there a way to change what directory object files and > executables/libraries are placed in? Thanks. ___

[CMake] Output directory

Is there a way to change what directory object files and executables/libraries are placed in? Thanks. ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] How to properly write a Module/Config.cmake file

Why not provide a pkg-config .pc file that can be used by your users? The syntax of .pc files is quite simple and your user can use pkg_check_module once the .pc is installed (or even use some some other build system that knows how to handle pkg-config, like autotools). Cheers, Ionutz On Mon, N

[CMake] How to properly write a Module/Config.cmake file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I'm reading http://www.cmake.org/cmake/help/cmake2.6docs.html#command:find_package for the usage of FIND_PACKAGE, but I'm not interested in using the FIND_PACKAGE command but to write a Module so that anybody is able to use FIND_PACKAGE(myLib ..

Re: [CMake] ALL_BUILD and ZERO_CHECK

On Mon, Nov 24, 2008 at 8:44 AM, Armin Berres <[EMAIL PROTECTED]>wrote: > On Mon, 24 Nov 08 08:38, Philip Lowman wrote: > > Works for me. Puts files in the root of the "bar" project: > > > > PROJECT(foo) > > SOURCE_GROUP("" FILES bar.h bar.cc) > > ADD_EXECUTABLE(bar bar.h bar.cc) > > Ah, ok. What

Re: [CMake] ALL_BUILD and ZERO_CHECK

On Mon, 24 Nov 08 08:38, Philip Lowman wrote: > Works for me. Puts files in the root of the "bar" project: > > PROJECT(foo) > SOURCE_GROUP("" FILES bar.h bar.cc) > ADD_EXECUTABLE(bar bar.h bar.cc) Ah, ok. What I am trying is more or less the following: PROJECT(foo) source_group("" REGULAR_EXPRE

Re: [CMake] Visual Studio Warning Level

Judicaël Bedouet wrote: I love the idea to set warning flags in platform files but I don't understand why new files must be created. Is not it possible to add warning variables to existent platform files in Modules/Platform ? That would be the end goal. However, if someone wanted it sooner it

Re: [CMake] ALL_BUILD and ZERO_CHECK

On Mon, Nov 24, 2008 at 7:39 AM, Armin Berres <[EMAIL PROTECTED]>wrote: > On Sat, 22 Nov 08 12:47, Philip Lowman wrote: > > 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 > >

Re: [CMake] Visual Studio Warning Level

Hello, I'm very interested in the fact that CMake could offer possibilities to portably set default warning levels. All people, with who I work, wondered a day how to set warning flags, especially for gcc (Flag /W3 is already set for Visual Studio). Different simple solutions have been found but

[CMake] CTest Subversion support and update handler

I'm trying to patch CTest (CMake 2.6.2) so that it can handle spaces in usernames, but am having real difficulty understand the cmCTestUpdateHandler::ProcessHandler() source and believe there may be fundamental bugs in the code. The lack of *any* comments doesn't help and makes me worry about

Re: [CMake] ALL_BUILD and ZERO_CHECK

On Sat, 22 Nov 08 12:47, Philip Lowman wrote: > 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 i

Re: [CMake] Complaint about if..endif

Andreas Schneider a écrit : On Sunday 23 November 2008 17:43:53 cyril_wobow wrote: Sure, I guess we are all here because CMake is a very powerful suite, with tons of functionalities and useful abstractions. But I challenge anyone to seriously tell me that he/she enjoys writing CMake script. A

Re: [CMake] Complaint about if..endif

On Sunday 23 November 2008 17:43:53 cyril_wobow wrote: > Sure, I guess we are all here because CMake is a very powerful suite, > with tons of functionalities and useful abstractions. But I challenge > anyone to seriously tell me that he/she enjoys writing CMake script. As > soon as you don't have t

Re: [CMake] missing OLDNAMES.lib when building for WinCE

Hello, I was using the NMake Generator, and I simply forgot to run the vsvars, prior to runing cmake :(. The OLDNAMES.lib is not mentioned in any of the generated Makefiles, but it was found in the object files. Maybe this is a "default" behaviour of cl to link against that library. kind regards A

[CMake] GetLibraryNamesInternal called on imported target

Hi, When I run (cvs head) cmake on my kde sources on OSX, I get lots of these errors: CMake Internal Error (please report a bug) in CMakeLists.txt: GetLibraryNamesInternal called on imported target: kparts What is going on? -- Boudewijn Rempt | http://www.valdyas.org