search for: checout

...ecify -DLLVM_BUILD_EXTERNAL_COMPILER_RT=On, which will configure > compiler-rt using the just-built clang after clang is built. > I thought the BUILD_EXTERNAL variables were for use when projects were not embedded within the llvm source tree (mostly in use by Takumi's flat buildbots that checout the top-level project without embedding, say, clang or compiler-rt within the llvm source tree)? > > 2) The new way, is to place compiler-rt under LLVM/runtimes. In this path > the build system will automatically build with the just-built compiler. > This path also splits compiler-rt...

...EXTERNAL_COMPILER_RT=On, which will configure > compiler-rt using the just-built clang after clang is built. > > > I thought the BUILD_EXTERNAL variables were for use when projects were not > embedded within the llvm source tree (mostly in use by Takumi's flat > buildbots that checout the top-level project without embedding, say, clang > or compiler-rt within the llvm source tree)? > > > You are confusing this with the similarly > named LLVM_EXTERNAL_${nameUPPER}_SOURCE_DIR variables. > Ah, right - indeed. > > 2) The new way, is to place compiler-rt und...

...EXTERNAL_COMPILER_RT=On, which will configure > compiler-rt using the just-built clang after clang is built. > > > I thought the BUILD_EXTERNAL variables were for use when projects were not > embedded within the llvm source tree (mostly in use by Takumi's flat > buildbots that checout the top-level project without embedding, say, clang > or compiler-rt within the llvm source tree)? > > > You are confusing this with the similarly > named LLVM_EXTERNAL_${nameUPPER}_SOURCE_DIR variables. > > > Ah, right - indeed. > > > 2) The new way, is to place co...

...EXTERNAL_COMPILER_RT=On, which will configure > compiler-rt using the just-built clang after clang is built. > > > I thought the BUILD_EXTERNAL variables were for use when projects were not > embedded within the llvm source tree (mostly in use by Takumi's flat > buildbots that checout the top-level project without embedding, say, clang > or compiler-rt within the llvm source tree)? > > > You are confusing this with the similarly > named LLVM_EXTERNAL_${nameUPPER}_SOURCE_DIR variables. > > > Ah, right - indeed. > > > 2) The new way, is to place co...

On Wed, Mar 8, 2017 at 2:03 PM Sterling Augustine <saugustine at google.com> wrote: > Yes, this is a aspect of the larger problem that clang bootstrap doesn't > work for a cross-compiler. The build (mostly?) assumes that host==target > during the build of clang itself, and then if you want another architecture > also, you run a second build of the target libraries, and