<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Op 18-12-12 13:46, David Cole schreef:<br>
    </div>
    <blockquote
cite="mid:CAAdwe9UBzRxmqh=DhoaQ=YiC9+jsq2-9CAYSGMBL=xA-2zvrBw@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">On Mon, Dec 17, 2012 at 11:57 AM,
        Alexander Neundorf <span dir="ltr">&lt;<a
            moz-do-not-send="true" href="mailto:a.neundorf-work@gmx.net"
            target="_blank">a.neundorf-work@gmx.net</a>&gt;</span>
        wrote:<br>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
            <div class="im">On Monday 17 December 2012, David Cole
              wrote:<br>
            </div>
            <div class="im">&gt; I thought we wanted them to switch to
              the new behavior... Isn't that the<br>
              &gt; goal of emitting warnings from policy
              implementations...?<br>
              <br>
            </div>
            ...but not as long as the project still wants to keep the
            old minimum required<br>
            cmake version (or am I mixing things up) ?<br>
            <br>
            Alex<br>
          </blockquote>
        </div>
        <br>
      </div>
      <div class="gmail_extra"><br>
      </div>
      <div class="gmail_extra">No, you're not mixing things up. You're
        correct.</div>
      <div class="gmail_extra"><br>
      </div>
      <div class="gmail_extra">If somebody wants to use minimum required
        2.6.2 *and* they don't like warnings emitted by newer versions
        of CMake about new policies, then they have to change their
        code, or use the -D&nbsp;<span
style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;line-height:22px;text-align:justify">CMAKE_POLICY_DEFAULT_CMP&lt;NNNN&gt;&nbsp;</span>technique.</div>
      <div class="gmail_extra"><br>
      </div>
      <div class="gmail_extra">Now if they're going to change their code
        anyway, why not make a change that is compatible with the new
        policy introduced rather than adding a bunch of code to keep
        things in the OLD state. With many policies it is possible to
        write CMake code that honors the NEW state of the policy, but
        still works with older CMakes.</div>
      <div class="gmail_extra"><br>
      </div>
      <div class="gmail_extra">I would ask for specific advice regarding
        the particulars of the policy violation to see if there is such
        a way to re-write the code to work with older AND newer CMakes
        before I would ever consider setting a policy to OLD in my own
        CMakeLists files.</div>
      <div class="gmail_extra"><br>
      </div>
      <div class="gmail_extra"><br>
      </div>
      <div class="gmail_extra">HTH,</div>
      <div class="gmail_extra">David</div>
      <div class="gmail_extra"><br>
      </div>
      <div class="gmail_extra"><br>
      </div>
    </blockquote>
    I can send specific examples if you want. I'm not sure I can send
    attachments to the mailing list, though.<br>
    <br>
    Regards,<br>
    Marcel Loose.<br>
    <br>
  </body>
</html>