search for: ninjas

Just posted this fix on ninja's github page, but figured I'd share it with a larger audience. Every time I run cmake && ninja in a new build directory, ninja will rerun cmake because the entry for build.ninja in .ninja_log is older than the timestamp on CMakeCache.txt, even if the timestamps on the actual file isn't older. The following patch fixes the problem, i.e.,

Wow, this is seriously fast on Windows! I've been using Ninja on Linux/Mac for awhile now, I'm glad to see it working on Windows now. On Wed, Jun 13, 2012 at 5:09 PM, =?utf-8?Q?=C3=93scar_Fuentes?= < ofv at wanadoo.es> wrote: > Nikola Smiljanic <popizdeh at gmail.com> writes: > > > Could somebody please provide more info. What exactly is ninja (I'm > >

On Sat, Aug 8, 2020 at 2:22 PM Dmitry Mikushin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Ninja is really good, indeed. The only problem I've seen is that LLVM linking step (made massively parallel by Ninja) renders the 8GB RAM system unresponsive due to excessive swapping. FWIW, there is a way to limit the number of parallel link jobs in particular (so compile jobs can

A tiny question (I hardly know what Ninja is, but am looking forward to trying it out): Does the changes also work with MinGW builds? I've got a Windows buildbot slave that does nothing but building LLVM+Clang using MinGW64 all day, every day. Or, is it only for Visual Studio? 2012/6/13 Justin Holewinski <justin.holewinski at gmail.com> > Wow, this is seriously fast on Windows!

I'm just wondering if anyone's using Ninja (which buffers output from subcommands, such as lit/FileCheck/etc) & has thought about/found a way to force FileCheck to use colour in spite of Ninja's buffering. Thanks, - David

(resend to the list) And of course, just as I say that, my next ninja build shows the line only once. On reflection I am less sure that the lack of a [N/M] line means they are from the same invocation. Surely ninja could spawn two links, which then independently report "Creating library" after ninja emits the [N/M] lines. --paulr From: llvm-dev [mailto:llvm-dev-bounces at

Hi, Ninja is being mentioned more and more frequently on this list, but I don't think anybody has introduced it formally. Ninja is, briefly put, a super-fast replacement for GNU Make, nmake, and all the other make tools out there. For those of you who are a bit reluctant to waste time on Ninja or don't know what it is, I can strongly urge you to download it from

You can set the LLVM_PARALLEL_LINK_JOBS CMake variable to restrict the number of link jobs. On Sat, Aug 8, 2020 at 3:00 PM Neil Nelson via llvm-dev < llvm-dev at lists.llvm.org> wrote: > https://ninja-build.org/manual.html > > ninja -h prints help output. Many of Ninja’s flags intentionally match > those of Make; e.g ninja -C build -j 20 changes into the build directory >

Nope. An easy solution (both here and for clang) is for ninja to set an environment variable (`NINJA_ISATTY`?), and add some magic to LLVM's "isatty" to return true if it sees it. (for matters of correctness, it would actually be best if ninja sets the environment variable only when *it's* stdout/stderr isatty (also taking into account this environment variable), so that

Hi, I was trying Ninja to build the LLVM sources. I am using cmake version 2.8.8, latest ninja from git and latest LLVM from git. Here's what I tried: $ cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=... /path/to/src $ ninja $ ninja install The installation aborted with the message below: CMake Error at utils/TableGen/cmake_install.cmake:36 (FILE): file INSTALL cannot

I built my first submission with Visual Studio, but everything I read and watch suggests Ninja, about which I know nothing. Is it okay if I rerun CMake with -G "Ninja" in the same build directory, then just run ninja?

> On Aug 8, 2020, at 3:32 PM, Dmitry Mikushin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Cool, thanks! > > вс, 9 авг. 2020 г. в 00:27, Petr Hosek <phosek at chromium.org <mailto:phosek at chromium.org>>: > You can set the LLVM_PARALLEL_LINK_JOBS CMake variable to restrict the number of link jobs. IMO, a more thorough solution would be switching to

I've got a i7 with 12 logical cores and 16GB of RAM I successfully built RELEASE_390/final but for the last 100 or so files I'd to use "ninja -j2" so as not to keep from swapping in the best case and and in the worst case the build kills itself without completing because apparently its run out of memory. For the first 3200 files or so it was doing just fine with

Hi Mikael, > My Clang build used to take 59:29 minutes using MinGW Makefiles. With > Ninja, it takes 18:43 minutes! That's a speed up of factor three. sorry for asking the obvious question: Are you comparing against a parallel "make -j<n>"? :-) Best regards, Christoph

Since there's no "[2663/3121] " line between the two messages, the two lines are from the same link.exe invocation. I don't know why link.exe thinks it needs to print this line twice, ninja doesn't have anything to do with it. On Mon, Nov 19, 2018 at 6:57 PM <paul.robinson at sony.com> wrote: > I'm more concerned about seeing the message come out twice, which

On 31 October 2016 at 19:46, Galina Kistanova <gkistanova at gmail.com> wrote: > I applied it and reconfigured the master. Thanks Galina! Marco, the build is complaining about Ninja: http://lab.llvm.org:8011/builders/clang-bpf-build/builds/414/steps/cmake%20stage%201/logs/stdio CMake was unable to find a build program corresponding to "Ninja" Now I remember we used ninja by

...have other options to speedup my build? > > Yes: start to use ninja ;) > If for any reason (?) you are really stuck with "make", then run "make -j ~ncpus" (with ~ncpus "approximately the number of cores in your machine). It will build in parallel. > So, I like NinjaS but I have not used it yet as software. >From my build-script... [ -d ${BUILD_DIR} ] || mkdir -p ${BUILD_DIR} cd $BUILD_DIR # BUILD-VARIANT #1: CONFIGURE AND MAKE (will be DEPRECATED with LLVM v3.9) ##../llvm/configure $CONFIGURE_OPTS 2>&1 | tee $LOGS_DIR/$CONFIGURE_LOG_FILE ##$MAKE $M...

Building LLVM with Visual Studio is a bit of a pain because the available methods are slow and doesn't make good use of multiprocessor systems. >From now on it is possible to build LLVM+Clang with the usual cmake method but using Ninja, an ultra-fast tool that knows how to take advantage of the availabe execution threads. Ultra-fast is no exageration: with a warm cache, a no-op build of

On further thought, I assume this issue actually hits everyone - it's not just Ninja getting in the way, but lit as well. (which also means we'd probably need to fix both Ninja and lit to resolve this issue - but everyone should at least be a little invested in fixing lit). On Sun, Jan 6, 2013 at 12:18 AM, Sean Silva <silvas at purdue.edu> wrote: > Nope. An easy solution (both

I don’t personally develop on Mac (i use Windows), but I have an analogous setup there where i use ninja to build and Visual Studio for editing, debugging, etc. What i do, and I assume it will be the same or very similar for Xcode, is to run cmake twice, once with Ninja, and once with VS (Xcode for you), from separate directories. I build with the ninja one (“ninja clang” on command line), and I