From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: qt: monolithic or modular? Date: Sat, 9 Apr 2016 16:39:17 +0200 Message-ID: <20160409143917.GA22282@solar> References: <20160405072220.1d828a86@debian-netbook> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33849) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aou2o-0001ii-B8 for guix-devel@gnu.org; Sat, 09 Apr 2016 10:39:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aou2l-00016W-2x for guix-devel@gnu.org; Sat, 09 Apr 2016 10:39:26 -0400 Received: from mailrelay7.public.one.com ([91.198.169.215]:42203) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aou2k-00016S-Nw for guix-devel@gnu.org; Sat, 09 Apr 2016 10:39:23 -0400 Content-Disposition: inline In-Reply-To: <20160405072220.1d828a86@debian-netbook> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Efraim Flashner Cc: guix-devel@gnu.org On Tue, Apr 05, 2016 at 07:22:20AM +0300, Efraim Flashner wrote: > I try very hard to not build qt on my laptop, mostly because of the long build time (7 hours on hydra [0]). Currently we download and use the big download of qt[1] and frankly I'd rather not. Qt does also ship in smaller bits[2], 32 if I counted correctly. I propose we package the submodules and over time we go through the packages that use qt and switch out the monolithic qt for just the parts that the program actually uses. It makes it less daunting to build, should make the closures smaller, and means that if a submodule fails to build on an architecture then they only lose that module, not all of qt. This would be very welcome indeed! It would also make debugging easier (for instance, Qt-5 currently does not build on arm). If I understand correctly, we could in the beginning keep the modules in parallel with a monolithic build (thanks to different names qt and qtbase) and switch over one package using Qt after the other? Since you mentioned incomplete build systems for some modules, would it not be enough to add qtbase (which includes qmake, I suppose?) to their inputs? Andreas