Thank you David, my issue is solved.
It's because the SET( CMAKE_CXX_FLAGS ) inside CTest script has no effect ,
instead, I need to insert lines into
SET (CTEST_INITIAL_CACHE
...
)
Also, I mistakenly override the CMAKE_CXX_FLAGS in the root CMakeList.txt
Regards,
Joseph
On
Thank you David, my issue is solved.
It's because the SET( CMAKE_CXX_FLAGS ) inside CTest script has no effect ,
instead, I need to insert lines into
SET (CTEST_INITIAL_CACHE
...
)
Also, I mistakenly override the CMAKE_CXX_FLAGS in the root CMakeList.txt
Regards,
Joseph
2010/8/25
On 26 August 2010 01:34, Mark Roden mmro...@gmail.com wrote:
I'm starting to get deep into CMake, and I have a few questions as I
try to convert the socket++ library such that it can be compiled by
CMake on Windows.
1) The default install directory on Windows is C:\Program Files, or
On 26. Aug, 2010, at 1:34 , Mark Roden wrote:
I'm starting to get deep into CMake, and I have a few questions as I
try to convert the socket++ library such that it can be compiled by
CMake on Windows.
Cool!
1) The default install directory on Windows is C:\Program Files, or
C:\Program
I do not want all the include flags to be isystem, only one. I'm using
cmake version 2.8.2
Cheers,
Johny
On 08/25/2010 09:46 PM, Bill Hoffman wrote:
On Wed, Aug 25, 2010 at 3:01 PM, Michael Wildthem...@gmail.com wrote:
On 25. Aug, 2010, at 18:57 , Johny wrote:
Hey,
I was trying
2010/7/5 John Drescher dresche...@gmail.com
I see, thanks. I intend to write a Python script that adds the extra
platform solution, because we really need that. Visual Studio and
Code::Blocks project files are XML files, so it shouldn't be too hard.
What is wrong with different build
On 26 August 2010 10:17, Mark Van Peteghem mar...@gmail.com wrote:
We do have different build folders for each compiler / ide, but I mean
'build folder' as the folder where the object files and executable ends. We
just want one project file with different platform solutions, so we don't
have
I tried and failed to generate working project files for the Fortran 12
compiler with Visual Studio 2010. (NMake works ok)
Has anyone else tried with success ?
If not ... is there any possibility of CMake Developers targeting the New Intel
tool suite in the near future?
I'd like to have a go
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf Of Mike McQuaid
Sent: Thursday, August 26, 2010 1:12 AM
To: Mark Roden
Cc: cmake@cmake.org
Subject: Re: [CMake] several questions about cmake
On 26 August 2010 01:34, Mark Roden
On 8/26/2010 4:00 AM, Johny wrote:
SET(CMAKE_INCLUDE_SYSTEM_FLAG_C)
SET(CMAKE_INCLUDE_SYSTEM_FLAG_CXX)
Can you try:
SET(CMAKE_INCLUDE_SYSTEM_FLAG_C -isystem)
SET(CMAKE_INCLUDE_SYSTEM_FLAG_CXX -isystem)
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
On Wed, Aug 25, 2010 at 11:17 PM, Michael Wild them...@gmail.com wrote:
On 26. Aug, 2010, at 1:34 , Mark Roden wrote:
I'm starting to get deep into CMake, and I have a few questions as I
try to convert the socket++ library such that it can be compiled by
CMake on Windows.
Cool!
Thanks, I
On Thu, Aug 26, 2010 at 6:47 AM, Hickel, Kelly kelly_hic...@bmc.com wrote:
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf Of Mike McQuaid
Sent: Thursday, August 26, 2010 1:12 AM
To: Mark Roden
Cc: cmake@cmake.org
Subject: Re: [CMake]
On 08/26/2010 09:45 AM, John Drescher wrote:
On Thu, Aug 26, 2010 at 6:47 AM, Hickel, Kellykelly_hic...@bmc.com wrote:
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf Of Mike McQuaid
Sent: Thursday, August 26, 2010 1:12 AM
To:
1) The default install directory on Windows is C:\Program Files, or
C:\Program Files (x86) on 64 bit. ?This default will not work on
Windows 7 (and perhaps Vista), because the user isn't running as
administrator anymore, and only administrators can modify that
directory. ?There should
On Thu, Aug 26, 2010 at 5:18 AM, Biddiscombe, John A. biddi...@cscs.ch wrote:
I tried and failed to generate working project files for the Fortran 12
compiler with Visual Studio 2010. (NMake works ok)
Has anyone else tried with success ?
If not ... is there any possibility of CMake
On 08/26/2010 05:38 PM, Mark Roden wrote:
2) I'm trying to check to see if a certain C++ code chunk will
compile. The line is:
CHECK_CXX_SOURCE_COMPILES(
#include string.h
#include stdio.h
void main(){
char buf[100];
char buf2[100];
strncpy(buf2, buf, 5);
buf2[5] = '\0';
Hi Chris,
Your suggestion to generate testlist.cmake in your build directory and
then re-run cmake worked with some tweaking.
Thank you!!
Neelima
Message: 3
Date: Wed, 25 Aug 2010 18:31:46 -0700
From: Chris Hillery chillery-cm...@lambda.nu
Subject: Re: [CMake] CMake and CTest for Google tests
Hi Fraser,
That's a great suggestion! Thank you for the script. It appears that
CMake has support for GTESTS in CMake 2.8.2 which uses a macro, very
similar to yours.
http://public.kitware.com/cgibin/viewcvs.cgi/Modules/FindGTest.cmake?rev
ision=1.4root=CMakeview=markup
Thanks again!
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 d8ccd1760c39ba836dc8daf3c0ea4f313be663cc (commit)
from
19 matches
Mail list logo
