Stephen Kelly wrote:
Ah, right the platform plugin issue. This is likely the reason for not
running on OSX.
CMake 3.1 learned a new feature specifically so that this would become
easier in the future:
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/7970
qmake generates a
Hi,
we use custom compiler flags for the default build types and our
solution works fine. However, when using the PGI Fortran compiler,
some initial flags are set in the module that are always there:
(/usr/share/cmake-3.1/Modules/Compiler/PGI-Fortran.cmake)
set(CMAKE_Fortran_FLAGS_INIT
Hi,
I am using Qt 5.3 (Angle on Windows) with CMake 2.8.12. Qt 5.3 has
dependencies on ICU and ANGLE libs. I wish to copy these dlls to the build
directory. Is there any CMake variable that holds name of ICU and ANGLE
libs?
To copy other Qt libraries I am using the following sample code
Alexander Neundorf wrote at 21:34 +0100 on Feb 9, 2015:
On Monday, February 09, 2015 18:23:41 44ghnqv...@snkmail.com wrote:
How does one who is making a package which installs .cmake files
decide whether to put them in .../share/cmake/Modules or
.../lib/cmake? Where are the docs about
I want to thank Rolf here for his advice because I failed to
do so in an off line reply.
Shortly after I replied to Rolf's note, I received notification from
IBM that the problem is related to our version of GPFS (4.1.0-2).
Versions 4.1.0-3 and later apparently do not have the
System: RHEL6 (2.6.32-504.8.1.el6.x86_64)
Hardware: Various cluster nodes.
We recently deployed GPFS storage and have discovered that
Cmake fails when writing to files in the GPFS storage. The source
of the problem, identified by using strace(1), appears to be a NULL
pointer in
P. A. Cheeseman wrote:
System: RHEL6 (2.6.32-504.8.1.el6.x86_64)
Hardware: Various cluster nodes.
A C code with explicit writev() calls, with a NULL pointer in
the first iovec entry, also reproduces the behavior. When the
NULL is part of any entry other than the first, the
Phil,
Could you give me a ticket or bug number (however they track it) for GPFS
that describes this as a known bug? I will need that when submitting a
ticket to my organization's helpdesk. This problem is quite a lot larger
than CMake: all C++ programs will break.
Sincerely,
Sam Trahan
On
Reading into the final resolution of the IBM ticket tipped me to where the
writev() calls originate in the C++ run-time. The amount of data has to be 1K
or more before writev() is used. Then the NULL pointer in the iovec is assured
with our versions of Gcc/G++. I've just compiled and
On Tuesday, February 10, 2015 03:43:33 44ghnqv...@snkmail.com wrote:
Alexander Neundorf wrote at 21:34 +0100 on Feb 9, 2015:
On Monday, February 09, 2015 18:23:41 44ghnqv...@snkmail.com wrote:
How does one who is making a package which installs .cmake files
decide whether to put them
Does anyone know of a workaround for this which does not require upgrading
GPFS or changing compilers?
On Tue, Feb 10, 2015 at 2:24 PM, P. A. Cheeseman a...@purdue.edu wrote:
I want to thank Rolf here for his advice because I failed to
do so in an off line reply.
Shortly after I
I am attempting to run CMake and use clang for the compiler. I am on
Windows 8.1. It seems to me that if CMake used gcc flags instead of vc++
flags that this would work. Any ideas how I can make this work?
I use the following command:
cmake -DCMAKE_C_COMPILER=clang.exe
Do you intentionally removed or just forgot to CC the list?
I failed to 'reply-all'.
One additional note. Turning off optimization didn't help, among
the other things I tried.
My own read of the issue is that there is room to trap the bad
pointer at every layer in its handling.
Here's a start. If I post to GNU/RedHat, I'll pass that along too.
http://www-01.ibm.com/support/docview.wss?uid=isg3T1021392
I understand the problem is bigger. It's helped me to understand why I'm
having problems with C++ support for other packages. I'm still
Hi All,
While installing cmake using below option, I am facing the error in step 3.
Step1: ./bootstarp
Step2: make
step: make install
Error after step 3:
*CMake Error at cmake_install.cmake:36 (file): file INSTALL cannot set
permissions on /usr/local/doc/cmake-3.1/Copyright.txt*
How to
Try running:
sudo make install
Instead.
On Feb 10, 2015, at 7:45 AM, Gunjan Gautam
gunjan.gemin...@gmail.commailto:gunjan.gemin...@gmail.com wrote:
Hi All,
While installing cmake using below option, I am facing the error in step 3.
Step1: ./bootstarp
Step2: make
step: make install
Error
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 d46e1e3f0fa386638b5a50b45783f4ec4d94bf2c (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 0b8d9581c0a651f36fc5a2d0b996fd006152ce50 (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 f69ce957afe5631e73f2130c725474e651813623 (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 c2edefc15ec1f2c13c64ac0b999caf1fd23f029f (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 eb8acf85d0e49c8b5f5e291cab043028dd979fac (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 5367c0e4781644a33ce9163666a626e50efffa2c (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 0f422f38cb7532af36b6d0a080dcf5ef4ff77748 (commit)
via
On 02/10/2015 07:56 AM, Robert Maynard wrote:
So we can safely presume that the new features listed at
https://gcc.gnu.org/gcc-5/changes.html will be the what gcc 5.0 will
ship with?
That's how I read things.
On Mon, Feb 9, 2015 at 11:18 PM, Orion Poplawski or...@cora.nwra.com wrote:
On
On 02/09/2015 12:17 PM, Ruslan Baratov via cmake-developers wrote:
This patch let do the check that exit code is 0, i.e. install_name_tool
exits successfully.
Applied with minor refactoring:
BundleUtilities: Teach fixup_bundle to check install_name_tool result
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 fa1af50e9bbe0506da14019b82cbc86fd1333e02 (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 4267f43d15cd42040773c620781ab8f7926f343b (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 06e527b36ccb86078e0caad2cd2962057b0c0558 (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 c548ddc1724c9c96bab04d2f51d1740360bcb737 (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 80c080052a123b71b69bf42fa99e01df621502bb (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 5b19ac52bb4db11dd932c2f522cdda25a19a2ba3 (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 db9a2e8966256d50efcd593a20ed8a2b8b9cc05e (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 1d6f4b6fcc04620fd5f8e090381e8330dc2a4b23 (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 f2ae132d96e36b856f91da499800d58efc37ccf5 (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 2681102e08a5a1f3615ee0c7717e7569ee460e25 (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 e2619c13f727504b7368e0bf156c17112ee81568 (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 57c6574b35a3d533e47cc8c2be131c46d2b30a99 (commit)
via
On 02/06/2015 09:10 PM, Michael Smith wrote:
On Fri, Feb 6, 2015 at 4:42 PM, Ben Boeckel wrote:
Doesn't work for cross-compiles.
FindRuby is already querying ruby for libdir. How does that work
for cross-compiles but using some of the other config doesn't?
That one doesn't work either, but
On 02/06/2015 06:00 PM, Michael Smith wrote:
New patch attached.
Applied, thanks:
FindRuby: Fix finding 64-bit Ruby on Windows
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e5ef9271
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
So we can safely presume that the new features listed at
https://gcc.gnu.org/gcc-5/changes.html will be the what gcc 5.0 will
ship with?
On Mon, Feb 9, 2015 at 11:18 PM, Orion Poplawski or...@cora.nwra.com wrote:
On 02/09/2015 11:08 AM, Ben Boeckel wrote:
On Mon, Feb 09, 2015 at 11:09:32
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 8926a09dd37e32502f0ed82b5b84dda9ce686d82 (commit)
via
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15400
==
Reported By:Ruslan Baratov
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 a06bd9fdc9c2ac5a921f6836454fc13c7523d060 (commit)
via
On Tue, Feb 10, 2015 at 17:15:33 -0800, Alan W. Irwin wrote:
As the originator (almost 6 years ago) of this bug report I am still
very much interested in a fundamental solution to give a WARNING
message rather than an error if there is any issue with a compiler.
This patch makes it only an
On 2015-02-06 10:21-0500 Ben Boeckel wrote:
On Fri, Feb 06, 2015 at 07:01:55 +0100, Christoph Grüninger wrote:
would you mind to tackle issue 9220 enable_language( OPTIONAL)
signature does not work correctly? It's a shame that CMake cannot
properly detect optional Fortran for more than 5
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15401
==
Reported By:Wojciech A. Koszek
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 17fef0dae571e0f745c3dd14facd90e68cf8c9db (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 a0272926fcd2ff20b26092c789dd6ae9538fc5e5 (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 5e36f8ee1ebf4538146f9f0cb5974426eac14249 (commit)
via
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15399
==
Reported By:Florent
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 6818ee67a5b1f81e3e5b7db36a49774d3dde8c99 (commit)
via
On Fri, Feb 06, 2015 at 13:15:45 -0500, Ben Boeckel wrote:
Looks like compiler_feature_detection will need to normalize the
_GLIBCXX_USE_CXX11_ABI preprocessor define as well:
http://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/
Followup (LWN comments will likely have
20150210)
+set(CMake_VERSION_PATCH 20150211)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
I've finally had some time to read over the Tests section, and it is a
bit overwhelming.
I'm going to describe the use cases for my patch and perhaps you can
give me some guidance on adding an actual test.
There are three, maybe four use cases:
1) native rpm (e.g. x86_64)
2) noarch rpm (a noarch
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 fd2cc9a1071279c0e3d41c38d670d0e669ab92bb (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 2fd44b082b0a8e546c73d921f9d8264a668c3b78 (commit)
via
On 02/07/2015 05:23 PM, Nuno Sucena Almeida wrote:
---
bootstrap | 8
1 file changed, 8 insertions(+)
Thanks, applied:
bootstrap: Add --sphinx-qthelp option to enable qthelp doc generation
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=85fd62ee
-Brad
--
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 db0f1df7bada28ea675fb563803786e7251c42b9 (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 03d60ba97b9790ec80a22be5b51d91492235a11f (commit)
via
On 02/09/2015 05:14 PM, Domen Vrankar wrote:
To get around this problem I thought about wrapping the entire script with:
cmake_policy(PUSH)
cmake_policy(VERSION 3.1)
cmake_policy(POP)
Would this be an acceptable solution?
That is currently the intended way to do it.
There was once some
60 matches
Mail list logo
