Bill Hoffman wrote:
> On 2/14/2014 11:00 AM, Abe Bachrach wrote:
>
>> I'd only want to do a full build if one of the CMakeLists.txt has
>> changed (cmake needs to get re-run). Otherwise, I'd like to do a normal
>> build.
>>
> That seems a bit over kill to m
I'd only want to do a full build if one of the CMakeLists.txt has changed
(cmake needs to get re-run). Otherwise, I'd like to do a normal build.
On Thu, Feb 13, 2014 at 4:52 AM, Ian Liu Rodrigues wrote:
> You are correct that I would prefer that behavior, however I'd prefer to
>> go for safety
On Wed, Feb 12, 2014 at 8:53 AM, Matthew Woehlke <
mw_tr...@users.sourceforge.net> wrote:
>
> What you really want is to record the "old" list of output files, re-run
> CMake, then remove any files on that list that no longer have rules to
> generate them. If you do a complete 'clean' you will dele
Hi there,
The Makefile that cmake generates includes a rule to automatically re-run
cmake if any of the input CMakelists.txt files change.
Is there a way to configure this rule to have it run clean first?
Currently, if you change the name of an executable target (or library), it
will leave the
In the cmake documentation for target_link_libraries() it says that:
> The named must have been created in the current directory by a
> command such as add_executable or add_library.
Can someone provide a reason for that, and is there a work-around?
We have a large project that is composed o
request?
-=Abe
On Sat, Sep 4, 2010 at 9:17 AM, David Cole wrote:
> On Sat, Sep 4, 2010 at 8:51 AM, Michael Hertling wrote:
>
>> On 09/04/2010 02:32 AM, Abe Bachrach wrote:
>> > Hi there,
>> > is there a way to change the color scheme that cmake uses while
>&g
Hi there,
is there a way to change the color scheme that cmake uses while building??
I would rather not have the message for linking be red, since this
immediately makes me think there was an error.
thanks,
-=Abe
___
Powered by www.kitware.com
Visit ot
