<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="direction: inherit;"><br></div></div><div><br>On Sep 3, 2016, at 3:04 PM, Patrice Kouame <<a href="mailto:pkouame@mac.com">pkouame@mac.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span></span><br><span>+1 for keeping it separate. </span><br></div></blockquote><div style="direction: inherit;"><br></div><div style="direction: inherit;">Can you clarify what you referring to specifically?</div><div style="direction: inherit;">This sub thread (the last 4 messages) started with a mention of GCC dependencies. It is not clear to me how to relate to llvm now.</div><div style="direction: inherit;"><br></div><div style="direction: inherit;">Mehdi</div><div style="direction: inherit;"><br></div><blockquote type="cite"><div><span></span><br><span>One can easily set up a git subproject structure if the need is pressing...</span><br><span></span><br><span>Patrice</span><br><span></span><br><blockquote type="cite"><span>On Sep 3, 2016, at 5:39 PM, Mehdi Amini via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>On Sep 2, 2016, at 12:33 PM, Dimitry Andric via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>On 16 Aug 2016, at 00:12, Lawrence, Peter via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>As someone that has worked with both gcc and llvm,</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>One thing about gcc that drives me bat-guano-crazy is that</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>First you check out gcc, try to build it, and find that you also</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Need mpc, so you check that out and try to build it, and</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Find out you also need gmp, so you check that out and try</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>To build it, and find out that you also need mpfr, …..</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I can understand your frustration, but these are all completely external libraries, and it does not really make sense to include this into any mono-repository.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>For example, you are also dependent on libc headers, are you going to include these into your repository? And kernel headers? The end result will possibly include half of GitHub into that mono-repository... :)</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>So as usual, for any open source project, read the requirements first, and install those from whatever your local package management system is.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>If LLVM is going to use a mono-repository, it should only include LLVM components, in my opinion.</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>This seems a good principle in general, but note that we already included external projects in the repo. Out-of-my-head right now I can think of the google tests library, and ISL.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>— </span><br></blockquote><blockquote type="cite"><span>Mehdi</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>LLVM Developers mailing list</span><br></blockquote><blockquote type="cite"><span><a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a></span><br></blockquote><blockquote type="cite"><span><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a></span><br></blockquote></div></blockquote></body></html>