From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 3 Mar 2015 14:29:01 +0100 Subject: [Buildroot] [RFC v3 00/30] Add per-package staging feature In-Reply-To: <1425374255-6827-1-git-send-email-fabio.porcedda@gmail.com> References: <1425374255-6827-1-git-send-email-fabio.porcedda@gmail.com> Message-ID: <20150303142901.5998a72c@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Fabio Porcedda, On Tue, 3 Mar 2015 10:17:05 +0100, Fabio Porcedda wrote: > this patch set aims to improve build reproducibility by using a > per-package staging directory. > Also this feature aims to enable as default the top-level parallel make. Interesting! I must say I'm a bit worried about the implications of having to pass custom -I and -L flags all the time: we did arrange the compiler do not require those (by configuration for the internal toolchain case, and using the wrapper for the external toolchain case). Could you give some hints about the performance impact of those copies of the staging directory? Does it continue to make the top-level parallel build thing useful? I.e can you compare in terms of build time the following cases: * Normal non-top-level parallel build. * A top-level parallel build without this PPS feature * A top-level parallel build with this PPS feature Preferably something with a fairly deep dependency tree, i.e lots of small packages that depend on each other. A X.org stack + gtk2 would be a good example. Thanks! Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com