On Friday 17 February 2012, Alexander Neundorf wrote:
On Friday 17 February 2012, Brad King wrote:
On 2/17/2012 5:05 PM, Alexander Neundorf wrote:
I think the nicer MODULE_MODE and CONFIG_MODE keywords are not worth
breaking backward compatibility of users projects (not cmake) this way.
2012/2/17 Eric Noulard eric.noul...@gmail.com:
2012/2/17 Alexander Neundorf neund...@kde.org:
On Friday 17 February 2012, Eric Noulard wrote:
2012/2/17 Alexander Neundorf neund...@kde.org:
On Thursday 16 February 2012, Brad King wrote:
On 2/16/2012 1:24 PM, Alexander Neundorf wrote:
Hi all,
I'm pursuing my quest for a better CPack doc.
First set of modifications are in master:
cpack --help-command-xxx
cpack --help-variable-xxx
works.
However variables are somehow problematic because I get all the
properties defined for CMake in the doc because variables are a
special kind
On Saturday 18 February 2012, Eric Noulard wrote:
...
include(CMakePackageConfigHelpers)
create_and_install_package_config_files(NAME Foo
CONFIG_TEMPLATE FooConfig.cmake.in
DESTINATION ${LIB_INSTALL_DIR}/Foo/cmake
PATH_VARS
Setup: Windows XP SP3 32 bits running on VMWare Workstation 8.0.1 with 4
real cores (no HT) assigned out of 4 available on the host machine,
which is Kubuntu 11.08 64 bits (kernel version 3.0.0-16-generic).
Visual Studio 2010 Ultimate. JOM 0.9.4 (that's an old version, but on my
experience newer
My recent commit on CPack-dynamicDocSection
http://cmake.org/gitweb?p=cmake.git;a=shortlog;h=e175af3e74006e6f3a4fdaead20522b29034c45b
may have broken this build
http://open.cdash.org/testDetails.php?test=135708291build=2018382
the trouble is I cannot imagine why, since most of the modification
2012/1/16 Michael Wild them...@gmail.com:
Definitely a bug in MySQL. They should be setting
CMAKE_REQUIRED_INCLUDES to ${OPENSSL_INCLUDE_DIR} before invoking the
CHECK_SYMBOL_EXISTS() function/macro in line 72 of cmake/ssl.cmake.
Otherwise CMake will not use the include directory found by
Hi,
On Fri, Feb 17, 2012 at 12:00:10PM -0500, cmake-requ...@cmake.org wrote:
Date: Fri, 17 Feb 2012 11:48:28 -0500
From: John Drescher dresche...@gmail.com
Subject: Re: [CMake] Generating CMake scripts from Visual Studio
solutions projects?
To: Eric Noulard eric.noul...@gmail.com
2+ years? That could easily end up like a Yugo vs. Porsche surprise ;)
The original vcproj2cmake script was composed of 300 lines,
and now the project is to the tune of around 4000 lines.
I have a lot of 5 to 15 year old MFC code(applications, dlls, static
libraries) that I would like to
This hang happened after installing Visual Studio 10 Service Pack 1.
Is there a known workaround for this?
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
Mantis == 0011968: cmake uses wrong project-guid entry (Visual Studio
2010): ProjectGUID
This is marked minor. The solution is in deed minor. The steps to the
solution are anything but.
Find in Files ProjectGUID Replace ProjectGuid in
build-dir/CMakeFiles/*.*
Rerun your generator and the
Now I don't know what is happening. This is no longer working. Back to
hanging up.
On Sun, Feb 19, 2012 at 7:59 AM, Nicky Perian nickyper...@gmail.com wrote:
Mantis == 0011968: cmake uses wrong project-guid entry (Visual Studio
2010): ProjectGUID
This is marked minor. The solution is in deed
Now I don't know what is happening. This is no longer working. Back to
hanging up.
I have never had this hang and I use visual studio 2010 SP1 daily for
over a year with cmake. Now I am on cmake-2.8.7 however I have used
probably every other 2.8 release as well.
John
--
Powered by
On Sat, Feb 18, 2012 at 11:23 PM, Nicky Perian nickyper...@gmail.com wrote:
Applied 5 additional microsoft updates related to sp1 and seems to by
working. Need to follow my own advice and apply updates to exhaustion.
I do have Microsoft Update running on all machines that I use CMake/VS
2010
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 39f0585e97783fa86779ad0c2067700f013f4a24 (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 12ab4af0b9422b67ea975a3579a7c93cabae3a6b (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 946ea3392e481dc1c20bafbce20af8f12e273f6b (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 c984ff2728288c7a5f38aa323110f5e1845b91fe (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 1c743388e414a33f73482e4e39861f13fe42a40d (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 704a6b00f36f8bfbafd05c074500d63768a13989 (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 7339cab0d39c5bcdceca220d4397b796a6fbab56 (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 48382d577d3bda377183c781096b595dc3f260ad (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 629cca4518cec1781bc9bbb3bd20ec0d74a62429 (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 e175af3e74006e6f3a4fdaead20522b29034c45b (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 263d9bdd64621370b1da991d7e3f0a3334643099 (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 e316cbbbc32bd7711c4bbd96ab34adfa79722d79 (commit)
from
26 matches
Mail list logo
