Ja som tiez za. Marek On Mon, Feb 18, 2019 at 4:42 PM Khem Raj <raj.k...@gmail.com> wrote:
> On Mon, Feb 18, 2019 at 7:15 AM Alexander Kanavin > <alex.kana...@gmail.com> wrote: > > > > On Mon, 18 Feb 2019 at 16:04, Khem Raj <raj.k...@gmail.com> wrote: > > > > There is now an official git repo for llvm, which also has version > tags: > > > > > > > > https://github.com/llvm/llvm-project > > > > > > yes there is and its intentional to use this mirror, since the > > > llvm-project is a super repo and > > > contains all llvm projects sources which is going to clone tonne > > > unnecessary code. > > > > More than half the commits are llvm's. (llvm-only mirror repo 175k, > > llvm super-repo 310k) > > So it adds to the clone, but not that much. > > I would have preferred to use mono repo and I have no problems using > it since thats what we > use in meta-clang as wella and it would make it simpler to reuse. but > it can be a pain for other people. > > 310k, I am not sure what is measured here. But here is the breakdown > of sizes for information > > 1.5G . > 676M ./.git > 16M ./lld > 51M ./libcxx > 3.5M ./libclc > 31M ./llgo > 32M ./polly > 395M ./llvm > 43M ./compiler-rt > 988K ./pstl > 116K ./debuginfo-tests > 720K ./libunwind > 13M ./clang-tools-extra > 7.3M ./openmp > 6.3M ./libcxxabi > 105M ./lldb > 352K ./parallel-libs > 155M ./clang > > > > > > The point is something else: > > - llvm-mirror is not an official repo, and may become stale/unmaintained > > - llvm-mirror does not have version tags, so we can't trace commit ids > > to the releases, or track upstream development with automatic tools > > > > I think these two things outweigh the extra clone overhead. > > > > > > I'll make a patch to switch over to that. > > > > > > > > Also note that final 8.0 is not yet out, so the recipe shouldn't make > > > > it look like it is. > > > > > > This is intentional too. > > > Its in rc stages and there are no specific chages espcially in > > > versioning schemes > > > which will mark it rc etc. > > > > What I mean is there is no mention whatsoever that the recipe is > > currently building a pre-release. It's not in PV, it's not anywhere in > > the recipe. This can mislead people. > > Yes it can however, we know that when next release is cut out from > master then we will be > on a 8.x release. > > > > > Alex > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > -- as simple and primitive as possible ------------------------------------------------- Marek Belisko - OPEN-NANDRA Freelance Developer Ruska Nova Ves 219 | Presov, 08005 Slovak Republic Tel: +421 915 052 184 skype: marekwhite twitter: #opennandra web: http://open-nandra.com
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
