Stephen Kelly wrote:
It can probably be refactored to bypass the genex evaluation though.
The refactoring I described can be done in the future I think, but doesn't
really solve the bug anyway, because it is evaluation of the generator
expression for the target itself which is causing
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14119
==
Reported By:Shimon Doodkin
Assigned To:
I created a topic called WindowsFormsResx following the developer
guide instructions and have committed my staged changes and a test
project. I don't know how to send out a link to this, but would be
happy to do so if someone pointed me in the right direction.
- John
On 2013-04-28 20:46,
On 04/29/2013 06:29 AM, Stephen Kelly wrote:
I've force-pushed the fix-multi-config-tll-include-dirs branch with a more-
simple fix for this issue to my clone.
Okay, that looks good. Please rebase on the partial fix I merged last
week so we can test it in 'next'. I'll squash all that together
Hi John,
Seems your topic isn't available on the CMake stage:
http://cmake.org/gitweb?p=stage/cmake.git
I would suggest you push your topic on github instead. The stage is used by
module maintainer or CMake core developers [1]
Hth
Jc
[1]
Done and Pull Request sent. Visual Studio C++ Windows Forms Designer
Support
Thanks. I look forward to helping this get into the CMake baseline!
- John
On 2013-04-29 08:08, Jean-Christophe Fillion-Robin wrote:
Hi John,
Seems your topic isn't available on the CMake
stage:
On Sunday 28 April 2013, Rolf Eike Beer wrote:
One question I see increasingly often is how do I test for C++11 support
or for specific parts of that. For 2.8.12 I plan to include the check
module I wrote for that a while back, and that I have reworked in the last
weeks. You can find the
On Thursday 18 April 2013, Alexander Neundorf wrote:
Hi,
attached are two patches for ctest and cdash from Volkan (on CC).
They are not ready for inclusion, but before we continue to work in this,
we'd like to get some comments whether this is a good idea, the right
approach, etc.
So, here
Hi,
in automoc, for every target foo a foo_automoc target is created, and for each
of those a file foo_automoc.cpp is created.
When this file does not exist, automoc reruns and all moc files should be
regenerated.
To achieve this, I added this file in cmQtAutomoc.cxx to the
On 04/29/2013 03:05 PM, Alexander Neundorf wrote:
Now after some emails on the cmake list, it seems ADDITIONAL_MAKE_CLEAN_FILES
is used only by the Makefile-generators, but not by e.g. the VS generators ?
VS does its own cleaning of the build outputs it knows.
The target is created using
Alexander Neundorf wrote:
On Sunday 28 April 2013, Rolf Eike Beer wrote:
One question I see increasingly often is how do I test for C++11 support
or for specific parts of that. For 2.8.12 I plan to include the check
module I wrote for that a while back, and that I have reworked in the last
On Monday 29 April 2013, Rolf Eike Beer wrote:
Alexander Neundorf wrote:
On Sunday 28 April 2013, Rolf Eike Beer wrote:
One question I see increasingly often is how do I test for C++11
support or for specific parts of that. For 2.8.12 I plan to include
the check module I wrote for that
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14121
==
Reported By:Nils Gladitz
Assigned To:
On Monday 29 April 2013, Brad King wrote:
On 04/29/2013 03:05 PM, Alexander Neundorf wrote:
Now after some emails on the cmake list, it seems
ADDITIONAL_MAKE_CLEAN_FILES is used only by the Makefile-generators, but
not by e.g. the VS generators ?
VS does its own cleaning of the build
Hello, we want to use the Visual Studio IDE with the Intel C++ compiler. The
Intel compiler integrates neatly with the IDE, you right click on a project or
solution and select use Intel C++ or use Visual C++ to switch between
compilers. I have added the following option to our CMake file:
I added these lines:
set_directory_properties(
PROPERTIES ADDITIONAL_MAKE_CLEAN_FILES
${CMAKE_CURRENT_BINARY_DIR}/abc.txt
)
# check the location where abc.txt is supposed to be deleted from
message(CURRENT_BINARY_DIR: ${CMAKE_CURRENT_BINARY_DIR})
to the end of my CMakeLists.txt and then
Hi all,
I noticed that FindCUDA.cmake fails to locate libcuda.so on at least two
different platforms: Ubuntu 12.10 and CentOS 6.3 using Cluster Manager
v5.2. I can persuade FindCUDA.cmake to search for this library by
explicitly setting the environment variable CUDA_LIB_PATH, and then it
Can you provide what Cuda version FindCuda is failing to find, and
where Cluster Manager is installing the CUDA toolkit and library?
On Mon, Apr 29, 2013 at 7:38 AM, Marcel Loose lo...@astron.nl wrote:
Hi all,
I noticed that FindCUDA.cmake fails to locate libcuda.so on at least two
different
Hi,
It fails to find CUDA 5.0. See below.
$ env | grep CUDA
CUDA_PATH=/cm/shared/apps/cuda50/toolkit/5.0.35
CUDA_INC_PATH=/cm/shared/apps/cuda50/toolkit/5.0.35
CUDA_SDK=/cm/shared/apps/cuda50/sdk/5.0.35
CUDA_CACHE_DISABLE=1
CUDA_INSTALL_PATH=/cm/shared/apps/cuda50/toolkit/5.0.35
Any idea on this? Or should I file a bug report?
On Mon, Apr 22, 2013 at 3:15 PM, Petr Kmoch petr.km...@gmail.com wrote:
If you look at the trace, you'll see the following few lines before the
error:
C:/Program Files (x86)/CMake
2.8/share/cmake-2.8/Modules/FindQt4.cmake(738):
Hi,
I read the content of the change in the link you provided, and I have a
newbie question:
Why not using one timestamp (different filename) per library/binary/project
?
Looking forward to having this issue solved in the next official release!
Best,
Raffi Enficiaud
--
View this message in
You have a nonstandard install path that will require you to use
CUDA_PATH / CUDA_BIN_PATH and CUDA_LIB_PATH.
On Mon, Apr 29, 2013 at 10:10 AM, Marcel Loose lo...@astron.nl wrote:
Hi,
It fails to find CUDA 5.0. See below.
$ env | grep CUDA
CUDA_PATH=/cm/shared/apps/cuda50/toolkit/5.0.35
Hi Robert,
I agree that on the CentOS machine the install paths are non-standard.
For the Ubuntu system, on the other hand, I have to disagree with that
statement. It is a *standard* Ubuntu 12.10 system, so IMHO
FindCUDA.cmake should be able to locate libcuda.so on that system.
Regards,
I have had no problem with Ubuntu 12.10 and Cuda 5; findCuda is able
to find cuda in /usr/lib. Can you run CMake --debug-output output
enable and see where findCuda is searching?
On Mon, Apr 29, 2013 at 11:52 AM, Marcel Loose lo...@astron.nl wrote:
Hi Robert,
I agree that on the CentOS
On Monday 29 April 2013, Glenn Coombs wrote:
I added these lines:
set_directory_properties(
PROPERTIES ADDITIONAL_MAKE_CLEAN_FILES
${CMAKE_CURRENT_BINARY_DIR}/abc.txt
)
# check the location where abc.txt is supposed to be deleted from
message(CURRENT_BINARY_DIR:
On 04/29/2013 10:53 AM, Raffi Enficiaud wrote:
I read the content of the change in the link you provided, and I have a
newbie question:
Why not using one timestamp (different filename) per library/binary/project?
The current approach evolved historically. A per-target approach would
Hi,
On Friday 19 April 2013, Robert Maynard wrote:
The CMake 2.8.11 release candidate continues. This is the last RC
unless a critical, must-fix issue is found. You can find the source
and binaries here:
http://www.cmake.org/files/v2.8/?C=M;O=D
what is the current plan, will there be another
Hi.
I've always thought one of the main objectives of cmake was being
portable, right?
So I was looking for a way to let the user (i.e. the person building a
project) choose how he wan't to link each external library (i.e. not
the ones built as targets by my project), depending on what that lib
On Mon, Apr 29, 2013 at 11:13 AM, Philippe Cerfon philc...@gmail.comwrote:
Hi.
I've always thought one of the main objectives of cmake was being
portable, right?
So I was looking for a way to let the user (i.e. the person building a
project) choose how he wan't to link each external library
Hi,
We found a bug in rc3 and are waiting for the fix to be finalized
before we make rc4. You can
track the bug by following the 2.8.11-rc3 generator expression error thread.
On Mon, Apr 29, 2013 at 2:00 PM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
Hi,
On Friday 19 April 2013, Robert
On Mon, 2013-04-29 at 14:53 -0400, Robert Maynard wrote:
We found a bug in rc3 and are waiting for the fix to be finalized
before we make rc4. You can track the bug by following the 2.8.11-rc3
generator expression error thread.
I haven't seen any action on that thread since Thursday... the
On Mon, Apr 29, 2013 at 8:30 PM, Ian Monroe i...@monroe.nu wrote:
Static linking of external libraries is just a weird thing to do.
And I thought this wasn’t lkml, where it’s perfectly fine that people,
instead of answering the question (if they choose to answer at all)
tell you your use case
On Monday 29 April 2013, Philippe Cerfon wrote:
Hi.
I've always thought one of the main objectives of cmake was being
portable, right?
So I was looking for a way to let the user (i.e. the person building a
project) choose how he wan't to link each external library (i.e. not
the ones built
Hi Brad,
Thank you for your reply.
As you pointed out, the problem seems to come from a race condition on the
file generate.stamp. Now the operations being atomic, the problem should
be solved, in practice.
However, I do not fully understand in what extent the atomicity of renaming
a file would
For example:
https://github.com/commontk/CTK/blob/ac13c32312c9160190b80bd3a03d012782eff40c/Libs/Core/CMake/ctkMacroBFDCheck.cmake#L33-43
Hth
Jc
On Mon, Apr 29, 2013 at 4:36 PM, Alexander Neundorf a.neundorf-w...@gmx.net
wrote:
On Monday 29 April 2013, Philippe Cerfon wrote:
Hi.
I've
On 04/29/2013 04:37 PM, Raffi Enficiaud wrote:
- process 1 is accessing generate.stamp for reading
Nothing ever reads the file. Only its existence and modification
time matter.
- process 2 is moving some tmpfile to generate.stamp - race
The only race was for multiple processes simultaneously
For reference I have opened a new issue:
http://public.kitware.com/Bug/view.php?id=14121
Nils
On 04/25/2013 10:00 PM, Nils Gladitz wrote:
I was able to reproduce the problem with Ninja on Ubuntu and CMake
2.8.11-rc2.
I set up a test project for which I set CTEST_CUSTOM_ERROR_MATCH to
Have a look at my post on StackOverflow
http://stackoverflow.com/questions/16286872/cmake-automoc-feature-skips-sources-of-executable-targets
for details.
http://stackoverflow.com/questions/16286872/cmake-automoc-feature-skips-sources-of-executable-targets
--
Powered by www.kitware.com
Visit
On Monday 29 April 2013, Haroogan wrote:
Have a look at my post on StackOverflow
http://stackoverflow.com/questions/16286872/cmake-automoc-feature-skips-so
urces-of-executable-targets for details.
http://stackoverflow.com/questions/16286872/cmake-automoc-feature-skips-so
On Mon, Apr 29, 2013 at 10:36 PM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
If cmake finds the static version of the library, it should properly use that
one.
I thought it would use the shared one per default?
Making cmake find the static version instead of the dynamic version is kind
On Mon, Apr 29, 2013 at 10:40 PM, Jean-Christophe Fillion-Robin
jchris.filli...@kitware.com wrote:
For example:
https://github.com/commontk/CTK/blob/ac13c32312c9160190b80bd3a03d012782eff40c/Libs/Core/CMake/ctkMacroBFDCheck.cmake#L33-43
I'm not sure whether I understand this correctly, or whether
On 29-Apr-13 23:27, Alexander Neundorf wrote:
On Monday 29 April 2013, Haroogan wrote:
Have a look at my post on StackOverflow
http://stackoverflow.com/questions/16286872/cmake-automoc-feature-skips-so
urces-of-executable-targets for details.
On Monday 29 April 2013, Haroogan wrote:
On 29-Apr-13 23:27, Alexander Neundorf wrote:
On Monday 29 April 2013, Haroogan wrote:
Have a look at my post on StackOverflow
http://stackoverflow.com/questions/16286872/cmake-automoc-feature-skips
-so urces-of-executable-targets for details.
On 29-Apr-13 23:27, Alexander Neundorf wrote:
On Monday 29 April 2013, Haroogan wrote:
Have a look at my post on StackOverflow
http://stackoverflow.com/questions/16286872/cmake-automoc-feature-skips-so
urces-of-executable-targets for details.
The only race was for multiple processes simultaneously deciding they need
to create the (currently missing) file and then trying to open the file for
write at the same time.
To what I see on the logs, this is not what I observe:
build 26-avr.-2013 13:11:12 CMake does not need to re-run
hard coded names aren't so bad, since they can be composed of dynamic
peices...
lib${CMAKE_LIBRARY_SUFFIX}/${CMAKE_SHARED_LIBRARY_PREFIX}c${CMAKE_SHARED_LIBRARY_SUFFIX}
or
lib${CMAKE_LIBRARY_SUFFIX}/${CMAKE_STATIC_LIBRARY_PREFIX}c${CMAKE_STATIC_LIBRARY_SUFFIX}
to choose lib[64]/libc.so or
On Tue, Apr 30, 2013 at 1:54 AM, J Decker d3c...@gmail.com wrote:
lib${CMAKE_LIBRARY_SUFFIX}/${CMAKE_SHARED_LIBRARY_PREFIX}c${CMAKE_SHARED_LIBRARY_SUFFIX}
or
lib${CMAKE_LIBRARY_SUFFIX}/${CMAKE_STATIC_LIBRARY_PREFIX}c${CMAKE_STATIC_LIBRARY_SUFFIX}
to choose lib[64]/libc.so or lib[64]/libc.a
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 7133dc9..2293000 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
set(CMake_VERSION_MAJOR 2)
set(CMake_VERSION_MINOR 8)
set(CMake_VERSION_PATCH 10)
-set(CMake_VERSION_TWEAK 20130429
48 matches
Mail list logo