'Re: [CMake] COMMENT ignored for POST_BUILD custom command?'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cmake
Subject:    Re: [CMake] COMMENT ignored for POST_BUILD custom command?
From:       Chris Green <greenc () fnal ! gov>
Date:       2015-03-20 19:49:03
Message-ID: 550C79AF.9000500 () fnal ! gov
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On 3/20/15 2:10 PM, Nils Gladitz wrote:
> On 20.03.2015 19:41, Chris Green wrote:
>> On 3/20/15 12:11 PM, Christopher H Green wrote:
>>> Indeed it might, thank you, but I believe I'm seeing the same 
>>> behavior with ninja also.
>> I can confirm that with CMake 3.2.1, the expected COMMENT is printed 
>> with the UNIX Makefile generator, but not for the Ninja generator. 
>> Any chance of getting this fixed in an upcoming version? Several of 
>> our users are trying out Ninja, and liking what they see so far.
>>
>
> In the Makefile generators this was a regression but with the Ninja 
> generator this seems to have never been implemented.
>
> CMake Ninja builds are much less verbose than CMake's Makefiles and I 
> am personally quite fond of that fact.
> In a diagnostic free build (no warnings or errors) this often means a 
> single line of output for the entire build.
>
> You could make this a feature request on the issue tracker though.
Hi,

Thanks for this. I'm in favor of brief myself, but if I've decided I 
want a message by using the mechanism provided for same, in general I'd 
like to see it. I'll put the issue in the tracker.

Thanks again,
Chris.
>
> Nils

-- 
Chris Green <greenc@fnal.gov>, FNAL CS/SCD/ADSS/SSI/TAC;
'phone (630) 840-2167; Skype: chris.h.green;
IM: greenc@jabber.fnal.gov, chissgreen (AIM),
chris.h.green (Google Talk).

[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <br>
    <div class="moz-cite-prefix">On 3/20/15 2:10 PM, Nils Gladitz wrote:<br>
    </div>
    <blockquote cite="mid:550C70C2.9050706@gmail.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div class="moz-cite-prefix">On 20.03.2015 19:41, Chris Green
        wrote:<br>
      </div>
      <blockquote cite="mid:550C69DE.9000502@fnal.gov" type="cite"> On
        3/20/15 12:11 PM, Christopher H Green wrote:<br>
        <blockquote
          cite="mid:1xvn1m4orgwsx8h6ladayly8.1426871488368@email.android.com"
          type="cite">
          <meta name="Generator" content="Microsoft Exchange Server">
          <!-- converted from text -->
          <style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: \
#800000 2px solid; } --></style>  <div>
            <div>Indeed it might, thank you, but I believe I'm seeing
              the same behavior with ninja also.</div>
          </div>
        </blockquote>
        I can confirm that with CMake 3.2.1, the expected COMMENT is
        printed with the UNIX Makefile generator, but not for the Ninja
        generator. Any chance of getting this fixed in an upcoming
        version? Several of our users are trying out Ninja, and liking
        what they see so far.<br>
        <br>
      </blockquote>
      <br>
      In the Makefile generators this was a regression but with the
      Ninja generator this seems to have never been implemented.<br>
      <br>
      CMake Ninja builds are much less verbose than CMake's Makefiles
      and I am personally quite fond of that fact.<br>
      In a diagnostic free build (no warnings or errors) this often
      means a single line of output for the entire build.<br>
      <br>
      You could make this a feature request on the issue tracker though.<br>
    </blockquote>
    Hi,<br>
    <br>
    Thanks for this. I'm in favor of brief myself, but if I've decided I
    want a message by using the mechanism provided for same, in general
    I'd like to see it. I'll put the issue in the tracker.<br>
    <br>
    Thanks again,<br>
    Chris.<br>
    <blockquote cite="mid:550C70C2.9050706@gmail.com" type="cite"> <br>
      Nils<br>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Chris Green <a class="moz-txt-link-rfc2396E" \
href="mailto:greenc@fnal.gov">&lt;greenc@fnal.gov&gt;</a>, FNAL CS/SCD/ADSS/SSI/TAC; \
                'phone (630) 840-2167; Skype: chris.h.green;
IM: <a class="moz-txt-link-abbreviated" \
href="mailto:greenc@jabber.fnal.gov">greenc@jabber.fnal.gov</a>, chissgreen (AIM), \
chris.h.green (Google Talk). </pre>
  </body>
</html>

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: \
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more information \
on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at \
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[prev in list] [next in list] [prev in thread] [next in thread] 