On 10/14/2013 04:40 PM, Evgeniy Dushistov wrote:
I wonder, does cmake support more then 8 bits for text encoding?
Looking at source code there is nothing about wchar_t or converting
utf-16/utf-32 to utf-8 on the fly. So what sence to support
anything except utf-8 BOM?
I wrote it that way to
On 10/15/2013 05:57 AM, Eric Noulard wrote:
However, from my understanding of the cmRST::ProcessModule
assumes that all markup are in a header I think it would be more convenient
to allow #.rst: anywhere in a module
It is allowed anywhere in the module already. Any #.rst: line
enables
On 10/14/2013 05:10 PM, Raphael Kubo da Costa wrote:
This was probably broken for a long while, but the problem was not apparent
because the check for execinfo.h would fail by default because
-I/usr/local/include was not being passed to the compiler when making the
checks for the header's
On 10/10/2013 09:46 AM, Brad King wrote:
Since this topic makes sweeping changes throughout the source code
we'll have to schedule a flag day on which I will freeze the
repository and apply the permanent conversion. Currently I plan
for this to be just after 2.8.13 is released.
As discussed
On 10/15/2013 11:06 AM, Eric Noulard wrote:
The fact that CPack uses cmake scripts does not mean the cmake **command**
is processing the CPack scripts.
I'm sure you know that but cpack -G NSIS does not call cmake command,
it is simply creating a cmake script processing object instance.
In
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14485
==
Reported By:irwin
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14486
==
Reported By:irwin
Assigned To:
On 2013-10-15 10:21-0400 Brad King wrote:
On 10/14/2013 02:22 PM, Alan W. Irwin wrote:
Therefore, I think a good compromise would be to provide both of these
possibilities to users, with the first one being used by default, but
with the second one used instead if a specific variable or
Hi!
I have the test succesfully running using the provided framework for
CTestUpdate, so I have a new CTest.UpdateP4 test. Right now it runs against
a local p4d server instance that you can download for free from Perforce.
I'm imagining that, depending on the testing machine, we might need to be
On 2013-10-15 18:44, Pedro Navarro wrote:
I'm imagining that, depending on the testing machine, we might need to be
able to specify where the perforce server is located, if it's not the local
machine (using either a command line switch or an environment variable). Is
there any infrastructure for
Hi CMake list,
A colleague and I are trying to somewhat sneak in CMake in a project
that uses Visual Studio for IDE. This is a fairly big step to take
and we anticipate a bit of push-back, even if it clearly is a
worthwhile improvement. One way to maybe ease the transition would be
to check in
Hi Magnus.
I am afraid that's not really possible (safely). CMake uses absolute paths
all over the place (by design), so all output file paths etc. are hardcoded
in the .sln and .vc[x]proj files to the paths applicable where they were
generated. You can experiment with the variable
On Tue, Oct 15, 2013 at 10:56 AM, Petr Kmoch petr.km...@gmail.com wrote:
Hi Magnus.
I am afraid that's not really possible (safely). CMake uses absolute paths
all over the place (by design), so all output file paths etc. are hardcoded
in the .sln and .vc[x]proj files to the paths applicable
On Monday, 14. October 2013, 19:07:06, Matthew Woehlke wrote:
The IN LISTS signature of foreach seems to do additional list
splitting, leading to (foo;bar baz) appearing as 3 elements.
Accessing the ARGV array by the positional indices (e.g. ${ARGV0})
prevents the splitting.
Really?
Thank you both for you responses.
As a side note, it might be nice to add a function to cmake along the lines of
add_cmake_cache_dependency(…) or some better name that just adds the dependency
without having to configure a dummy file.
-Kris
From: David Cole [mailto:dlrd...@aol.com]
Sent:
All--
I'm using CMake 2.8 to create an Xcode project with ITK, for use with Xcode 5.
I've followed this post:
http://www.itk.org/pipermail/insight-users/2009-February/028911.html
I'm using the Hello World example from the ITK 4.4.2 source, which is I think
identical or very close to the one
I set Boost_LIBRARYDIR to a list of 2 directories where boost libs are
installed on linux. distrib
However, once a component is found, it sets _boost_LIBRARY_SEARCH_DIRS to
be _only_ Boost_LIBRARY_DIR and a NO_DEFAULT_PATH
In my case, I still want to keep searching, for other components, in the
Hello, I'm using NSIS and CPack with this configs:
(...)
set(CPACK_PACKAGE_EXECUTABLES MyTool My Tool Description)
set(CPACK_CREATE_DESKTOP_LINKS MyTool)
set(CPACK_NSIS_MODIFY_PATH ON)
(...)
Then the installer shows two options:
1) An option to add an icon to the desktop
2) An option to add
Hi,
I'd like to make some code in my build system dependent on the existance of a
target. Basically I'd like to write something like this:
if(TARGET optional_lib)
add_library(bar ${bar_srcs})
target_link_library(bar optional_lib)
endif()
The problem I have is that for a couple of reasons
This seems like an Xcode bug. I'm seeing the same thing you are. The path with
the extra build is the project's build path. The target's build path seems to
be ignored when trying to figure out the location of the binary for the
Products group.
Hi,
On Tue, Oct 15, 2013 at 12:00:05PM -0400, cmake-requ...@cmake.org wrote:
Date: Tue, 15 Oct 2013 17:49:40 +0200
From: Johannes Zarl johannes.z...@jku.at
Hi,
I'd like to make some code in my build system dependent on the existance of a
target. Basically I'd like to write something like
On 2013-10-15 11:49, Johannes Zarl wrote:
I'd like to make some code in my build system dependent on the existance of a
target. Basically I'd like to write something like this:
if(TARGET optional_lib)
add_library(bar ${bar_srcs})
target_link_library(bar optional_lib)
endif()
The problem
On Tue, Oct 15, 2013 at 10:16 AM, Malfettone, Kris
kris.malfett...@sig.com wrote:
As a side note, it might be nice to add a function to cmake along the lines
of add_cmake_cache_dependency(…) or some better name that just adds the
dependency without having to configure a dummy file.
+1 nice
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 289f15b63015a18c6fd774702b4f38b9a824d0f4 (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 6b3b03dcf4edb657959939e907f0c16931d483a5 (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 77ade1e5a74f96d8a1ec088393c8fd6f74637ca6 (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 08dc9720efff8cb3e11d615a4eda76286880bd01 (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 29b1e591152dc56c03ae2b6d6721d5b1c297505a (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 ebffbda4476aae1e89029f2e24fd76a22765205a (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 34f66ae21b5d90588165a4b76d3e47afb989e0e5 (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 cd36929c278d69c00850144932d931676ed5f889 (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 21ccad58fd5abae66b67baba200e2b6cb2402e91 (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 cb51088f75f9496fa472972e133620c1e2454052 (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 69fd12583c18e42338aabfa67cd1791571a2c86e (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 06491955ebe566e025b25abaa91977824811e282 (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 b31ca93ba2665c353ba723fecff55eaedf5fb569 (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 33c1cdc254b3942ebd0d704dd5f967205857676e (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 3213734d14048e9c2aa921dc533f66a3a543b9c5 (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 a7b989c2ae68faa8733b2a3acf601ef163fb860b (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 c4d64207cf524c02b5a6600123d035c1f4900bfe (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 8ef346ffb0109d02812d934e676751ecdd76ccdd (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 b7fa7f7f82931173aa9c66962b00deed44b5bad8 (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 0d10c10..833903e 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
set(CMake_VERSION_MAJOR 2)
set(CMake_VERSION_MINOR 8)
set(CMake_VERSION_PATCH 12)
-set(CMake_VERSION_TWEAK 20131015
43 matches
Mail list logo
