Lines Matching refs:projects
77 In addition, because Git seems to be replacing many OSS projects' version
85 projects. Any of these could replace the code-hosting infrastructure that we
103 The current SVN repository hosts all the LLVM sub-projects alongside each other.
105 all LLVM sub-projects.
168 Git views for the sub-projects (if the monorepo is selected).
212 sub-projects in a single source tree. It is often referred to as a monorepo and
214 own top-level directory. Not all sub-projects are used for building toolchains.
217 Putting all sub-projects in a single checkout makes cross-project refactoring
220 * New sub-projects can be trivially split out for better reuse and/or layering
223 * Changing an API in LLVM and upgrading the sub-projects will always be done in
227 * Tooling based on `git grep` works natively across sub-projects, allowing to
228 easier find refactoring opportunities across projects (for example reusing a
230 * Having all the sources present encourages maintaining the other sub-projects
234 the sub-projects move synchronously, and a single revision number (or commit
235 hash) identifies the state of the development across all projects.
243 all sub-projects together. It is trivial to configure builds for a single
284 undecided if these projects will continue to be maintained.
298 * :ref:`Commit an API Change in LLVM and Update the Sub-projects <workflow-cross-repo-commit>`.
344 from someone who would check out all the projects with SVN today.
353 The data for all sub-projects is still in your `.git` directory, but in your
358 Note that when you fetch you'll likely pull in changes to sub-projects you don't
359 care about. If you are using sparse checkout, the files from other projects
387 cd ../projects
405 cd ../../projects/
413 Note that the list would be longer with more sub-projects.
420 The repository contains natively the source for every sub-projects at the right
424 cd llvm-projects
432 Commit an API Change in LLVM and Update the Sub-projects
454 multiple sub-projects.
461 cd ../../projects/libcxx
469 cd ../../projects/libcxx
477 cd ../../projects/libcxx
509 sub-projects makes it possible to script around.
540 Also, since the monorepo handles commits update across multiple projects, you're
570 # your local mirror. All projects are listed here but you need only
725 things at ``U3`` since all of the upstream projects not participating
755 # Import histories for upstream split projects (this was probably
763 # Import histories for downstream split projects (this was probably
820 tools/clang, etc.). Let's also say ``projects/myproj`` is a submodule
827 projects/compiler-rt compiler-rt
828 projects/debuginfo-tests debuginfo-tests
829 projects/libclc libclc
830 projects/libcxx libcxx
831 projects/libcxxabi libcxxabi
832 projects/libunwind libunwind
835 projects/openmp openmp
837 projects/myproj local/myproj
842 map entries for all of the projects in your umbrella (except llvm).
858 # Import histories for upstream split projects (this was probably
866 # Import histories for downstream split projects (this was probably
883 echo "projects/compiler-rt compiler-rt" >> my-monorepo/submodule-map.txt
884 echo "projects/debuginfo-tests debuginfo-tests" >> my-monorepo/submodule-map.txt
885 echo "projects/libclc libclc" >> my-monorepo/submodule-map.txt
886 echo "projects/libcxx libcxx" >> my-monorepo/submodule-map.txt
887 echo "projects/libcxxabi libcxxabi" >> my-monorepo/submodule-map.txt
888 echo "projects/libunwind libunwind" >> my-monorepo/submodule-map.txt
891 echo "projects/openmp openmp" >> my-monorepo/submodule-map.txt
893 echo "projects/myproj local/myproj" >> my-monorepo/submodule-map.txt