The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=12255
==
Reported By:Vivien Delmon
Assigned To:
2011/6/7 Michael Wild them...@gmail.com:
On 06/07/2011 07:40 PM, Werner Mahr wrote:
Michael Wild wrote:
[...]
I don't think that writing
stuff like this in many different projects is a good idea, that's why I
proposed to include it native in cmake.
ADD_EXECUTABLE(app, sources)
The following issue has been SUBMITTED.
==
http://cmake.org/Bug/view.php?id=12256
==
Reported By:Daniel Franke
Assigned To:
On Tuesday, June 07, 2011 02:34:06 PM Eric Noulard wrote:
2011/6/7 Alexander Neundorf neund...@kde.org:
On Monday, June 06, 2011 03:26:03 PM Brad King wrote:
On 06/04/2011 06:30 AM, Alexander Neundorf wrote:
[...]
What do you think about adding the keyword OPTIONAL to
On Saturday, June 04, 2011 10:09:57 AM Alexander Neundorf wrote:
Hi,
I'm currently at the KDE Platform Sprint, where we (a bunch of KDE
developers) are discussing how to move on with the KDE platform.
This includes some things regarding cmake.
When we introduced cmake in KDE, there were not
On Jun 8, 2011, at 12:08 PM, Alexander Neundorf wrote:
On Tuesday, June 07, 2011 02:34:06 PM Eric Noulard wrote:
2011/6/7 Alexander Neundorf neund...@kde.org:
On Monday, June 06, 2011 03:26:03 PM Brad King wrote:
On 06/04/2011 06:30 AM, Alexander Neundorf wrote:
[...]
What do you think
On Monday, June 06, 2011 03:37:16 PM Brad King wrote:
On 06/06/2011 03:56 AM, Alexander Neundorf wrote:
On Saturday, June 04, 2011 10:24:52 AM Alexander Neundorf wrote:
Hi,
one feature which all KDE developers are used to and which is also used
by qmake when building Qt is automoc.
On 6/8/2011 2:59 PM, Alexander Neundorf wrote:
The two things are
- BSD licensing, we did that 3 years ago:
http://quickgit.kde.org/?p=automoc.gita=commith=78fdba1e2d96bc45512531748ffb770cb1124798
-and porting to STL+cmsys, we did that now
Beside that, I didn't ask explicitely, but I'm sure
On 6/8/2011 3:33 PM, Clinton Stimpson wrote:
It seems an extra tool is needed at build time to handle qrc files correctly,
and I'm wondering if a generic tool could handle both this and the autmoc.
It is not possible to implement custom build-time dependency
scanning in VS IDE projects without
On 6/8/2011 2:59 PM, Alexander Neundorf wrote:
The two things are
- BSD licensing, we did that 3 years ago:
http://quickgit.kde.org/?p=automoc.gita=commith=78fdba1e2d96bc45512531748ffb770cb1124798
-and porting to STL+cmsys, we did that now
Great. Please push a topic to the stage for
On 06/08/2011 09:24 PM, Bill Hoffman wrote:
On 6/8/2011 2:59 PM, Alexander Neundorf wrote:
The two things are
- BSD licensing, we did that 3 years ago:
http://quickgit.kde.org/?p=automoc.gita=commith=78fdba1e2d96bc45512531748ffb770cb1124798
-and porting to STL+cmsys, we did that now
On 6/8/2011 2:08 PM, Alexander Neundorf wrote:
This would make the options available for cmake-based projects more
consistent.
This issue comes up regularly from new users.
The option() command adds options. The add_subdirectory command
adds subdirectories. The find_package command finds
On Wed, Jun 8, 2011 at 8:08 PM, Alexander Neundorf neund...@kde.org wrote:
On Tuesday, June 07, 2011 02:34:06 PM Eric Noulard wrote:
2011/6/7 Alexander Neundorf neund...@kde.org:
On Monday, June 06, 2011 03:26:03 PM Brad King wrote:
On 06/04/2011 06:30 AM, Alexander Neundorf wrote:
[...]
On Wed, Jun 8, 2011 at 1:35 PM, Brad King brad.k...@kitware.com wrote:
On 6/8/2011 3:33 PM, Clinton Stimpson wrote:
It seems an extra tool is needed at build time to handle qrc files
correctly,
and I'm wondering if a generic tool could handle both this and the
autmoc.
It is not possible
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12258
==
Reported By:Campbell Barton
Assigned To:
Clinton Stimpson wrote:
On Wednesday, June 08, 2011 12:59:36 pm Alexander Neundorf wrote:
Beside that, I didn't ask explicitely, but I'm sure without automoc
cmake
is out of the game for becoming the buildsystem for Qt5 (because in Qt4
they do automoc in qmake).
What if this was a
Dear CMake developers,
for our oproject we are utilizing the 'make Exerimental' and 'make Nigthly'
commands to make the all (update)/configure/build/test and sending report
steps.
One can see that on our CDash-board, like
https://repo.ctcc.no/CDash/index.php?project=DIRACdate=2011-06-07
Ralph Barth will be out of the office starting 08.06.2011 and will be
returning on 09.06.2011.
Ich werde Ihre Nachrichten nach meiner Rückkehr beantworten.
-
Deutsche Börse AG
Chairman of the Supervisory Board/
Hi @all,
I have some problem with the library usage in cmake.
It seems to me, that cmake removes the full path of the library, if the
path is in the environment variable LIBRARY_PATH.
This behaviour cause problems at our system, such that the linker links
against the wrong library.
Is there
2011/6/7 Jean-Christophe Fillion-Robin jchris.filli...@kitware.com:
Hi Folks,
I observed there are different ways of naming binary packages:
myproject-Linux-i386.{ext}
myproject-Linux-amd64.{ext}
myproject-Linux-x86_32.{ext}
myproject-Linux-x86_64.{ext}
2011/6/8 Andreas Naumann andreas-naum...@gmx.net:
Hi @all,
I have some problem with the library usage in cmake.
It seems to me, that cmake removes the full path of the library, if the path
is in the environment variable LIBRARY_PATH.
This behaviour cause problems at our system, such that
On Tuesday 07 Jun 2011 7:40:33 PM dfurt...@cox.net wrote:
I have been hammergin on a vxworks cross-compile toolchain file. It seems
that not all properties that are set in the cross-compilation file
propogate to the CMakeLists.txt file that is using it. An example is the
CMAKE_AR property.
Am 08.06.2011 11:56, schrieb Eric Noulard:
2011/6/8 Andreas Naumannandreas-naum...@gmx.net:
Hi @all,
I have some problem with the library usage in cmake.
It seems to me, that cmake removes the full path of the library, if the path
is in the environment variable LIBRARY_PATH.
This
2011/6/8 Andreas Naumann andreas-naum...@gmx.net:
Am 08.06.2011 11:56, schrieb Eric Noulard:
2011/6/8 Andreas Naumannandreas-naum...@gmx.net:
Hi @all,
I have some problem with the library usage in cmake.
It seems to me, that cmake removes the full path of the library, if the
path
is in
Dear experts,
We would like to check the generated target (main executable) after it was
built.
For example
.
.
Linking Fortran executable vibcal.x
[100%] Built target vibcal.x
[100%] Built target dirac.x
afterwards, it would be good to get own message about properties of the
generated target
2011/6/8 Ilias Miroslav miroslav.il...@umb.sk:
Dear experts,
We would like to check the generated target (main executable) after it was
built.
For example
.
.
Linking Fortran executable vibcal.x
[100%] Built target vibcal.x
[100%] Built target dirac.x
afterwards, it would be good to
Hi there,
Slightly off topic, but how do people cope with cmd.exe not
expanding wildcards (*) ?
I would like to do something like:
cmd cmake -E tar cvfz test.tgz *.log
Thanks
--
Mathieu
___
Powered by www.kitware.com
Visit other Kitware
Hi Mathieu,
May be you could try the following ...
file(GLOB log_files *.log)
if(log_files)
execute_process(${CMAKE_COMMAND} -E tar cvfz test.tgz ${log_files})
endif()
Hth
Jc
On Wed, Jun 8, 2011 at 12:05 PM, Mathieu Malaterre
mathieu.malate...@gmail.com wrote:
Hi there,
Slightly off
On 08.06.11 20:00:54, Andreas Naumann wrote:
Am 08.06.2011 15:02, schrieb Eric Noulard:
2011/6/8 Andreas Naumannandreas-naum...@gmx.net:
Am 08.06.2011 11:56, schrieb Eric Noulard:
2011/6/8 Andreas Naumannandreas-naum...@gmx.net:
Hi @all,
I have some problem with the library usage in
On Wednesday 08 June 2011, Ilias Miroslav wrote:
Dear CMake developers,
for our oproject we are utilizing the 'make Exerimental' and 'make Nigthly'
commands to make the all (update)/configure/build/test and sending report
steps.
One can see that on our CDash-board, like
On Tuesday 07 June 2011, Alexander Neundorf wrote:
On Tuesday, June 07, 2011 04:41:03 AM jeeyoung kim wrote:
I was wondering if there's some way to prevent make clean in cmake from
re-building external dependencies. I'm using ExternalProject to build
third party c++ libraries, and they do
On 06/07/2011 02:20 PM, Bjørn Forsman wrote:
Hi all,
As far as I can tell, all Qt programs built with CMake must include
QT_USE_FILE after find_package(). So why doesn't FindQt4.cmake simply
include QT_USE_FILE itself? Is there maybe a use case where
QT_USE_FILE is *not* wanted?
Yes, there
On 06/07/2011 06:58 PM, Michael Wild wrote:
On 06/07/2011 06:23 PM, Bjørn Forsman wrote:
2011/6/7 Michael Wild them...@gmail.com:
On 06/07/2011 03:38 PM, Bjørn Forsman wrote:
Why not put find_package(Qt4) in the sub directories where it is actually
used?
And if it is used in multiple
On 06/07/2011 09:13 PM, Bjørn Forsman wrote:
2011/6/7 Michael Wild them...@gmail.com:
If the FindXXX.cmake file called add_definitions(),
include_directories() et al., that could be potentially harmful. Some
sources might required that some define is not set, or a wrong header
file might be
Am 08.06.2011 20:43, schrieb Andreas Pakulat:
On 08.06.11 20:00:54, Andreas Naumann wrote:
Am 08.06.2011 15:02, schrieb Eric Noulard:
2011/6/8 Andreas Naumannandreas-naum...@gmx.net:
Am 08.06.2011 11:56, schrieb Eric Noulard:
2011/6/8 Andreas
On 06/09/2011 07:13 AM, Andreas Naumann wrote:
Am 08.06.2011 20:43, schrieb Andreas Pakulat:
On 08.06.11 20:00:54, Andreas Naumann wrote:
Am 08.06.2011 15:02, schrieb Eric Noulard:
2011/6/8 Andreas Naumannandreas-naum...@gmx.net:
Am 08.06.2011 11:56, schrieb Eric Noulard:
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 e2276488ae6a37b1597bcf92a37fb02992de93bd (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 45adc8e8c16127f9d12b5c59a37fb9eeb492cf74 (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 98dc13e5139e53446febd01c754430b9edf09575 (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 b661b3452136b368556639b54b8333ff37c79407 (commit)
via
40 matches
Mail list logo
