<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, Jun 18, 2015 at 5:07 PM John Criswell <<a href="mailto:jtcriswel@gmail.com">jtcriswel@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
    <div>On 6/18/15 6:49 PM, Eric Christopher
      wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">Hi John,
        <div><br>
        </div>
        <div>Long term we don't want to keep the burden of two build
          systems in tree. CMake is turning out to be the build system
          we want because of its multi-platform support, etc and as soon
          as the CMake system can do everything we can do with the
          autoconf/makefile build I plan on turning down the support for
          that and removing the code.</div>
      </div>
    </blockquote>
    <br></div><div bgcolor="#FFFFFF" text="#000000">
    Thanks, but I wasn't asking about autoconf vs. cmake.<br>
    <br></div></blockquote><div><br></div><div>Well, you are, but only sorta. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
    I'm wanting to know whether the ability to "plug into" the LLVM
    build system by external projects will be maintained.  For example,
    SAFECode doesn't have its own build system; it uses LLVM's, and it
    does so without being a "patch" to the LLVM source tree.  You can
    put the SAFECode source code anywhere you like, use LLVM-style
    Makefiles in its source code, and build it.  All of the
    PROJ_SRC_ROOT, PROJ_OBJ_ROOT magic in the autoconf build system is
    what permits that feature to work.<br>
    <br>
    Do you intend to keep this functionality when you replace autoconf
    with cmake, or will all projects that want to use the LLVM build
    system need to place their source code in the LLVM source tree?  To
    put it another way, do you intend to deprecate the
    PROJ_SRC_ROOT/PROJ_OBJ_ROOT stuff?<br>
    <br>
    While I've enjoyed the PROJ_* magic, I can see why you'd want to get
    rid of it.  I just want to ensure that you are not planning on
    replacing it.<br>
    <br></div></blockquote><div><br></div><div>Right. So this is a "autoconf/makefile build system vs cmake build system" question as the Makefiles would, theoretically, all go away at the end. I don't think anyone has plans of replacing this functionality (Chris?), but migrating out of tree projects to hook in via modifying the cmake build locally shouldn't be too bad.</div><div><br></div><div>-eric</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
    Regards,<br>
    <br>
    John Criswell</div><div bgcolor="#FFFFFF" text="#000000"><br>
    <br>
    <blockquote type="cite">
      <div dir="ltr">
        <div>Thanks!</div>
        <div><br>
        </div>
        <div>-eric<br>
          <br>
          <div class="gmail_quote">
            <div dir="ltr">On Thu, Jun 18, 2015 at 4:47 PM John Criswell
              <<a href="mailto:jtcriswel@gmail.com" target="_blank">jtcriswel@gmail.com</a>>
              wrote:<br>
            </div>
            <blockquote class="gmail_quote">Dear All,<br>
              <br>
              Will the LLVM project system (the extension to the build
              system that<br>
              allows sub-projects to reuse the LLVM Makefiles) be
              maintained long<br>
              term, or is the slow push to CMake intending to deprecate
              this<br>
              functionality?<br>
              <br>
              We used this feature a lot for research projects at UIUC,
              but if the<br>
              current maintainers of the build system are planning on
              deprecating it,<br>
              I'll have my students avoid using it.<br>
              <br>
              Regards,<br>
              <br>
              John Criswell<br>
              <br>
              --<br>
              John Criswell<br>
              Assistant Professor<br>
              Department of Computer Science, University of Rochester<br>
              <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cs.rochester.edu_u_criswell&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=-J4LAdmf0ISN0pp3SokS90LjCILV_JAFRyxeK4z5tKE&s=BuyJWJYlBgVkrB6x_D_EBKY02w2qmfRxxYp2BL1IKI8&e=" rel="noreferrer" target="_blank">http://www.cs.rochester.edu/u/criswell</a><br>
              <br>
              _______________________________________________<br>
              LLVM Developers mailing list<br>
              <a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> 
                     <a href="http://llvm.cs.uiuc.edu" rel="noreferrer" target="_blank">http://llvm.cs.uiuc.edu</a><br>
              <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" rel="noreferrer" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
            </blockquote>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <br>
    <pre cols="72">-- 
John Criswell
Assistant Professor
Department of Computer Science, University of Rochester
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cs.rochester.edu_u_criswell&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=-J4LAdmf0ISN0pp3SokS90LjCILV_JAFRyxeK4z5tKE&s=BuyJWJYlBgVkrB6x_D_EBKY02w2qmfRxxYp2BL1IKI8&e=" target="_blank">http://www.cs.rochester.edu/u/criswell</a></pre>
  </div></blockquote></div></div>