Bill Hoffman wrote:
Tyler Roscoe wrote:
On Fri, Dec 19, 2008 at 01:33:45AM +0800, Kermit Mei wrote:
c++ -Wall -gstabs(or -g) main.cpp hello.cpp -o main
How can I use cmake to do the same thing?
Add your -g flag to CMAKE_CXX_FLAGS or I think you can use
ADD_DEFINITIONS("-g").
It would be
Tyler Roscoe wrote:
On Fri, Dec 19, 2008 at 01:33:45AM +0800, Kermit Mei wrote:
c++ -Wall -gstabs(or -g) main.cpp hello.cpp -o main
How can I use cmake to do the same thing?
Add your -g flag to CMAKE_CXX_FLAGS or I think you can use
ADD_DEFINITIONS("-g").
tyler
Thank you, tyler;
I tried to find documentation for this somewhere, but couldn't... I'm
happy to get a ref to relevant documentation, instead of a specific
answer...
The Windows version of my project builds, and I can run the INSTALL and
the files go where I want them. But the final steps of my install will
re
Pierrick Grasland wrote:
> I'm testing CMake with a little project, but I encounter a problem with GTK.
> I was building with autotools and pkg_config before, so I know I have
> GTK+-2.0 on my system.
Since pkg-config is the "officially supported" way to obtain GTK
dependencies and compiler flag
Bartlett, Roscoe A wrote:
Bill,
I am having all kinds of trouble with the extended Ctest scripting
mode.
Here are just some of the problems:
1) Can't get memory checking to work
http://www.cdash.org/CDash/viewNotes.php?buildid=231924
2) Can't get coverage testing to work
Should be pretty m
Ok, I will try it tomorrow.
On Thu, Dec 18, 2008 at 8:37 PM, Hendrik Sattler wrote:
> Am Thursday 18 December 2008 20:03:25 schrieb Philip Lowman:
> > Could you try the following beta FindGTK2 module?
> >
> > Set CMAKE_MODULE_PATH prior to calling FIND_PACKAGE(GTK2 COMPONENTS gtk)
> > See the mod
I want to use sed to modify and create a file like:
sed -e 's/\(^#include[ \t]*"\)(.*"[ \t]*$\)/\1autogen_include\/\2/g'
original_file new_file
Seems ADD_CUSTOM_COMMAND can't accept this kind of regularexp as the ARGS.
Thanks and regards,
Huyi Wang
_
Tyler wrote:
On Thu, Dec 18, 2008 at 03:07:12PM -0500, Bill Hoffman wrote:
Tyler Roscoe wrote:
On Fri, Dec 19, 2008 at 01:33:45AM +0800, Kermit Mei wrote:
c++ -Wall -gstabs(or -g) main.cpp hello.cpp -o main
How can I use cmake to do the same thing?
Add your -g flag to CMAKE_CXX_FLAGS or I t
Brad Aisa wrote:
They have different suffixes, so they do not conflict. But thanks for
the answer.
So, a custom command can be used to do the copy. There is a feature
request for this that has been coming up frequently on the list... :)
-Bill
___
Jon Shuler wrote:
I searched and I am sure I missed it but how do I change the project
filename from zero_check.vcproj to something else?
Right now you can't.
-Bill
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On Thu, Dec 18, 2008 at 03:07:12PM -0500, Bill Hoffman wrote:
> Tyler Roscoe wrote:
> >On Fri, Dec 19, 2008 at 01:33:45AM +0800, Kermit Mei wrote:
> >>c++ -Wall -gstabs(or -g) main.cpp hello.cpp -o main
> >>
> >>How can I use cmake to do the same thing?
> >
> >Add your -g flag to CMAKE_CXX_FLAGS o
On Thu, Dec 18, 2008 at 12:48:49PM -0700, Brad Aisa wrote:
> I have set
> CMAKE_xxx_OUTPUT_DIRECTORY (LIBRARY RUNTIME ARCHIVE)
> at the top of my CMakeLists.txt
> I then confirmed it had this value for my target properties.
>
> But when I build, MSVC adds an additional Target subdirectory, which i
Would it be possible to add configuration support to include_directories()?
For example, some include directories I only want to show up in debug, some
in release, and some in all configurations. I imagine this would look a lot
like target_link_libraries():
include_directories(
C:\includes\foo
They have different suffixes, so they do not conflict. But thanks for
the answer.
Bill Hoffman wrote:
Brad Aisa wrote:
I have set
CMAKE_xxx_OUTPUT_DIRECTORY (LIBRARY RUNTIME ARCHIVE)
at the top of my CMakeLists.txt
I then confirmed it had this value for my target properties.
...
You can not
Brad Aisa wrote:
I have set
CMAKE_xxx_OUTPUT_DIRECTORY (LIBRARY RUNTIME ARCHIVE)
at the top of my CMakeLists.txt
I then confirmed it had this value for my target properties.
But when I build, MSVC adds an additional Target subdirectory, which is
not what I want. For example, I want this generat
Tyler Roscoe wrote:
On Fri, Dec 19, 2008 at 01:33:45AM +0800, Kermit Mei wrote:
c++ -Wall -gstabs(or -g) main.cpp hello.cpp -o main
How can I use cmake to do the same thing?
Add your -g flag to CMAKE_CXX_FLAGS or I think you can use
ADD_DEFINITIONS("-g").
It would be better to edit the CM
I searched and I am sure I missed it but how do I change the project filename
from zero_check.vcproj to something else?
Thanks,
Jon
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
I have set
CMAKE_xxx_OUTPUT_DIRECTORY (LIBRARY RUNTIME ARCHIVE)
at the top of my CMakeLists.txt
I then confirmed it had this value for my target properties.
But when I build, MSVC adds an additional Target subdirectory, which is
not what I want. For example, I want this generated:
C:\MyProject
I don't know about your first question but:
On Thu, Dec 18, 2008 at 12:33:56PM -0700, Brad Aisa wrote:
> Also (minor point) how is the default project chosen? Can I explicitly
> override this to force my main executable target to be the default
> project? Thanks!
There was a thread about this t
Am Thursday 18 December 2008 20:03:25 schrieb Philip Lowman:
> Could you try the following beta FindGTK2 module?
>
> Set CMAKE_MODULE_PATH prior to calling FIND_PACKAGE(GTK2 COMPONENTS gtk)
> See the module for details
Some notes: you should make better use of path suffixes in find_file instead
o
When I'm building using MSVC 9, if one project fails, the build keeps
going -- I want the build to stop if any project fails. Can someone tell
me how to do this?
Also (minor point) how is the default project chosen? Can I explicitly
override this to force my main executable target to be the de
I did a clean build last night. This morning I see one bogus failure.
Bill
On Wed, Dec 17, 2008 at 1:18 PM, Bill Lorensen wrote:
> Some more information. This is not a clean build each night. With the
> compiler flags I use, it just takes too long. However, tonight, I'll
> clean the build tree.
Could you try the following beta FindGTK2 module?
Set CMAKE_MODULE_PATH prior to calling FIND_PACKAGE(GTK2 COMPONENTS gtk)
See the module for details
.. Original Message ...
On Thu, 18 Dec 2008 16:15:28 +0100 "Pierrick Grasland"
wrote:
>Hello all,
>
>I'm testing CMake with a little pr
On Fri, Dec 19, 2008 at 01:33:45AM +0800, Kermit Mei wrote:
> c++ -Wall -gstabs(or -g) main.cpp hello.cpp -o main
>
> How can I use cmake to do the same thing?
Add your -g flag to CMAKE_CXX_FLAGS or I think you can use
ADD_DEFINITIONS("-g").
tyler
___
hello, I want debug my project which is managed by cmake.
I don't know how to add the debug information to the program.
For example, I always compile my program by the following way:
c++ -Wall -gstabs(or -g) main.cpp hello.cpp -o main
Then I can use gdb to debug it.
How can I use cmake to
Is there a recommended way to organize our cmake files?
Thanks,
Jon
From: David Cole
To: Jon Shuler
Cc: cmake@cmake.org
Sent: Thursday, December 18, 2008 11:03:33 AM
Subject: Re: [CMake] Multiple CMakeLists.txt in the same directory
Well, if you want to organ
Well, if you want to organize things that way, you could have one
CMakeLists.txt file and then Project1.cmake, Project2.cmake
and then:
CMakeLists.txt:
==
cmake_minimum_required(VERSION 2.6)
project(AllProjects)
include(${CMAKE_CURRENT_SOURCE_DIR}/Project1.cmake)
include(${CMAKE_C
Jon Shuler schrieb:
Right now we have a build\win32 directory that contains all the projects
files. I was looking at creating a CMakeLists.txt for each project and
putting them in the same directory. I rather have separate
CMakeLists.txt for each project instead of one big file.
How would t
Right now we have a build\win32 directory that contains all the projects files.
I was looking at creating a CMakeLists.txt for each project and putting them
in the same directory. I rather have separate CMakeLists.txt for each project
instead of one big file.
How would this work based on what
Consider a CMakeLists.txt file as if it were one of your project files. You
will use the CMakeLists.txt file to generate project files after converting
to cmake. You should be able to write one that references your source, just
as you reference your source from your existing VS project files.
The
On Thu, Dec 18, 2008 at 08:12:46AM -0800, Jon Shuler wrote:
> I am looking at converting our build system to cmake and have found an issue.
> We keep all the project files (VS 6, VS 2003 and VS 2008) in one common
> directory that is separate from the source tree. Based on what I read it
> loo
I am looking at converting our build system to cmake and have found an issue.
We keep all the project files (VS 6, VS 2003 and VS 2008) in one common
directory that is separate from the source tree. Based on what I read it looks
like CMake expects the CMakeLists.txt to exist in the same direct
Bill,
I am having all kinds of trouble with the extended Ctest scripting mode.
Here are just some of the problems:
1) Can't get memory checking to work
2) Can't get coverage testing to work
3) Getting submition errors like:
Error when triggering:
?xmlfile=godel.sandia.gov___Linux-gcc-ser
Hello all,
I'm testing CMake with a little project, but I encounter a problem with GTK.
I have the following architecture with CMake 2.6-patch2 on ubuntu 8.04 :
src/
gui/
tools/
target/
My goal is to generate my project in target.
So I created a CMakeLists.txt in src :
cmake_minimum_requi
Tron Thomas wrote:
I need to be able to run a certain unit from a specific directory so
that it will be able to find some supporting file that are needed for
the test. However CTest insists on launching the test from a
different location.
I tried using the --build-run-dir and --build-exe-di
Bartlett, Roscoe A wrote:
Bill,
How do you set CTEST_DROP_SITE and CTEST_DROP_LOCATION in the extended Ctest
script? I don't see an example of that in the script you point to below.
Thanks,
Usually those are in the projects CTestConfig.cmake file that goes in
the root of the source tree.
tormod.ravnanger.lan...@dnv.com wrote:
---
Intel(R) Visual Fortran Compiler Professional for applications running
on IA-32, Version 11.0Build 20081105 Package ID: w_cprof_p_11.0.066
Copyright (C) 1985-2008 Intel Corporation. All rights reserved.
30 DAY EVALUATION LICENSE
if
2008/12/16 Tyler Roscoe :
> I am using what I think is a common pattern to create some headers.
> Following the example at
> http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_generate_an_executable.2C_then_use_the_executable_to_generate_a_file.3F,
> I have an add_custom_command which calls a script (gen
> -Original Message-
> From: Arjen Markus [mailto:arjen.mar...@wldelft.nl]
> Sent: 18. desember 2008 09:36
> To: Landet, Tormod Ravnanger
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Problems with Intel Fortran 11 on Windows XP
> >
> Would that not break when there are several versions ins
>> -Original Message-
>> OK, but we can't just apply the patch to CMake as it would break the
>> older version of Fortran. Is there a way to detect which version is
>> installed from the registry or something? I am glad you are working,
>> but to get a solution for everyone, we need to g
> -Original Message-
> From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
> Sent: 17. desember 2008 21:14
> To: Landet, Tormod Ravnanger
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Problems with Intel Fortran 11 on Windows XP
>
> > For the list and search engines: to make CMake 2.6.2
41 matches
Mail list logo
