search for: llvm_distribution_components

Hi all, I want to use the LLVM_DISTRIBUTION_COMPONENTS support to create an installed toolchain image (via the install-distribution target). I'd also like the installed binaries to be stripped. If you're invoking a cmake install script directly, you can pass -DCMAKE_INSTALL_DO_STRIP=1 to cmake to request stripping. The install-* targets set up...

Hey Chris, Sedat was asking for a way to "to speedup my build" and those blog posts were really helpful to me. Anyway LLVM_DISTRIBUTION_COMPONENTS sounds very cool, hope you will push your code soon! On Tue, Mar 1, 2016 at 11:32 PM, Chris Bieneman <cbieneman at apple.com> wrote: > Fabio, the work I was mentioning here is an extension beyond those blog > posts. > > Some details: > > * The “almost 40%” number I referre...

...hen the v3.8.0 FINAL is released. > > - Sedat - > > On 3/2/16, Fabio Pagani <pagabuc at gmail.com> wrote: >> Hey Chris, >> >> Sedat was asking for a way to "to speedup my build" and those blog posts >> were really helpful to me. >> Anyway LLVM_DISTRIBUTION_COMPONENTS sounds very cool, hope you will push >> your code soon! >> >> On Tue, Mar 1, 2016 at 11:32 PM, Chris Bieneman <cbieneman at apple.com> >> wrote: >> >>> Fabio, the work I was mentioning here is an extension beyond those blog >>> posts. >>...

...conf did. To help with this or CMake system has lots of convenient > "install-${name}" targets that support component-based installation. Not > every component has one of these rules, but if one you need is missing let > me know. I also recently (r261681) added a new option > (LLVM_DISTRIBUTION_COMPONENTS) that allows you to specify a list of > components that have custom install targets. It then creates a new > "install-distribution" target that wraps just the components you want. For > Apple this is almost a 40% speed up over "ninja install". > > > > That s...

I configure LLVM build with this command cd llvm-8.0.0.src & md buildsys-x64-MT & cd buildsys-x64-MT & cmake -G "Ninja" -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_BUILD_TYPE=Release -DLLVM_USE_CRT_RELEASE=MT -DLLVM_ENABLE_RTTI=1 -DLLVM_ENABLE_TERMINFO=OFF -DCMAKE_INSTALL_PREFIX=../x64-MT .. The number of build objects grew with every major release to 1660 for LLVM 7 and 1761 for

...behalf of Shoaib Meenai via llvm-dev" <llvm-dev-bounces at lists.llvm.org on behalf of llvm-dev at lists.llvm.org> wrote: (accidentally sent the previous one to llvm-commits instead of llvm-dev, sigh) Hi all (CC beanz for CMake advice), I stumbled into an issue with LLVM_DISTRIBUTION_COMPONENTS. The simplest way to reproduce is to run a configure with `-DLLVM_DISTRIBUTION_COMPONENTS=clang`. This should show lots of errors of the following form: CMake Error: install(EXPORT "ClangTargets" ...) includes target "clang" which requires target "LLVMAArch...

...;all" than autoconf did. To help with this or CMake system has lots of convenient "install-${name}" targets that support component-based installation. Not every component has one of these rules, but if one you need is missing let me know. I also recently (r261681) added a new option (LLVM_DISTRIBUTION_COMPONENTS) that allows you to specify a list of components that have custom install targets. It then creates a new "install-distribution" target that wraps just the components you want. For Apple this is almost a 40% speed up over "ninja install". That sounds great, I want to use it! It...

> Which combination of cmake/ninja versions are you using (latest are > v3.4.3 and v1.6.0)? > With this combination I could reduce build-time down from approx. 3h down to 01h20m. $ egrep -i 'jobs|ninja' llvm-build/CMakeCache.txt //Program used to build from build.ninja files. CMAKE_MAKE_PROGRAM:FILEPATH=/opt/cmake/bin/ninja //Define the maximum number of concurrent compilation

...;>> On 3/2/16, Fabio Pagani <pagabuc at gmail.com> wrote: >>>> Hey Chris, >>>> >>>> Sedat was asking for a way to "to speedup my build" and those blog >>>> posts >>>> were really helpful to me. >>>> Anyway LLVM_DISTRIBUTION_COMPONENTS sounds very cool, hope you will >>>> push >>>> your code soon! >>>> >>>> On Tue, Mar 1, 2016 at 11:32 PM, Chris Bieneman <cbieneman at apple.com> >>>> wrote: >>>> >>>>> Fabio, the work I was mentioning here...

...dual tools in the LLVM and Clang projects. I believe we should eliminate those options, which will result in the `all` target always being everything. We have explicit clean dependencies for the `check-*` targets so most developer workflows should be un-impacted. Distribution workflows can use the `LLVM_DISTRIBUTION_COMPONENTS` option to hand tailor which parts of LLVM to build and install with better control without as much complication. Many other options exist to support a wide variety of divergent workflows. For example, the `LLVM_EXTERNAL_${PROJECT}_SOURCE_DIR` options exist to allow users to specify custom paths f...

On Sun, 1 May 2016 at 16:12 Amaury SECHET <deadalnix at gmail.com> wrote: > Some update on this. > > 2016-04-12 18:48 GMT-07:00 Andrew Wilkins <axwalk at gmail.com>: > >> On Wed, 13 Apr 2016 at 09:38 Amaury SECHET <deadalnix at gmail.com> wrote: >> >>> I'd be happy to do it, but this is a bit much high level for me to be >>>

...dual tools in the LLVM and Clang projects. I believe we should eliminate those options, which will result in the `all` target always being everything. We have explicit clean dependencies for the `check-*` targets so most developer workflows should be un-impacted. Distribution workflows can use the `LLVM_DISTRIBUTION_COMPONENTS` option to hand tailor which parts of LLVM to build and install with better control without as much complication. > > Many other options exist to support a wide variety of divergent workflows. For example, the `LLVM_EXTERNAL_${PROJECT}_SOURCE_DIR` options exist to allow users to specify cust...

On Thu, Feb 25, 2016 at 7:37 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> On Feb 24, 2016, at 9:55 PM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi, >> >> I switched from "configure and make" to "cmake" build-system and >> wanted to speedup my build. >> >> In my build-script I

...dual tools in the LLVM and Clang projects. I believe we should eliminate those options, which will result in the `all` target always being everything. We have explicit clean dependencies for the `check-*` targets so most developer workflows should be un-impacted. Distribution workflows can use the `LLVM_DISTRIBUTION_COMPONENTS` option to hand tailor which parts of LLVM to build and install with better control without as much complication. >> >> Many other options exist to support a wide variety of divergent workflows. For example, the `LLVM_EXTERNAL_${PROJECT}_SOURCE_DIR` options exist to allow users to spec...

...minate > those options, which will result in the `all` > target always being everything. We have > explicit clean dependencies for the `check-*` > targets so most developer workflows should be > un-impacted. Distribution workflows can use > the `LLVM_DISTRIBUTION_COMPONENTS` option to > hand tailor which parts of LLVM to build and > install with better control without as much > complication. > > Many other options exist to support a wide > variety of divergent workflows. For example, > the `LLVM_EXTERNAL_${PROJE...