On Monday, 5 June 2017 22:45:26 BST Stephen Kelly wrote:
> Brad King wrote:
> > Steve, is there any reason for the restriction other than not implementing
> > more use cases up front?
>
> There may be more information in the mailing list archives, but as far as I
> remember, yes - we wanted to be
On Thursday 30 July 2015 09:28:12 Brad King wrote:
On 07/29/2015 03:58 PM, Alex Merry wrote:
This is intended to be used from a settings file which is applied to a
group of CMake projects. This allows the file to control which policies
means that users of the settings file are not forced
Add a PARENT_SCOPE argument to cmake_policy(SET) that makes the policy
apply to the parent (strong) scope - it will break out of exactly one
level of the policy stack.
This is intended to be used from a settings file which is applied to a
group of CMake projects. This allows the file to control
Suppose you have a CMakeLists.txt file like
=
cmake_minimum_required(VERSION 2.8.12)
project(Foo)
add_library(Ext::Imported SHARED IMPORTED)
add_library(FooDep SHARED main.cpp)
install(TARGETS FooDep
ARCHIVE DESTINATION lib
LIBRARY DESTINATION lib
)
On Saturday 06 June 2015 12:36:53 Stephen Kelly wrote:
Hi,
The documentation notes that Policies are not feature toggles:
http://www.cmake.org/cmake/help/git-master/manual/cmake-policies.7.html
However, the reality is that Policies *are* feature toggles because they are
so long-lived.
On Saturday 21 March 2015 09:41:06 Gregor Jasny wrote:
Hello,
I wanted to start documenting our in-company CMake modules. Often I'd
like to refer to some basic CMake commands. As far as I understand the
intersphinx extension [1] should be able to provide that. To reference
remote projects
On Tuesday 17 March 2015 15:41:17 Brad King wrote:
On 03/13/2015 06:04 AM, Alex Merry wrote:
For the extra-cmake-modules package, I wrote some macros to help with
writing component-based Find modules, which are non-trivial to get right.
The documentation for them can be found here
For the extra-cmake-modules package, I wrote some macros to help with writing
component-based Find modules, which are non-trivial to get right.
The documentation for them can be found here:
http://api.kde.org/ecm/module/ECMFindModuleHelpers.html
I've found them incredibly useful in writing
On Monday 26 January 2015 18:22:41 Ben Boeckel wrote:
On Mon, Jan 26, 2015 at 22:39:00 +, Alex Merry wrote:
Maybe it's just my colour scheme - I'll have a play with the colour
settings when I have some free time.
FWIW, I use neverland-darker, a 256-color scheme. Looking
On Monday 26 January 2015 11:00:44 Ben Boeckel wrote:
On Mon, Jan 26, 2015 at 11:00:05 -0500, Ben Boeckel wrote:
Odd; attached is an HTML dump from Vim for what I see (:TOhtml) where
variable expansions are highlighted in strings just like outside of
strings.
Probably help if I actually
On Wednesday 21 January 2015 16:17:35 Ben Boeckel wrote:
List of improvements to the syntax file:
- drop support for 7.0 (which is 7.5 years old now);
- add support for Lua-style comments;
- update the list of system variables;
- update the list of operators;
- make only
On Friday 24 October 2014 10:02:31 Brad King wrote:
On 10/24/2014 09:50 AM, Brad King wrote:
With 3.0 we see the list of headers accumulate. With 3.1 just the
first one works and the rest do not.
I bisected it down to:
commit 5abfde6cb8a1ae0b2825797eab6c2e9842eb7c49
Author: Ben
On Friday 24 October 2014 10:20:42 Brad King wrote:
On 10/24/2014 10:02 AM, Brad King wrote:
I bisected it down to:
commit 5abfde6cb8a1ae0b2825797eab6c2e9842eb7c49
Author: Ben Boeckel ben.boec...@kitware.com
Date: Wed Mar 12 14:01:45 2014 -0400
cmDefinitions: Don't store
On 10/04/14 09:46, Stephen Kelly wrote:
Alex Merry wrote:
On 28/03/14 15:16, Stephen Kelly wrote:
The target_compile_features topic in my clone is almost ready to merge to
next.
Having looked through the docs for the topic, the thing that is missing
that I'd like to see is a way (probably
On 28/03/14 15:16, Stephen Kelly wrote:
The target_compile_features topic in my clone is almost ready to merge to
next.
Having looked through the docs for the topic, the thing that is missing
that I'd like to see is a way (probably a variable) to specify the
default enabled features for all
On 27/03/14 14:33, Brad King wrote:
On 03/26/2014 03:02 PM, Alex Merry wrote:
I wrote some documentation on how to write a find module for KDE's
extra-cmake-modules project, and Stephen suggested upstreaming it. So
attached is a patch that does that.
Thanks for working on this. I like
imported targets
(which are much easier and less error-prone to use).
Alex
From 2dc24347a65c1aeec6410dc265e6b0047b6a2317 Mon Sep 17 00:00:00 2001
From: Alex Merry alex.me...@kde.org
Date: Wed, 26 Mar 2014 18:54:02 +
Subject: [PATCH] Rewrite the find module developer documentation
On 26/03/14 22:28, Ben Boeckel wrote:
[ Sorry for stealing the thread, but this might help spawn off a
follow-up patch for COMPONENT-handling docs. ]
On Wed, Mar 26, 2014 at 19:02:40 +, Alex Merry wrote:
Modules that provide components are glossed over currently, despite
being
b82c9c6ff78582254a540b83fad9cc7c98b88479 Mon Sep 17 00:00:00 2001
From: Alex Merry alex.me...@kde.org
Date: Wed, 26 Feb 2014 11:41:35 +
Subject: [PATCH 1/2] find_dependency: use correct version variable name
The code set cmake_fd_version, but used ${version}.
---
Modules/CMakeFindDependencyMacro.cmake | 2 +-
1 file changed, 1
this.
Alex
From 57b10901f1f857bde0471f2be4398dace5c36253 Mon Sep 17 00:00:00 2001
From: Alex Merry k...@randomguy3.me.uk
Date: Sat, 22 Feb 2014 13:35:14 +
Subject: [PATCH] Always set version variable of find_dependency macro
If there is no ARGV1, that is fine; version will be made empty
On 04/02/14 12:45, Stephen Kelly wrote:
Alex Merry wrote:
If you have a header file like foo.h and the corresponding source file
is, say, foo_win.cpp, automoc will never look at foo.h.
... unless you include moc_foo.cpp in foo_win.cpp, right?
Yes; the fix is easy, but developers need
.
+# Copyright 2014 Alex Merry d...@randomguy3.me.uk
#
# Distributed under the OSI-approved BSD License (the License);
# see accompanying file Copyright.txt for details.
@@ -274,7 +282,7 @@ function(SET_PACKAGE_PROPERTIES _name _props)
message(FATAL_ERROR PROPERTIES keyword is missing
On 03/02/14 19:27, Stephen Kelly wrote:
It's generally preferable to write an email and attach the patch.
Noted.
Alex Merry wrote:
+set_package_properties(${dep} PROPERTIES TRANSITIVE_DEPENDENCY)
I prefer not to create public API in set_package_properties for something
that doesn't
The automoc documentation
(http://www.cmake.org/cmake/help/v2.8.12/cmake.html#prop_tgt:AUTOMOC)
states that all header files are considered for automoc, which is not
true for any sensible definition of all header files.
Only header files with certain names are considered: specifically, if
you
24 matches
Mail list logo
