The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13167
==
Reported By:ycollet
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=13168
==
Reported By:Denis Shamonin
Assigned To:
Hi there,
On the KDE Frameworks mailing list I had an idea for a
cmake_maximum_required(), which would be symmetric with
cmake_minimum_required().
http://thread.gmane.org/gmane.comp.kde.devel.frameworks/517/focus=532
The idea is that if you use cmake_maximum_required(2.8.8) and attempt to
On Wed, Apr 25, 2012 at 1:55 PM, Stephen Kelly steve...@gmail.com wrote:
The idea is that if you use cmake_maximum_required(2.8.8) and attempt to use
a feature or API introduced in 2.8.9, CMake would report an error.
I don't think that's the opposite of a minimum required version, I
think that
Brad King wrote:
On Wed, Apr 25, 2012 at 1:55 PM, Stephen Kelly
steve...@gmail.com wrote:
The idea is that if you use cmake_maximum_required(2.8.8) and attempt to
use a feature or API introduced in 2.8.9, CMake would report an error.
I don't think that's the opposite of a minimum required
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13169
==
Reported By:askalex
Assigned To:
On Wed, Apr 25, 2012 at 2:17 PM, Stephen Kelly steve...@gmail.com wrote:
Brad King wrote:
I don't think that's the opposite of a minimum required version, I
think that *is* one.
I'm having trouble parsing this. What does 'It is one' mean?
It is the same as a minimum required version. If
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13170
==
Reported By:Daniel Franke
Assigned To:
Hi,
As part of my NSIS packaged installer, I need to register an
environment variable e.g. MYSOFTWARE_PATH
I see the variable CPACK_PACKAGE_INSTALL_REGISTRY_KEY but am unsure
about the syntax
I tried the following but it didn't work
SET ( CPACK_PACKAGE_INSTALL_REGISTRY_KEY
Hello! I use 2.8.8 version and got the problem, with absolute paths to
files and bug in MSVS2010.
Issues is already discribed in bugtracker.
http://public.kitware.com/Bug/view.php?id=12570#c27757
I am trying to use the LLVM dragonegg plugin for GCC in a project, which
is built using CMake. However I have a hard time figuring out how to
tell CMake, what it should do. Dragonegg is a plugin, which makes GCC
use part of the LLVM infrastructure to optimize the compiled code. In my
case,
I am
2012/4/25 Nicholas Yue yue.nicho...@gmail.com:
Hi,
As part of my NSIS packaged installer, I need to register an
environment variable e.g. MYSOFTWARE_PATH
I see the variable CPACK_PACKAGE_INSTALL_REGISTRY_KEY but am unsure
about the syntax
I tried the following but it didn't work
SET
Hi All!
My project's (named Compare) structure is similar to this:
Root
|
SphinX
|
sphinxbase (autotools project)
Sound
|
|-DoScoring (my Cmake-based project)
|-Compare (my Cmake-based project)
|-CMakeLists.txt
|-src (source files
On Wed, Apr 25, 2012 at 8:21 AM, Eric Noulard eric.noul...@gmail.com wrote:
2012/4/25 Nicholas Yue yue.nicho...@gmail.com:
Hi,
As part of my NSIS packaged installer, I need to register an
environment variable e.g. MYSOFTWARE_PATH
I see the variable CPACK_PACKAGE_INSTALL_REGISTRY_KEY but
Hi Brad,
Consider looking at
https://github.com/Slicer/Slicer/blob/master/CMake/SlicerDashboardDriverScript.cmake#L246
Hth
Jc
On Tue, Apr 24, 2012 at 9:13 AM, Bradley Lowekamp blowek...@mail.nih.govwrote:
Hello,
Are both of these project using SuperBuilds?
I know with SimpleITK I was
Great!
These look like the important lines to fix my coverage issue with Superbuilds:
# HACK Unfortunately ctest_coverage ignores the BUILD argument, try to
force it...
file(READ ${slicer_build_dir}/CMakeFiles/TargetDirectories.txt
slicer_build_coverage_dirs)
file(APPEND
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, master has been updated
via fd1788294df63f3e5483c952c7dd709b41efee07 (commit)
via
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, master has been updated
via 04f5dd8ad49086f22cf866713482b5ea8c19f9fb (commit)
via
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, master has been updated
via 745067bd7e1ac9d6cc40a45c58a8d1cd61eac537 (commit)
via
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, master has been updated
via 81e696c99d8f1d9239aae722ffe2b2b15a5e0fa9 (commit)
via
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, master has been updated
via 65a4926326ccc7e76187f10909223a664ceb244c (commit)
via
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, master has been updated
via ee35d8a0eac00abb041f6e4005579f1b97890b5f (commit)
via
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, master has been updated
via 82c579de45a20ccbdd6c016199799e6922361de7 (commit)
via
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, master has been updated
via 21be162f9b33b0054e7dd7f5cb0ce93685ae08b3 (commit)
via
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, master has been updated
via 728cbd19e3574d0a103ad17cacf98518c9b2c5bf (commit)
via
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, master has been updated
via f1ecabd98a102b97f663f44953c732a74b2a9f57 (commit)
via
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, master has been updated
via f45d004c0a052646494085b687af6aa1d539c876 (commit)
via
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, master has been updated
via c4aa5386fb69822e1b131fb95cc11682ed1f5219 (commit)
via
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, master has been updated
via 91f83347d35e970896aaa9200cf68cdd0ea413ac (commit)
via
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, master has been updated
via 7e4c11e0fca5cdddf18f778760fa659982382db4 (commit)
via
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, master has been updated
via 44e2bdc7a5be4021bb5a8eef53bf87685955f263 (commit)
via
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, master has been updated
via d2230cdb5ed291087c9f1dd3fe6d66f2c5a8c760 (commit)
via
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, master has been updated
via 4b4a98d72298e892b17aa0d14462bab7836a7c1d (commit)
via
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, master has been updated
via 00be692b54c52f779ec629cfde47b588019ab49d (commit)
via
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, master has been updated
via 8bb46ee787828c75b825d72b7121296d91bef7d6 (commit)
via
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 5c9cfe4249f240e0328e0bbb1a0508116a6fbaaf (commit)
via
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 53c3ca3a59790e99b5fc94bc8d99dc20d0379c5b (commit)
via
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 283b8fe1ed285f15ee3b408ec070e8a98bb29413 (commit)
via
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 08118430d645ef0f8bb9f4429cee534b0fcb2a71 (commit)
via
39 matches
Mail list logo
