<div dir="ltr"><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large">I recommend using <a href="https://github.com/llvm-project/llvm-project-20170507">https://github.com/llvm-project/llvm-project-20170507</a> if you can spare 1.1 GB of disk and bandwidth for the initial checkout and git repo itself.</div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large"><br></div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large">It's just a few minutes behind the svn master copies. I don't know of a better monorepo at present.</div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large"><br></div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large">Although everything is there, things such as clang and compiler-rt aren't actually built unless you saymlink them into the appropriate place in the llvm directory.</div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large"><br></div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large">If you want to actually submit patches then you'll need to make patch files and send them to the svn master.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 13, 2018 at 10:37 PM, Martin J. O'Riordan via llvm-dev <span dir="ltr"><<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-IE" link="#0563C1" vlink="#954F72"><div class="m_2922033999840795522WordSection1"><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif">Hi LLVM Devs,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif">I recently finished working for Intel/Movidius, and thought that before I start working on some new LLVM project, that this would be a good time to discard all of my old practices (which began with v2.7, and has gathered crud over the years) and restart with a brand new fresh LLVM approach directly from head.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif">In preparation for doing this, I would like to know what is the current status of using GIT vs SVN and should I start afresh with the GIT repositories? There is also the issue of Mono vs Multiple repositories, and which I select will be somewhat dictated by recommended best approach, and how big the Mono repository is to clone for the first time as I have ISP download caps to contend with. I would prefer to have a Mono installation, and that way be able to track future development of all LLVM projects; but I also need to be able to enable and disable subprojects cleanly as I need them - for instance, at this time I am not yet ready for LLD and I don’t need DragonEgg, so although they are in the Mono repository, I need to be able to configure my build to exclude them.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif">Mostly I expect that I will be working on cross-compilers for embedded systems, so cross-compilation of the libraries is important. Historically I have done this with my own hand-crafted build systems (for LibC++ and Compiler-RT), but would like to do this with the integrated LLVM prescribed approach when possible.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif">For testing I have never used the LLVM test-suite, nor the LIT and LNT frameworks, but in a fresh context I would like to get these up and running as soon as possible. My primary development platform is Windows, with various Linux distros for verifying my development. And if possible, I would like to construct a private BuildBot for each target I am working on that mirrors the LLVM community BuildBots - but this is also something I have never done. To date, all of my testing for cross-development systems has used bespoke test harnesses and I would like to learn how to run the standard testing too; especially on Windows (8.1 and 10).<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif">Advice on getting set up with a fresh start would be greatly appreciated, as well as Newbie advice for how to test LLVM since in this regard I am a newbie.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif">Thanks,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif"> MartinO<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Book Antiqua",serif"><u></u> <u></u></span></p></div></div><br>______________________________<wbr>_________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/llvm-dev</a><br>
<br></blockquote></div><br></div>