The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15607
==
Reported By:Martin Baute
Assigned To:
On 06/09/2015 05:00 PM, Robert Goulet wrote:
install scripts doesn't seem to be per configuration
While there is not a separate script for each configuration the
scripts themselves do support switching on the configuration
selected for installation. For single-configuration generators
they only
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, release has been updated
via 86bde2ef3e5d56ca7326b51e6608a79a08eb90cd (commit)
from
CHECK_INCLUDE_FILE(stdint.h HAVE_STDINT_H)
is this supposed to create some sort of ADD_DEFINITION( -DHAVE_STDINT_H) ?
if not what else do I have to do to make that work?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
On Wednesday 10 June 2015 00:48:06 J Decker wrote:
CHECK_INCLUDE_FILE(stdint.h HAVE_STDINT_H)
is this supposed to create some sort of ADD_DEFINITION( -DHAVE_STDINT_H) ?
No.
if not what else do I have to do to make that work?
IF(HAVE_STDINT_H)
ADD_DEFINITION(HAVE_STDINT_H)
ENDIF()
If you
Hello,
Facing an issue while building in cmake 3.3.0. Need some help.
*cmakelist file code extract*
cmake_minimum_required(VERSION 2.8) project(AMFIO) #Flags for compilers if
(${CMAKE_CXX_COMPILER_ID} STREQUAL Clang) # using Clang
(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} -Wall -Wextra -pedantic
On 06/10/2015 10:11 AM, Arunava Nag wrote:
cmake_minimum_required(VERSION 2.8)
[snip]
if (${CMAKE_CXX_COMPILER_ID} STREQUAL Clang)
[snip]
CMake Warning (dev) at CMakeLists.txt:6 (if):
Policy CMP0054 is not set: Only interpret if() arguments as variables or
The policy is documented here:
On 06/10/2015 01:41 AM, Domen Vrankar wrote:
So that's why my newly added test broke with CMP0011 error :) I didn't
even know that I was using this policy with old functionality... Can I
somehow force treating of all policies as errors to spot such cases
for e.g. in tests?
See my response to
Please test that version because I made some minor tweaks.
I read all commits you made on the upstream and tested each of them
with attention. There's nothing you broke by what you wrote you
'rebased'. Again, thank you for your sincere review on my patches.
Cheers.
Eon Jeong
--
Eon
Can you change your CMake minimum required version to 3.3?
On Wed, Jun 10, 2015 at 10:11 AM, Arunava Nag arunavos...@gmail.com wrote:
Hello,
Facing an issue while building in cmake 3.3.0. Need some help.
cmakelist file code extract
cmake_minimum_required(VERSION 2.8) project(AMFIO) #Flags
Hmm. It's a possibility.
But those files are generate when I run cmake, aren't they? So re-running
that would tend to overwrite any custom modifications I made. And I have
about 350 of them.
I note that cmake_install.cmake simply uses the file(INSTALL ...) command.
How could I find the
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 4d73673ff03d1f60314eac2fde5db6483db2de1c (commit)
via
On 6/10/2015 12:57 PM, Chris Johnson wrote:
Hmm. It's a possibility.
But those files are generate when I run cmake, aren't they? So
re-running that would tend to overwrite any custom modifications I
made. And I have about 350 of them.
That is what install(CODE ...) will do for you. It will
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 83ef27fdf1bb1c23a1bf57d27cc4dad3f1f4a729 (commit)
via
And do we really still need version 2.6 as default (we could bump this
version to where current policies are still treated as warnings not
errors)?
To which default do you refer? Where in our code is it set?
Likely we cannot update it because it could change behavior
of existing scripts
Ok I think I got something nicely integrated now.
Patch in attachment.
This enable generator expressions for the target properties OUTPUT_NAME and
RUNTIME_OUTPUT_DIRECTORY, as well as the DESTINATION property of the install
command.
Cheers!
-Robert Goulet
-Original Message-
From:
Hi,
I tried several times now to find documentation about how to define
and use target names which seem to have namespaces, like Qt ones.
For example: add_executable( MyProject::some_target ... )
I can't find any documentation or even name for this.
Is it considered a namespace?
In any way I
Brad King wrote:
I think Fraser's point about the docs of each policy not explicitly
mentioning deprecated is a major culprit there.
I disagree. It is obvious that NEW is better than OLD.
If it 'works' people will use it until they are forced not to, as Alex said.
I expect most people doing
I'm trying out my project on 3.3.0-rc1, but currently I'm using 2.8.11 and
2.8.12. I got a couple errors from CMP0046. Most of them are correct: I've
fixed a couple places where a non-existent dependency was used, and I want to
set this policy to NEW so that more do not sneak in.
However
On 6/10/2015 4:57 PM, Alexander Neundorf wrote:
If the conclusion would be a policy is removed after 5 years, it's deadline
could even be part of the error/warning message right from the point when it
is introduced (you are relying on CMP1234 OLD behaviour. This will be removed
June 2020.).
So, when you're saying:
...but still supporting the OLD stuff with a warning if no one tried
explicitly to set things to use OLD, they just had a working build
system.
You're effectively saying we will never remove the OLD behavior for
any policies, ever?
If that's the case, then why bother
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via b39c01dbb626bbbf2ce145311824997ad8965b33 (commit)
via
On Monday, June 08, 2015 09:57:14 Brad King wrote:
...
This may be okay for CMP0011, but CMP0024 and CMP0026 were much
more recent (3.0). I think 5 years is a more reasonable cut-off
than 2 years, especially given the time it takes CMake versions
included in older distro releases to fall out
20150610)
+set(CMake_VERSION_PATCH 20150611)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 3acb236e86a081e522417b0881f87d08f904ee3d (commit)
via
25 matches
Mail list logo
