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
Some of the notable changes in this release are:
- Introduced Target Usage Requirements
- Targets can
Thankyou Thomas, it works now... Another issue I was faced with the first
script is, it assumes that the dlls are in the lib folder of Qt (I think
you build qt from source). I have downloaded the prebuilt Qt library, in
that the dlls are in the bin folder. I modified the macro you have given,
as
Hi,
My project hierarchy is as shown below
Code ;Root cmake file
Code/Src;Main Source code and the cmake file
Code/lib/reverse ; Library source code and the cmake file
When I compile the project I get the outputs in these folder structure
BuildDir\src\Debug
Hello,
It seems that the Projetct(name NONE) macro requires the CMAKE_MAKE_PROGRAM to
be defined.
This CMakelists will trigger a CMAKE_MAKE_PROGRAM not found, when trying to
cross-compile with code sourcery toolchain which is using a non-trivial make
program name:
Hi,
I have another wired situation when I run cpack -G RPM, the cpack changed
a binary file permission:
Original file in the build directory:
$ ls -l Robotic/Robotic-prefix/src/robotic/bin/CreateSystemObject
-rwxr-xr-x. 1 root root 15307640 Apr 19 12:01
Hello,
As suggested by the forums I have tried searching the archives, but I have
not got an answer to my question. Hence, if this is a duplicate question,
I
apologize in advance.
We have a team across multiple countries which use different versions of
Visual Studio and Eclipse. Hence, for us,
Thanks again. Setting the WORKING_DIRECTORY worked for me...
On Mon, Apr 15, 2013 at 5:17 PM, Petr Kmoch petr.km...@gmail.com wrote:
It's good the second signature works; I believe there's hardly ever use
for using the first one, anyway.
As for the DLLs, would it help if you set the
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
Some of the notable changes in this release are:
- Introduced Target Usage Requirements
- Targets can
2013/4/19 hce jupiter@gmail.com:
Hi,
I have another wired situation when I run cpack -G RPM, the cpack changed
a binary file permission:
Original file in the build directory:
$ ls -l Robotic/Robotic-prefix/src/robotic/bin/CreateSystemObject
-rwxr-xr-x. 1 root root 15307640 Apr 19
On 4/19/2013 7:20 AM, jitesh.but...@ifm.com wrote:
I would like to generate the projects for all the different
flavors of C / C++ compilers that we would like to support.
Unfortunately, I
do not have all the flavors installed on my machine. Is it possible for me
to generate the projects without
dear Jean-Christophe,
indeed the approach you demostrated works for me!
this is exactly what i needed.
thank you again!
(i am sorry for coming back to you so late;
was too busy with other things)
best regards,
radovan
On Sat, 13 Apr 2013 12:24:02 +0200, Jean-Christophe Fillion-Robin
Hi Radovan,
That is good news :) Do you think you could share the CMake code you ended
up created. May be could generalize the solution to create a re-usable
module.
Thanks
Jc
On Fri, Apr 19, 2013 at 12:23 PM, radovan bast
radovan.b...@irsamc.ups-tlse.fr wrote:
dear Jean-Christophe,
dear Jean-Christophe,
absolutely. it will take a bit of time until
we finetune things but the plan is to have and share an open
source repository (probably on github) that will provide
generic plug-n-play CMake infrastructure for projects that require
Fortran, C, and C++,
as well as
Hi,
That is awesome. May be the most generic component could be hosted on the
http://github.com/commontk ? We are also trying to make
generic component allowing to easily build application relying on multiple
project.
The idea would be to provide a drop-in CMake module (named CMakeSuperBuild
?)
On Friday 19 April 2013, Gregoire Aujay wrote:
Hello,
It seems that the Projetct(name NONE) macro requires the CMAKE_MAKE_PROGRAM
to be defined.
in usual setups this is not a problem.
This CMakelists will trigger a CMAKE_MAKE_PROGRAM not found, when trying to
cross-compile with code
I am invoking CMake like this on Windows:
Working directory is: C:\work\build
Directory containing source root level CMakeLists.txt file: Y:\
So I invoke like this:
C:\work\build cmake -G NMake Makefiles Y:\
When I do this, any subdirectories I traverse inside Y:\ do not appear
under their
On 2013-04-17 12:41, Skippy VonDrake wrote:
Thought I understood this - but alas my implementation is wrong.
Here's my test case with a top-level cmake file and 3 subdirectories:
'src', 'bin' and 'outdir'.
Top level CMakeLists.txt
cmake_minimum_required (VERSION 2.8)
project (copyFile)
Eric Noulard wrote
2013/4/19 hce lt;
jupiter.hce@
gt;:
Hi,
I have another wired situation when I run cpack -G RPM, the cpack
changed
a binary file permission:
Original file in the build directory:
$ ls -l Robotic/Robotic-prefix/src/robotic/bin/CreateSystemObject
-rwxr-xr-x. 1 root
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 5e01b6d..81684e7 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 20130419
19 matches
Mail list logo
