Dieter Oberkofler wrote:
This does sound very interesting but I'm not sure if I understand how this
might replace my need for a wrapper.
To better understand, it would be most helpful, if you could eventually post
a short CMakeLists.txt snipped on how to capture the output from a
compile/link
I might sound old fashioned but I'm still only building from the command
line and only use an IDE (XCode on Mac and VS on the PC) when debugging.
I therefore manually changed the CMake compile and link rules to always
generate an error file for each file that gets compiled or linked.
This is quite
2009/7/15 Dieter Oberkofler doberkofler.li...@gmail.com:
I might sound old fashioned but I'm still only building from the command
line and only use an IDE (XCode on Mac and VS on the PC) when debugging.
OK, command line is great :-)
I usually edit in some editors (vi, [x]emacs, eclipse etc...)
no longer needed.
Thank you,
-D
-Original Message-
From: Eric Noulard [mailto:eric.noul...@gmail.com]
Sent: Wednesday, July 15, 2009 2:12 PM
To: Dieter Oberkofler
Cc: CMake@cmake.org
Subject: Re: [CMake] Processing the output from CMake build
2009/7/15 Dieter Oberkofler
2009/7/15 Dieter Oberkofler doberkofler.li...@gmail.com:
But I do not need that feature, would you explain why
you need the 1 file compiled - 1 file error mapping?
Generally speaking to keep track of each individual file status. This
especially useful, when dealing with compiler warnings that
CVS CMake/CTest has a new wrapper mode that can be used.It is set
with CTEST_USE_LAUNCHERS=1.
-Bill
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep
2009/7/15 Bill Hoffman bill.hoff...@kitware.com:
CVS CMake/CTest has a new wrapper mode that can be used. It is set with
CTEST_USE_LAUNCHERS=1.
I'm not sure to understand that.
How can it be used?
What does it make?
Is there some doc for this ? On the Wiki ? In a source file?
--
Erk
Eric Noulard wrote:
2009/7/15 Bill Hoffman bill.hoff...@kitware.com:
CVS CMake/CTest has a new wrapper mode that can be used.It is set with
CTEST_USE_LAUNCHERS=1.
I'm not sure to understand that.
How can it be used?
What does it make?
Is there some doc for this ? On the Wiki ? In a
2009/7/15 Bill Hoffman bill.hoff...@kitware.com
Eric Noulard wrote:
2009/7/15 Bill Hoffman bill.hoff...@kitware.com:
CVS CMake/CTest has a new wrapper mode that can be used. It is set
with
CTEST_USE_LAUNCHERS=1.
I'm not sure to understand that.
How can it be used?
What does it make?
.
Thank you!
-D
-Original Message-
From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
Sent: Wednesday, July 15, 2009 6:15 PM
To: Eric Noulard
Cc: Dieter Oberkofler; CMake@cmake.org
Subject: Re: [CMake] Processing the output from CMake build
Eric Noulard wrote:
2009/7/15 Bill
Subject: Re: [CMake] Processing the output from CMake build
2009/7/15 Dieter Oberkofler doberkofler.li...@gmail.com:
But I do not need that feature, would you explain why
you need the 1 file compiled - 1 file error mapping?
Generally speaking to keep track of each individual file status
2009/7/15 Dieter Oberkofler doberkofler.li...@gmail.com:
Since the build is done by the target generator
(make, nmake, etc...) I would say the change should
be made in each generator you are wanting to support/use
beginning with Makefile generator.
This is correct.
1) On first invocation of
12 matches
Mail list logo
