Hi All,
I know that some new CPackRPM tests are failing
http://www.cdash.org/CDash/testDetails.php?test=86188713build=889597
the reason is the build path used contains space which cannot be handled
by rpmbuild...
I'll fix that tonight and avoid running those tests if build dir contains
2011/3/4 Rolf Eike Beer e...@sf-mail.de:
Hi All,
I know that some new CPackRPM tests are failing
http://www.cdash.org/CDash/testDetails.php?test=86188713build=889597
the reason is the build path used contains space which cannot be handled
by rpmbuild...
I'll fix that tonight and avoid
On 03/03/2011 05:04 PM, Alexander Neundorf wrote:
On Thursday 03 March 2011, Brad King wrote:
Hi Alex,
The Sun compiler still fails:
http://www.cdash.org/CDash/testDetails.php?test=85204365build=888421
It's because the execute_process in the CMakeLists.txt file of the test
does not use the
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11927
==
Reported By:David Cole
Assigned To:
On 03/02/2011 04:51 AM, Matej Hribernik wrote:
Reason for this mail are changes which I have done in head CMake code .
I would like to share my changes with you and I would be very grateful
for any feedback regarding my changes done in CMake sources.
[snip]
I have created my own locale branch
On 02/20/2011 12:38 PM, Peter Kümmel wrote:
Here is a very first shot of ninja on Windows:
https://github.com/syntheticpp/ninja/tree/qprocess
Cool, thanks for starting it!
I don't have time to review it in detail right now but we are
interested in this :)
Thanks,
-Brad
Hi all,
I have reported a number of issues and I am willing to contribute. Is
there any developer guide apart those links:
http://public.kitware.com/Wiki/Git/Workflow/Topic
http://www.itk.org/Wiki/CMake/Git
http://www.cmake.org/Wiki/CMake_FAQ
http://www.cmake.org/Wiki/CMake
Also, is there some
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11928
==
Reported By:Nicolas Despres
Assigned To:
2011/3/4 Eric Noulard eric.noul...@gmail.com:
Le 4 mars 2011 16:54, Nicolas Desprès nicolas.desp...@gmail.com a écrit :
Hi all,
I have reported a number of issues and I am willing to contribute. Is
there any developer guide apart those links:
The following issue has been SUBMITTED.
==
http://vtk.org/Bug/view.php?id=11929
==
Reported By:MarkR
Assigned To:
Hi All,
As of CPack 2.8.4 the component support has been added to
ArchiveGenerator and RPM
(and NSIS and PackageMaker continue to support component packaging)
As explained here;
http://www.cmake.org/Wiki/CMake:Component_Install_With_CPack#CPack_Generator_specific_behavior
Currently NSIS and
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11931
==
Reported By:Andrew Pennebaker
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11933
==
Reported By:Andrew Pennebaker
Assigned To:
Dear All,
Sorry to repost but I am still stuck with this, would anyone have suggestions?
Anyone had the same experience with the UPDATE_COMMAND not working?
Thanks,
Yves
From: Yves Martelli
Sent: lunes, 21 de febrero de 2011 15:00
To: 'cmake@cmake.org'
Subject: EXTERNALPROJECT_ADD and
add_definitions( -DSTORE=XYZ )
should do what you want.
If you have a cmake_minimum_required of at least version 2.6, then the
cmake_policy call is unnecessary -- it is simply implied by the minimum
required version of CMake for 2.6 and later.
What version of CMake are you using?
What OS and
On 04.03.11 14:56:14, Orcun Gokbulut wrote:
While I was investigating the problem I came across another problem; I can
not read default values of a source property. In more generic terms value of
a source file property (I don't known whether this applies to
target/directory/global properties)
You can definition two different library target
and use OUTPUT_NAME property to adjust the name
add_library(foo1 ${foo_source})
set_target_properties(foo1 PROPERTIES
OUTPUT_NAME foo)
add_library(foo2 ${foo_source})
set_target_properties(foo2
On 03/04/2011 01:56 PM, Orcun Gokbulut wrote:
Hi everybody,
I came across two problems when I was porting our project build system to
cmake.
The first program that I encounter is I can not compile generated source
files with extension other than default c/c++ extensions.
I have
Hi,
Can I create an rpm package with cpack in order to not deal with spec files ?
We did not need to put any debian/{changelog,rules,control} files
related implementation into the project so that to build a debian
package for arm with cpack.
2011/3/4 Laszlo Papp djsz...@archlinux.us:
Hi,
Can I create an rpm package with cpack in order to not deal with spec files ?
Yes you can CPackRPM is meant to do that:
http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#RPM_.28Unix_Only.29
The fastest path is to try:
$ cd /path/to/builddir
I am not a Visual Studio user so I may be missing your point here
but why having foo_1 and foo_2 ending up in the same workspace is a problem?
As long as the lib/dll end up in separate dirs (using *_OUTPUT_DIRECTORY).
Workspaces become too large, so I would like make'em smaller.
Should work
2011/3/4 Alexey Livshits livch...@web.de:
I am not a Visual Studio user so I may be missing your point here
but why having foo_1 and foo_2 ending up in the same workspace is a problem?
As long as the lib/dll end up in separate dirs (using *_OUTPUT_DIRECTORY).
Workspaces become too large, so
Hi Alexey,
Usually there are 2 ways: 1) put them into separate directories (like Debug
and Release), probably specifying different output directories or 2) use
different file names, say adding suffixes like D, or d8.
BTW, what's the point to have different configurations in the same workspace
One other thing. You may try using the NMake Makefiles generator if you
must use the VS10 compiler: the dependencies definitely work via the
makefiles. I just tried it out...
On Fri, Mar 4, 2011 at 10:15 AM, David Cole david.c...@kitware.com wrote:
Using:
UPDATE_COMMAND
is perfectly
Hi everyone,
Is there a better way to check whether the platform support symlink
than this one:
if(WIN32)
if(CYGWIN)
set(HAVE_SYMLINK TRUE)
else(CYGWIN)
set(HAVE_SYMLINK FALSE)
endif(CYGWIN)
else(WIN32)
set(HAVE_SYMLINK TRUE)
endif(WIN32)
Regards,
--
Nicolas Desprès
Yeah I was aware of that, I forgot to state that on the comment for the
function. This was made on purpose since I don't want the pain of adding every
file to CMake and I certainly don't want CMake running automatically.
Thanks,
Pablo Zurita.
PS: the sourceFiles argument must be removed from
Hi All,
I was just trying out the Target folders stuff in 2.8.4. The ALL_BUILD
target doesn't seem to be affected by the PREDEFINED_TARGETS_FOLDER
property.
Is that by design or an oversight?
Aaron Meadows
Software Engineer
Thomson Reuters
Phone: 314.468.3530
Mobile: 636.541.6139
To use Qt in my projects with CMake, up until now all it seemed to
require was this:
find_package(Qt4 REQUIRED)
include(${QT_USE_FILE})
But then I tried to use QTcpServer and QTcpSocket, and the compiles
failed because it couldn't find the include files.
Then I read through the FindQt4.cmake
Is there some reason that couldn't be a property as well? Or
possibly a
Policy?
2) why does ALL_BUILD need to be the default project
- This one I can't answer. I don't understand why it even is the
default
startup project anyhow. As such, it's useless. It seems to me that
On Friday, March 04, 2011 11:59:07 am kent williams wrote:
To use Qt in my projects with CMake, up until now all it seemed to
require was this:
find_package(Qt4 REQUIRED)
include(${QT_USE_FILE})
But then I tried to use QTcpServer and QTcpSocket, and the compiles
failed because it
2011/3/4 Laszlo Papp djsz...@archlinux.us:
On Fri, Mar 4, 2011 at 3:05 PM, Eric Noulard eric.noul...@gmail.com wrote:
2011/3/4 Laszlo Papp djsz...@archlinux.us:
Hi,
Can I create an rpm package with cpack in order to not deal with spec files
?
Yes you can CPackRPM is meant to do that:
Hi,
I'm trying to use cmake with the Cray Fortran compiler. The compiler is wrapped
through a script called ftn.
When I have the PrgEnv-pgi (pgi compiler) or the PrgEnv-gnu modules loaded, it
works with no issue.
But, when I have it set to PrgEnv-cray, it doesn't work.
I manually compiled
Hi,
I'm trying to use cmake with the Cray Fortran compiler. The compiler is wrapped
through a script called ftn.
When I have the PrgEnv-pgi (pgi compiler) or the PrgEnv-gnu modules loaded, it
works with no issue.
But, when I have it set to PrgEnv-cray, it doesn't work.
I manually compiled
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 4d54531341664fdc8e07d8892aa90ebcfe0f7a44 (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 5bdb41118dc7b529c1180d5253081958b2ff5429 (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 44c437ea65b58ed05f9e2ba80c2471dc0f852dbf (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 eb92381eb6cb509b5f64f295a2ed85ff16b17e43 (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 e8f3c307077bb50011019608c535bfa11aa6d781 (commit)
via
38 matches
Mail list logo
