The patch worked for me.
cheers,
Erik Sjölund
On Thu, Dec 4, 2014 at 4:52 PM, Brad King brad.k...@kitware.com wrote:
On 12/04/2014 10:32 AM, Brad King wrote:
Roger, as the contributor of this module do you have any reason
not to change the name?
I've constructed a commit to perform the
On 12/04/2014 05:54 PM, Roger Leigh wrote:
No. Either is fine with me; I didn't expect this to be problematic
to omit the C suffix, but happy to have it added if it will avoid
confusion.
I just saw your other mail saying you'd made a patch. Do you need me
to do anything else?
Please just
On 05-Dec-14 17:12, Brad King wrote:
On 12/05/2014 09:10 AM, Ruslan Baratov wrote:
file: Add LOCK subcommand to do file and directory locking
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e6db4c5a
Great, thank you! So will this be applied to cmake 3.1.0?
No, sorry. The feature
On 12/05/2014 09:38 AM, Ruslan Baratov wrote:
Okay, just curious what version it will be?
3.2. There is a roadmap here:
http://www.cmake.org/Bug/roadmap_page.php
with tentative dates.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
On 05-Dec-14 17:09, Brad King wrote:
On 12/05/2014 09:03 AM, Ruslan Baratov wrote:
Actually why not use 'strtoll' and 'long long' ?
I'm not sure that function or type exists portably on some of the
older host platforms we support. The long type should be plenty
big for timeout values, and
On 12/05/2014 09:51 AM, Ruslan Baratov wrote:
Sending patch with 'long'.
Applied while also renaming to StringToLong, thanks:
file: Use 'long' to represent the parsed LOCK TIMEOUT value
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=97841dad
What granularity you think is appropriate,
Hi Christoph,
Thanks for working on this.
On 12/05/2014 02:35 AM, Christoph Grüninger wrote:
For users it would be great to simply have all these binaries.
I don't have all the converters installed but can still build PDF books.
The varying tools do not all come in the same package on Linux
On 12/04/2014 12:59 AM, Konstantin Podsvirov wrote:
In the source tree, you can see some of the components.
The Debian packaging can serve as a good reference:
cmake - cross-platform, open-source make system
cmake-curses-gui - curses based user interface for CMake (ccmake)
cmake-data - CMake
I see, thanks.
cheers,
Erik Sjölund
On Fri, Dec 5, 2014 at 7:32 PM, Brad King brad.k...@kitware.com wrote:
On 12/05/2014 04:28 AM, Erik Sjölund wrote:
The CMake documentation doesn't mention that the order matters:
http://www.cmake.org/cmake/help/v3.1/command/file.html#command:file
Why does
Hi, Brad!
05.12.2014, 22:33, Brad King brad.k...@kitware.com:
On 12/04/2014 12:59 AM, Konstantin Podsvirov wrote:
In the source tree, you can see some of the components.
The Debian packaging can serve as a good reference:
cmake - cross-platform, open-source make system
cmake-curses-gui -
Hi all,
I’m writing a CMake file for a project that should be compiled both in Ubuntu
and OS X.
I want to use eclipse as IDE, gcc and C++ 11.
I read different threads that suggest how to enable C++ 11 in eclipse.
According to them I included these lines in my CMake:
set(CMAKE_CXX_FLAGS
It turns out that CGAL's CGAL_CreateSingleSourceCGALProgram.cmake module
handles this nicely:
create_single_source_cgal_program( src/cdt-docopt.cpp
src/docopt/docopt.cpp)
does the trick.
Thanks for your consideration!
On Thu, Dec 4, 2014 at 10:54 PM, Adam Getchell adam.getch...@gmail.com
So, it appears to find the compiler OK since it emits the correct compiler
identification. But, the actual value of CMAKE_CXX_COMPILER is not usable. If
you try to execute
C:/Program…./x86_amd64/cl.exe from within a CMake script or even from the
command line, it will fail and produce the
Hi all.
I'm converting a small Makefile-based project to CMake. The project is not
mine, so I am trying to match its existing buildsystem as closely as
possible.
One of the rules in the original Makefile is (simplified) as follows:
examples: all
make -C example_dir all
This gives a target
Try:
cmake --build . --target examples
(where . represents the current working directory, and assumes
you're in the top level build tree...)
On Fri, Dec 5, 2014 at 5:46 AM, Petr Kmoch petr.km...@gmail.com wrote:
Hi all.
I'm converting a small Makefile-based project to CMake. The project is
Hi Jakub: Thanks for the tip. What is the proper way to execute the compiler
during the initial configure step? try_compile?
Thanks,
Allen
So, it appears to find the compiler OK since it emits the correct compiler
identification. But, the actual value of CMAKE_CXX_COMPILER is not usable. If
I assume you actually meant 'cmake --build . --target example_dir', the
name of the directory. 'examples' is the name of the custom target; if that
target's command was to build itself, I believe it would become a fork bomb.
Anyway, I tried it with the directory name, it doesn't work. I'm
Hello Petr,
In your example the original make command simply states that it should
switch to the example_dir and build an 'all' target there. It does not
specify how this target is build. That is the part that should end up in
your custom command. You can name the command 'examples', set
Hi,
this original makefile rule was probably just a simplification.
Make your custom target depend on all example targets which link the desired
parts, then you get what the original makefile author just didn't want to do
manually: having built all examples and their dependencies.
And it's less
Hi Micha.
I understand how the original works, and I know I can work around it with a
separate buildsystem (using e.g. ExternalProject_Add() or ctest
--build-and-test). I was just wondering: since CMake generates a .sln (or
Makefile) in the subdirectory (because I put a project() call in there),
No, I meant exactly what I said.
--target takes a CMake target name.
HTH,
D
On Fri, Dec 5, 2014 at 9:23 AM, Petr Kmoch petr.km...@gmail.com wrote:
I assume you actually meant 'cmake --build . --target example_dir', the name
of the directory. 'examples' is the name of the custom target; if
OK, sorry for misunderstanding. But then I don't have a target like this.
Basically, I am trying to create a custom target that would do this:
# When using Makefile generator
add_custom_target(
examples
COMMAND make -C example_dir all
VERBATIM
)
# When using vs2008 generator
Hi cmake-users,
I have the following setup:
CMAKE: 3.0.2
Visual Studio 2010
In one of my cmake files, I’m trying to create a preprocessor definition based
on the TARGET_FILE_DIR of a different target … so I’m trying this:
target_compile_definitions(my_target_B PUBLIC
Strangely, running cmake -DCMAKE_INSTALL_PREFIX=/some/path does NOT
rewrite the cmake_install.cmake, but does rewrite the CMakeCache.txt and
other files. The result is a bad install path won't go away until one
manually removes the cmake_install.cmake file(s).
On Thu, Dec 4, 2014 at 9:48 PM, J
Hi everyone,
I'm trying to add a .NET assembly reference to my CMake project. Various forums
on Google suggested to use /clr. The problem I've found, is that while CMake
sets the Common Language RunTime Support option in the C/C++ section of the
configuration properties if /clr is in the
To enable compiling as/with CLR...
SET_TARGET_PROPERTIES(bag PROPERTIES
COMPILE_FLAGS /CLR )
# need to set unicode characters...
add_definitions( -D_UNICODE -DUNICODE )
string( REPLACE /EHsc CMAKE_CXX_FLAGS_INIT ${CMAKE_CXX_FLAGS_INIT}
)
string( REPLACE /EHsc
Isn't it as smiple as
add_subdirectory( examples_dir ) which has it's own CMakeLists?
Does it really have to build as an extra step or would
OPTION( BUILD_EXAMPLES Build Examples? ON )
if( BUILD_EXAMPLES)
add_subdirectory( examples_dir)
endif( BUILD_EXAMPLES)
On Fri, Dec 5, 2014 at 7:41
This looks like a bug to me. I have a very simple test case where
CMAKE_INSTALL_PREFIX is set correctly if I do so after the project()
statement, and fails to be set correctly if I do it before the project()
statement.
On Fri, Dec 5, 2014 at 2:06 PM, Chris Johnson cxjohn...@gmail.com wrote:
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 677d66d06472560a5c9dedfec73e093ee40db2c6 (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 d13e65b3db32a6060b833e96024a1526998b63ea (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 f3f7acf67d013c432a610bea29d7d1b3b80a1150 (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 b2dde0459e93b316d1c9700a466b9fb78c0f1c4f (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 c00ead9f5516d9d84da5bf365bf9d8345e1d347b (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 03db9a061aa62eb2b373010a6a38d5707749a6d7 (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 3042e27a969b11b13a9e742e0b8d7ec662e0e350 (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 fad59f2dd12b72ec1b23b08a8bff7f0b296bb4b1 (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 f0fcb0b3883272097f98c16d3ae33f13511b5864 (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 ce28da6c64aba359b4399bca56ec60707a3d6073 (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, release has been updated
via eff4081bfbc7285ceeb5d6ec32a4f8682066cef6 (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 86777356c5ebfc43fbbf5aabceaeea02d6b3f84e (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 ad137b5af4f40f7c07df7da67684082c5e4a5012 (commit)
via
20141205)
+set(CMake_VERSION_PATCH 20141206)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
42 matches
Mail list logo
