[CMake] documentation on how to use cmake as an "end-user"?

Hi all, As a developer using CMake, I'd like to add to the README a link to general documentation on how to use CMake to build the source code.  Something like this, but it's a bit out of date: https://cmake.org/runningcmake/   Is there something more recent I can link to?  I've looked into t

[CMake] FindPython.cmake in older CMake version

Hi, I'm testing out CMake 3.12, and I very much like the new FindPython.cmake. Being able to use targets for the Python libraries means I can much easier package my own library without hardcoded paths. The only thing is that I want to be compatible with older CMakes >= 3.0.  Therefore I came

Re: [CMake] how to deprecate a target?

ld you also define a non-namespaced target `foo` and craft it such that linking against it generates a linker warning? Something like "Warning: symbol `Using_just_foo_is_deprecated_use_Foo_foo_instead` defined twice, ignoring weak definition." Petr On 2 July 201

Re: [CMake] how to deprecate a target?

yone to have moved to the "foo" target first. Best, Bram. On 6/29/2018 20:22, Robert Maynard wrote: I am not aware of a nice way to setup CMake to error out if a user links to `foo` instead of `Foo::foo`. On Fri, Jun 29, 2018 at 2:05 AM Bram de Greve wrote: Hi all, Consider this

[CMake] how to deprecate a target?

Hi all, Consider this situation.  I'm building a Foo packaged, to be used by a Bar project. Foo used to export its target as simply foo. Now it exports its target as Foo::foo. Bar contains this: add_library(bar ...) target_link_libraries(bar foo) This of course must now be: add_library(bar .

Re: [CMake] multiple cvs updates for continuous build

Clinton Stimpson wrote: You can do it like this: WHILE (${CTEST_ELAPSED_TIME} LESS 36000) SET (START_TIME ${CTEST_ELAPSED_TIME}) CTEST_START (Continuous) CTEST_UPDATE (SOURCE "${CTEST_SOURCE_DIRECTORY}" RETURN_VALUE res1) CTEST_UPDATE (SOURCE "${OTHER_SOURCE_DIRECTORY}" RETURN_VALUE

[CMake] multiple cvs updates for continuous build

Hi, I have a large project that combines the sources of different CVS repositories/projects in one build. I would like to perform a continuous build on this, but AFAIK it's possible to do only one cvs update on this. So the continuous build would "listen" to only one of the CVS projects. Is the

Re: [CMake] continuous build on a branch?

Weird, because that's exactly what I'm trying. I'll have a closer look. Bram Bill Hoffman wrote: Bram de Greve wrote: Hello, Does anyone know how I can fix this? I need a continuous build on a branch, but it keeps updating to the main branch This script does that: http:

Re: [CMake] timeout on total test time?

Thanks for the info, I'll use a workaround then ... Bram Bill Hoffman wrote: Bram de Greve wrote: Hello, Can anyone answer this question? I've tried the --test-timeout switch on ctest, but it seems to have no effect. Thanks, Bram Hi, Is it possible to specify the total amou

Re: [CMake] continuous build on a branch?

Hello, Does anyone know how I can fix this? I need a continuous build on a branch, but it keeps updating to the main branch Thanks, Bram > Hi, > > How can I set up a continuous build on a branch? > > I've tried setting CTEST_UPDATE_OPTIONS to include the branch name, but > it keeps removing the

Re: [CMake] timeout on total test time?

Hello, Can anyone answer this question? I've tried the --test-timeout switch on ctest, but it seems to have no effect. Thanks, Bram > Hi, > > Is it possible to specify the total amount of time CTest may spend on > running the tests? With CTEST_TIMEOUT, you can set the time CTest may > spend on

[CMake] timeout on total test time?

Hi, Is it possible to specify the total amount of time CTest may spend on running the tests? With CTEST_TIMEOUT, you can set the time CTest may spend on each test, but that's not really what I'm looking for. Thanks Bram ___ CMake mailing list CMake

[CMake] continuous build on a branch?

Hi, How can I set up a continuous build on a branch? I've tried setting CTEST_UPDATE_OPTIONS to include the branch name, but it keeps removing the stickyness and update to the main branch. set(CTEST_CVS_CHECKOUT "${CTEST_CVS_COMMAND} -d:pserver:f...@bar.com/baz co -r branchname foobar") set

[CMake] how to set 2 additional compile flags on target (VS2005)

Hi, I'm trying to use precompiled headers with VS2005. Therefore, I need to set on the target two additional compile flags: /Yu with the header to be precompiled, and /Fp with the path of the resulting PCH. But whatever I try, cmake will only set one of them. The following will only set the seco

Re: [CMake] assembly files with masm in vs2005 64bit

> Alexander Neundorf wrote: > >> On Wednesday 29 October 2008, Bill Hoffman wrote: >> >>> Bram de Greve wrote: >>> >>>> So thumbs up for the nmake side of the story. Thanks for your help. >>>> >>>> So, now there's only

Re: [CMake] assembly files with masm in vs2005 64bit

Hi Alex, 2008/10/28 Alexander Neundorf <[EMAIL PROTECTED]> > Hi Bram, > > > That still leaves open the issue of the visual studio projects not > > including any build rule for the assembly. So it's not a build rule that > > fails, but it is simply missing ... > > Hmm, I think Bill or Brad can he

Re: [CMake] assembly files with masm in vs2005 64bit

> > > Message: 7 > Date: Mon, 27 Oct 2008 23:06:22 +0100 > From: Alexander Neundorf <[EMAIL PROTECTED]> > Subject: Re: [CMake] assembly files with masm in vs2005 64bit > To: cmake@cmake.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-6" > > Hi Bram, > > Please te

Re: [CMake] assembly files with masm in vs2005 64bit

Hi Alexander, Thanks for your quick response! 2008/10/24 Alexander Neundorf <[EMAIL PROTECTED]> > On Friday 24 October 2008, Alexander Neundorf wrote: > > > > Yes, I think you're the first one who tries that. > > > Alright! =) > > > > This is the custom build step I need to perform (copy past

[CMake] assembly files with masm in vs2005 64bit

Hi, I'm trying to build some library with vs2005 64bit using CMake. This library uses some assembly and as the 64 bit mode of vs2005 doesn't support inline assembly, and external call to MASM is necessary. However, I'm having troubles getting this working. I've googled on cmake + masm, but that