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 8895f113237afaa09e8964ad30f45702bfd5cdf3 (commit)
via
On 2016-02-09 13:50-0500 Brad King wrote:
On 02/09/2016 01:00 PM, James Bigler wrote:
Will changes integrated into master automatically be slated for either
v3.5.0 RC2 or v.3.5.0 final?
No, the development window for 3.5 closed on Feb 1:
On 02/09/2016 02:39 PM, Alan W. Irwin wrote:
> So what branch should we follow if we want to test the on-going 3.5.x
> effort?
>
> I assumed it would be "release"
Yes. I just merged several of the fixes there this morning.
> but one of the key fixes to 3.5.0-rc1 is the efficiency one
[snip]
>
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15962
==
Reported By:nitroamos
Assigned To:
On Tue, Feb 9, 2016 at 10:15 AM Gilles Khouzam
wrote:
> I'm trying to understand what is necessary to make this work. I'll circle
> back when I find out more information.
>
> -Original Message-
> From: Brad King [mailto:brad.k...@kitware.com]
> Sent: Monday,
>
> > + math(EXPR Protobuf_MAJOR_VERSION "${Protobuf_VERSION} / 100")
> > + math(EXPR Protobuf_MINOR_VERSION "${Protobuf_VERSION} / 1000 % 1000")
> > + math(EXPR Protobuf_SUBMINOR_VERSION "${Protobuf_VERSION} % 1000")
>
> Would string manipulation be better here?
I don't know how to make
>
> On 02/08/2016 04:24 PM, Antonio Pérez Barrero wrote:
> > Yes, it is possible, but currently it's not looking for the debug
> > library with a different name, just in a different path that is
> > unlikely to exist in a Unix system.
>
> The fact that a separate find_library is called for it and
Hello,
The FILE(COPY) command displays an incorrect error message when its
argyument is empty:
$ cat >x.cmake
FILE(COPY "" DESTINATION ".")
$ cmake -P x.cmake
CMake Error at x.cmake:1 (FILE):
file INSTALL encountered an empty string input file name.
INSTALL should obviously be COPY. This
Am 09.02.2016 11:10, schrieb Antonio Pérez Barrero:
On 02/08/2016 04:24 PM, Antonio Pérez Barrero wrote:
> Yes, it is possible, but currently it's not looking for the debug
> library with a different name, just in a different path that is
> unlikely to exist in a Unix system.
The fact that a
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 0de8af011e69b31d2c67cca890cff301ad22ad0f (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 656bf0da2c0b9a2fa6e79970df968d5e9c4e4e1a (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 dfa01fd005502cf8d80d007bb42d21e2817d4d73 (commit)
via
I'll say that in my line of work, we still have to support OS X 10.6
(just dropped 10.5 support) .. And we're doing this at Apple's own
request/demand! It's not fun. I've had to hack tools around to get
somewhat newer tool chains to continue to work, but it's been /great/
that cmake hasn't
Hi,
I'm a long time user of CMake (and huge fan of it) but newly registered on
this list, so please forgive me if I have missed something regarding the
new 3.5 series.
I use CMake with the GCC ARM Embedded compiler (
https://launchpad.net/gcc-arm-embedded) to cross-compile my project
(Windows
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 8aec0f955a5e6a11cea6004a31fbe88760db939f (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 e509c0e6d47510940d4282bf46b583ac15ab033d (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 16f83f648a1ef75a66a5b07deec55c6e6e65b0d3 (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 a887c7f1fd97d9ebf88b294105e81acf5963fc25 (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 686b52d714b059aeecbf1a835f6eafa50943b0f8 (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 7b53e8c6a52d64768774608116f6c5cc72d1e0b1 (commit)
via
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15961
==
Reported By:raffael casagrande
Assigned To:
Hi,
I myself use statements like:
list( INSERT CMAKE_MODULE_PATH 0 ${CMAKE_SOURCE_DIR}/modules )
at the beginning of my main CMakeLists.txt file, and it works exactly as one
would expect. I also override some CMake provided modules like this.
Cheers,
Attila
> On 08 Feb 2016, at
Hi,
Am 9. Februar 2016 13:36:03 MEZ, schrieb Gerhard Pobinger
:
>I'm trying to include legacy Visual Studio projects into a cmake
>generated
>solution like this:
>
>project(Crypto)
>
>include_external_msproject(${PROJECT_NAME}_vcproj
>
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 236133f1fb460880cb87c7ed48f2be81bd197cb2 (commit)
via
I should also have mentioned that we're supporting a number of other
platforms at the same time.. hence our use of cmake. And would rather
not have to maintain cmake files that are lowest-common-denominator for
the version of cmake that has to continue working on OS X 10.6
On 02/09/2016
Hi Thibault,
Can you post your toolchain file?
- Chuck
On Tue, Feb 9, 2016 at 9:10 AM, Thibault Genessay
wrote:
> Hi,
>
> I'm a long time user of CMake (and huge fan of it) but newly registered on
> this list, so please forgive me if I have missed something regarding the
>
I'm trying to understand what is necessary to make this work. I'll circle back
when I find out more information.
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Monday, February 8, 2016 10:32
To: Yi-Hong Lyu
Cc: cmake-developers@cmake.org;
Hi Thibault,
Thanks for trying the release candidate!
On 02/09/2016 09:10 AM, Thibault Genessay wrote:
> I installed 3.5 and the build broke
While CMakeForceCompiler is deprecated we think it should still work
in most cases where it worked before, just with a warning. What
actually breaks?
>
On 02/08/2016 10:35 AM, Alin Marin Elena wrote:
> I was playing to day with FeatureSummary and Fortran and I discovered the two
> do not like each other too much . While MPI is obviously found in here...
> Feature summary claims it did not
>
> -- Found MPI_Fortran:
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15963
==
Reported By:Bruce Adams
Assigned To:
On 02/09/2016 01:00 PM, James Bigler wrote:
> Will changes integrated into master automatically be slated for either
> v3.5.0 RC2 or v.3.5.0 final?
No, the development window for 3.5 closed on Feb 1:
https://cmake.org/pipermail/cmake-developers/2016-February/027637.html
-Brad
--
Powered by
I ran into a problem recently where a project I was building set a SYSTEM
include directory which was already a non-SYSTEM include directory imported
from a dependency. When this happened, CMake dropped the non-SYSTEM
directory in favor of the SYSTEM one, causing my build to fail.
Should this be
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 57d546cf95daa5b5187d47697b9476feca4a146d (commit)
via
The Daemon mode for CMake is online here:
https://github.com/steveire/CMake/tree/cmake-daemon
The commit messages and some of the commits contain indications of things
that need to be done before such a mode could be introduced into CMake, such
as writing a new failsafe parser and
Stephen Kelly wrote:
> Tamás Kenéz wrote:
>
>> That's great and really does open a new world for IDEs!
>
> Thanks! Let's see if the interest grows.
>
> I've just pushed the daemon code here:
>
> https://github.com/steveire/cmake/tree/cmake-daemon
Tobias made a pull request there. Rather
Stephen Kelly wrote:
> Hi,
>
> I just made a blog and video about the advanced features and possibilities
> that a daemon mode for CMake can bring:
>
> https://steveire.wordpress.com/2016/01/24/cmake-daemon-for-user-tools/
>
The lack of response on the list to any of this is quite
In order to make it possible to implement fully featured user tools like the
cmake daemon
https://steveire.wordpress.com/2016/01/24/cmake-daemon-for-user-tools/
... and to make it possible to use multiple toolchains at once
_VERSION_MINOR 5)
-set(CMake_VERSION_PATCH 20160209)
+set(CMake_VERSION_PATCH 20160210)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
Hi,
I am using cmake 2.8.12.2, and I'm getting this warning when I attempt to
link a fortran program or library.
ifort: command line remark #10148: option 'i_dynamic' not supported
I cannot find very much about this error searching the web. What does this
mean?
Thanks
--
Powered by
Will changes integrated into master automatically be slated for either
v3.5.0 RC2 or v.3.5.0 final?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For
40 matches
Mail list logo