The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15556
==
Reported By:Kjell Irgens
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 3b2929cd2d253b02f88112943db9b19b5ff81a9f (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 dcce21d77e98066a420e28a253f112443002e8d0 (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 dd08530978146a806014c6778f472db667899378 (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 ea1db6c43d9709169525ee481670e187b7293273 (commit)
via
My need is the following:
I have two imported targets, let say, IMPORTED::TARGET and
IMPORTED::STATIC::TARGET
And I have a project which can be customised, through an option, by selecting
which imported target will be used (shared or static).
So I tried, at first place:
if
Hello,
I try to create my first FindXXX.cmake and use find_package inside.
My goal is to check that a repository exists: it's always the same because it
come from the ExternalProject_add command.
However, I don't manage to write a first very simple version.
I can't find the path I want.
I
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 6a6fae9caf7d70999db96e4317e62859a53dd5d4 (commit)
via
On 05/04/2015 03:07 PM, Robert Goulet wrote:
Here's a patch that include the docs and the test.
Applied with minor tweaks, thanks:
VS: Add option to put INSTALL target in .sln default build
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a6e4e73d
-Brad
--
Powered by www.kitware.com
Hi,
I have serious problems in installing OpenCV 2.4 on my Ubuntu Linux machine
(Linux 2.6.32-24-generic #43-Ubuntu SMP ... x86_64 GNU/Linux).
Firstly I use cmake as below:
cmake -D CMAKE_INSTALL_PREFIX:PATH=/pathwherebuilding /path-to-source
Secondly I use make but there are the following
Hi,
I'm trying to get my head around CMake config files to use in combination
with find_package.
So currently I have a given library target setup.
Then I call a configure_package_config_file to generate some
TargetConfig.cmake.
After that I call an export on the target.
The files are generated
Hi,
The search path rule #5 reads:
Search project build trees recently configured in a cmake-gui(1). This can be
skipped if
NO_CMAKE_BUILDS_PATH is passed. It is intended for the case when a user is
building
multiple dependent projects one after another. (This step is implemented only
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 ffd4c588ef0e205f665f19e1bc9ad241cc757061 (commit)
via
On Wed, May 06, 2015 at 13:53:42 -0400, Brad King wrote:
On 05/05/2015 04:11 PM, Ben Boeckel wrote:
Does anyone have any issue with remove `-i` from the implicit flags from
makefile generators with the build command (ctest_build)?
We can change it with explicit options to the relevant
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 583be259f60d03db0b74905e4905f93db1bf7cc4 (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 86d8b40eac87b4b62510761d0d05782cc880e4d3 (commit)
via
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15558
==
Reported By:jest
Assigned To:
On Wed, May 06, 2015 at 11:15:55 -0400, Brad King wrote:
On 05/05/2015 05:44 PM, Ben Boeckel wrote:
Should CMakeConfigurableFile.in have a trailing newline?
Prior to a fix in CMake 3.1:
CMakeConfigurableFile: Remove excess newline.
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15557
==
Reported By:trsystran
Assigned To:
On 05/05/2015 04:11 PM, Ben Boeckel wrote:
Does anyone have any issue with remove `-i` from the implicit flags from
makefile generators with the build command (ctest_build)?
We can change it with explicit options to the relevant commands and
also add a policy to change the default (leaving the
On 05/06/2015 01:29 PM, Ben Boeckel wrote:
file(GENERATE) does not document its newline behavior (nor does it have
options for setting it at all). Does it write in text or binary mode?
From the source it looks like it opens without the ios::binary flag.
One could consider adding a similar set
20150506)
+set(CMake_VERSION_PATCH 20150507)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
On 05/05/2015 05:44 PM, Ben Boeckel wrote:
Should CMakeConfigurableFile.in have a trailing newline?
Prior to a fix in CMake 3.1:
CMakeConfigurableFile: Remove excess newline.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e2f09aff
it actually had *two* trailing newlines.
at least some
On 05/05/2015 04:57 PM, Robert Goulet wrote:
This is a major issue because when building with msbuild.exe,
specifying a target project will not respect the rules set in
the solution file, which might have some projects disabled by
the EXCLUDE_FROM_DEFAULT_BUILD cmake target property.
The VS
Well, it's just that it makes it cleaner in our build script to simply invoke
cmake to build, instead of doing per-platform code. This is much cleaner.
Anyway I still believe we should be able to tell cmake to build the visual
studio solution without specifying a target. That's just basic
On 05/06/2015 11:12 AM, Robert Goulet wrote:
Well, it's just that it makes it cleaner in our build script to
simply invoke cmake to build, instead of doing per-platform code.
Adding a special argument to cmake --build to tell it to build
the solution file will also be platform-specific code.
Hello.
When I tried to use the write_compiler_detection_header() function, I
got the following error:
write_compiler_detection_header: FILE parameter missing.
Apparently on line 250 of WriteCompilerDetectionHeader.cmake, CMake
was parsing FILE as a variable instead of a string. Wrapping FILE
27 matches
Mail list logo
