From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id AB31A1381F3 for ; Sat, 25 May 2013 21:09:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C7257E0C56; Sat, 25 May 2013 21:09:50 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CA7CCE09A5 for ; Sat, 25 May 2013 21:09:49 +0000 (UTC) Received: from Nyx.local (dynamic-adsl-84-220-77-8.clienti.tiscali.it [84.220.77.8]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lu_zero) by smtp.gentoo.org (Postfix) with ESMTPSA id 58C9133E0C3 for ; Sat, 25 May 2013 21:09:48 +0000 (UTC) Message-ID: <51A12899.8020607@gentoo.org> Date: Sat, 25 May 2013 23:09:45 +0200 From: Luca Barbato User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Usage of dev-utils/ninja in ebuilds References: <51A1077E.1030607@gentoo.org> <20130525211750.61b81a57@TOMWIJ-GENTOO> In-Reply-To: <20130525211750.61b81a57@TOMWIJ-GENTOO> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 51f33a62-3ad9-4e31-8b08-4212f853ff2c X-Archives-Hash: 0c5426ebe71b0a5921a0356544598c8f On 5/25/13 9:17 PM, Tom Wijsman wrote: > On Sat, 25 May 2013 14:48:30 -0400 > Mike Gilbert wrote: > >> For those unaware, dev-util/ninja is a make-replacement created by one >> of the Chromium guys at Google. Its focus is on making incremental >> builds of large software faster. > > I've no idea how this would work out, so I'm asking some questions from > different perspective to form a better idea; this may step aside your > discussion but on the other hand could help other unaware developers. > > If I missed earlier ML discussions on this by not paying attention or > being too new, feel free to point me to those; no need to repeat. :) > Ninja is simpler than make and strives to be as essential as possible, for those that know exotic build system is a close relative to plan9 mk. Ninja doesn't make any effort to make its build rules human readable, as said they have to be generated by something else, not sure how easy/hard would be debug the generated file. Being what it is used by default by upstream, probably it makes sense using it for building chromium. Using it on cmake shouldn't make much, if any, difference speed wise and would just make cmake build require yet another building block so I wouldn't use it if there aren't clear advantages in doing so (somebody could benchmark so we can see how it fares) lu