http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/devel/cmake/patches/patch-b
ootstrap?rev=1.7content-type=text/x-cvsweb-markup
They just want to bootstrap with Ninja, except on specific
architectures. Not an upstream concern.
Yes, because:
XXX: broken on arm and m88k
It's the same as with
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 7589b5fe25daa4fc154ae0ea6999e6e89f7d1bdb (commit)
via
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15363
==
Reported By:Moshe Rubin
Assigned To:
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 a75bb8377e228107917135b06a1af42aec1ecd52 (commit)
via
Hello.
I am trying to use a specific version of cmake (v2.8.8). I also need ccmake
(v2.8.8). I located the folders uploaded for this release. I plan to use it
on ubuntu. I downloaded cmake folders and extracted all the folders related
to Linux. However, only one folder has options to build from
Thanks for your help so far. Your 3rd command produced the output
below. I'll keep looking into this but just wanted to share. I'm not
sure why it isn't working, and I'm not completely familiar with linux
development so it will take me a while to figure this out.
robert@robert-OptiPlex-745 ~ $
Hi,
This makes cmake --build much less predictable across cmake versions and cmake
projects.
How can I find out if msbuild is chosen without inspecting the cmake project?
Specifying this manually is not really an option... too complicated.
Or like that:
- run CMake
- get the CMAKE_VS_MSBUILD...
This is a pre-built Linux binary that should work on that system, and
should include ccmake:
http://www.cmake.org/files/v2.8/cmake-2.8.8-Linux-i386.tar.gz
If you can't run it, it's probably because you're on an x64 box, and
you need the run the 32-bit exes and libs library -- hopefully
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 6a5da86d1eb53526ad48724cae6ce23151f56e0e (commit)
via
On 01/21/2015 03:19 PM, Andrew Seidl wrote:
Here's a small patch for FindCUDA for finding the new cuSOLVER
library included in the upcoming CUDA 7.0.
Applied, thanks:
FindCUDA: Add cuSOLVER library from CUDA 7.0
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e56c9327
-Brad
--
Powered
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 7f7c996a707e206c8cd87bb97689b77ad249e114 (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 fcf07b5ac180c78f5d88d3aebad2120844a2e841 (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 45049eca97e8931721f4a371e136a012c0473e8d (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 c709ebb08e675fc4603187cd8a125a6b8f704436 (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 42eb85d6c7bfac664fee8df62bf0ccb84b8e4e5c (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 40c11f0f62af1365cee44111429946862b5cf93f (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 afd998373da0d0c39266b5c7a078ee48aa939554 (commit)
via
Hi all,
Here's a small patch for FindCUDA for finding the new cuSOLVER library
included in the upcoming CUDA 7.0.
Andrew
0001-FindCUDA-add-cuSOLVER.patch
Description: Binary data
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
Hi all,
Any Vim users out there who would like to try out the changes I've made
to the Vim files shipped with CMake can grab it from either stage
(vim-support-overhaul) or my GitHub fork[1]. It is not in next yet since
I expect further changes to come and that would only make unnecessary
churn on
On 01/21/2015 12:01 PM, Raffi Enficiaud wrote:
Ok. What do you think about mimicking the mex compiler in terms
of options set to the compiler? The -Wl,--exclude-libs,ALL is in
fact set by the mex compiler for compiling the mex extensions under
Linux. Then I will just drop the REDUCE_VISIBILITY
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 c2650e5588c8ce19ffbc3f861ce19f033c2eede3 (commit)
via
20150121)
+set(CMake_VERSION_PATCH 20150122)
#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 1c175147e32341d5a9bf4c54fc8ea7cd9831c31c (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 65ebdf17ae3f463dd10862a4f1bec017f2c15cb5 (commit)
via
Greetings,
Can I add a variable, was set before, to add_executable ?
set(PROJ_NAME Test01)
,,,
file( GLOB ${PROJ_NAME}_SRC *.h *.cpp )
add_executable( ${PROJ_NAME} ${PROJ_NAME}_SRC)
...
error in add_executable(..)
Any help is appreciated.
Best Regards,
Joshua Robinson
--
Powered by
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 b6aa7393f5501c658afc1c83001fcecec7a86e7a (commit)
via
Is there any builtin CMake support for compiler independent support for
pre-compiled headers?
I have found a couple of hacks out there for MSVC, and some for gcc.. but
nothing that is all inclusive, and frankly none that look up to the quality of
CMake :)
Scott
--
Powered by
2015-01-22 3:41 GMT+01:00 Joshua Robinson shooki.robin...@gmail.com:
Greetings,
Can I add a variable, was set before, to add_executable ?
I guess yes. However if PROJ_NAME value was used in
project(Test01 C CXX)
then there may be a conflict between project name and a target name
Ok, so it all seems to boil down to the following:
- 2.8.12: cmake --build uses devenv to build, which in turn picks
up a setting (maximum number of parallel project builds) from the VS
IDE at build time. As this was set to 8 on my machine, by default the
build used parallellization with 8 cores
I am not sure what else it could be.
Here are some queries I did on my system where it seems to be working;
perhaps it will help you backtrack the issue:
Ubuntu 14.04.1 LTS (64-bit)
# gcc --version :
gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2
# clang --version :
Ubuntu clang version 3.4-1ubuntu3
Hi,
it should also not work when you build a test project in release mode and then
in the build directory type cpack -G ZIP for example. (Without the -C option)
In the CTestScript is also added the -C option to ensure it uses the release
mode, but it doesn't work either.
When you then open
On 01/20/2015 02:44 PM, Gregor Jasny wrote:
Do you plan to make this patch available in 3.1.1 release?
Yes. It's already been backported to the 'release' branch:
Xcode: Do not require code signing for compiler id (#15214)
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7b7209f6
and 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 ca646585aa25396915e4ac0411c2e166abe24c6d (commit)
via
Unfortunately, that is not what I've found. There are libraries we build
that have their own target_link_libraries, and if these libraries are used
on the target_link_libraries for an executable, its dependencies are also
pulled into the executables link line. This is expected, handling of
On 01/20/2015 03:40 PM, Paul Smith wrote:
Where can I go to find out more about how cmake --build chooses whether
to use msbuild vs. devenv?
The behavior was updated in 3.0 and is now described here:
http://www.cmake.org/cmake/help/v3.0/variable/CMAKE_MAKE_PROGRAM.html
In 2.8.12 and below we
35 matches
Mail list logo
