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 C compiler flags. Therefore 32-bit assembly code is
generated and then it tries to compile it with
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 C compiler flags. Therefore 32-bit assembly code
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11925
==
Reported By:Farid Zaripov
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11926
==
Reported By:hkrishna
Assigned To:
On Tue, Mar 1, 2011 at 3:45 PM, Campbell Barton ideasma...@gmail.com
Hi, my original questions is still unanswered.
I'm not familiar with how the CMake project goes about these decisions.
Are there any developers on this list who might review patches for new
project generators?
If so, any
Hello,
IF(bgdgbBromNN MATCHES Brom)
is true,
but
IF(Brom MATCHES bgdgbBromNN)
is false.
Should be same, or?
Greetings
Micha
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
On 03/03/2011 11:25 AM, Micha Renner wrote:
Hello,
IF(bgdgbBromNN MATCHES Brom)
is true,
but
IF(Brom MATCHES bgdgbBromNN)
is false.
Should be same, or?
Greetings
Micha
No, the right-hand-side of MATCHES is a regular expression.
Michael
Hello CMakers,
suppose I've got a library foo with tow configurations: foo_1 and
foo_2. Both versions should have the same output name: foo. The
problem is, the output directory for both ist the same, so the second
will overwrite the first.
What's the best way to organize it?
--
BG,
Alexey
2011/3/3 Alexey Livshits livch...@web.de:
Hello CMakers,
suppose I've got a library foo with tow configurations: foo_1 and
foo_2. Both versions should have the same output name: foo. The
problem is, the output directory for both ist the same, so the second
will overwrite the first.
You can
Hello! One more question.. For example I have such structure:
folder:base
CMakeLists.txt (with PROJECT(someproject))
folder:lib1
CMakeLists.txt
folder:lib2
CMakeLists.txt
folder:app
CMakeLists.txt
and result is someproject.sln with 3 projects lib1, lib2,
Anton Sibilev skrev 2011-03-03 15:49:
Hello! One more question.. For example I have such structure:
folder:base
CMakeLists.txt (with PROJECT(someproject))
folder:lib1
CMakeLists.txt
folder:lib2
CMakeLists.txt
folder:app
CMakeLists.txt
and result is
No, only one solution (someproject.sln) for all three targets.. 2.8.3 version
2011/3/3 Robert Bielik robert.bie...@xponaut.se:
Anton Sibilev skrev 2011-03-03 15:49:
Hello! One more question.. For example I have such structure:
folder:base
CMakeLists.txt (with PROJECT(someproject))
David Cole skrev 2011-03-03 15:57:
Solution files correspond to project commands in CMakeLists.txt.
Add a project command at the top of app/CMakeLists.txt
Of course, I usually put a project command at top of CMakeLists.txt so I get
the solution files... didn't cross my mind
that not
David, it has helped me, thanks :)
2011/3/3 David Cole david.c...@kitware.com:
On Thu, Mar 3, 2011 at 9:52 AM, Robert Bielik robert.bie...@xponaut.se
wrote:
Anton Sibilev skrev 2011-03-03 15:49:
Hello! One more question.. For example I have such structure:
folder:base
CMakeLists.txt
On 3/3/2011 9:59 AM, gekso wrote:
No, only one solution (someproject.sln) for all three targets.. 2.8.3 version
2011/3/3 Robert Bielikrobert.bie...@xponaut.se:
Anton Sibilev skrev 2011-03-03 15:49:
Hello! One more question.. For example I have such structure:
folder:base
CMakeLists.txt
Hi All,
I would like to be able to script the cmake compatibility command
use_mangle_mesa(mesapath/include/GL some_other_path).
For example:
%cat scriptfile
cmake_minimum_required(VERSION 2.8)
use_mangled_mesa(mesapath/include/GL some_other_path)
%cmake -P scriptfile
Ultimately it would be
On Wednesday 02 March 2011, Frans de Boer wrote:
Dear Readers,
I guess that my question has been asked many time before, but I could
not find it. So her it is (again): Using './configure --libdir=...' one
can set the base directory where the libraries are supposed to be
placed. CMake has so
On Tuesday 01 March 2011, Campbell Barton wrote:
On Tue, Mar 1, 2011 at 2:47 PM, Marcus D. Hanwell
marcus.hanw...@kitware.com wrote:
On Tue, Mar 1, 2011 at 9:15 AM, John Drescher dresche...@gmail.com
wrote:
On Tue, Mar 1, 2011 at 6:45 AM, Campbell Barton ideasma...@gmail.com
wrote:
On Thursday 03 March 2011, Chris Green wrote:
Hi,
I have a macro which takes a variety of arguments and does all the
things necessary for making a test: compiling the exec (or copying the
script), putting input files in the right place and setting desired
properties on the test. I use the
Hello friends,
As far as I have been investigating this problem, seems that GNU compilers
have a problem when combining -c flag with multiple files and -o flag to
generate an executable.
The problem is that CMake somehow is generating the compile command, and
assembling it wrongly. Is there any
On Thursday 03 March 2011, Enrique Izaguirre wrote:
Hello friends,
As far as I have been investigating this problem, seems that GNU compilers
have a problem when combining -c flag with multiple files and -o flag to
generate an executable.
The problem is that CMake somehow is generating the
Is it possible to set the build config in a ctest script rather than pass it in
on the command line? I haven't found a list of ctest variables in the
documentation like there is for cmake.
Thanks a lot,
Dan
___
Powered by www.kitware.com
Visit other
In CMake 2.8.2 and later, you can:
set(CTEST_CONFIGURATION_TYPE Release) # or Debug
in the ctest -S script.
That will influence both the ctest_build and ctest_test commands.
HTH,
David
On Thu, Mar 3, 2011 at 2:09 PM, Macumber, Daniel
daniel.macum...@nrel.govwrote:
Is it possible to set
On Thursday 03 March 2011, Harinarayan Krishnan wrote:
Hi All,
I would like to be able to script the cmake compatibility command
use_mangle_mesa(mesapath/include/GL some_other_path).
Please put this in the cmake bug tracker, I'll take care of it.
Alex
Thanks for looking into this. I have posted this request on the bug
tracker. http://public.kitware.com/Bug/view.php?id=11926
http://public.kitware.com/Bug/view.php?id=11926Best regards,
Hari
2011/3/3 Alexander Neundorf a.neundorf-w...@gmx.net
On Thursday 03 March 2011, Harinarayan Krishnan
On Thu, Mar 3, 2011 at 5:10 PM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
On Tuesday 01 March 2011, Campbell Barton wrote:
On Tue, Mar 1, 2011 at 2:47 PM, Marcus D. Hanwell
marcus.hanw...@kitware.com wrote:
On Tue, Mar 1, 2011 at 9:15 AM, John Drescher dresche...@gmail.com
wrote:
I am using cmake 2.8 version.
My cmake contains following statements.
cmake_policy(SET CMP0005 NEW)
add_definitions(
-DSTORE=\XYZ\
)
I am using VS 8 (2005). cmake writes the build file(vcproj) successfully
without any warning
When I see, vcproj. It contains
\quot;\qout;XYZ\quot;\qout;
So
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 9feea1200a40f59d70e35034ccc91256e34789cd (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 2bdac994e5f4e9ce8e1810ea80f7fd8a693e6443 (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 ed1cd2daf6bedbfc9870852184940494bfacec42 (commit)
from
30 matches
Mail list logo
