From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Fri, 23 Aug 2013 09:36:42 +0200 Subject: [Buildroot] [PATCH v2 2/3] package: fix generic extract target for top-level parallel make In-Reply-To: <521513E3.8080401@mind.be> References: <1374138746-23279-1-git-send-email-fabio.porcedda@gmail.com> <1374138746-23279-3-git-send-email-fabio.porcedda@gmail.com> <521513E3.8080401@mind.be> Message-ID: <20130823093642.3ff0e2bb@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Arnout Vandecappelle, On Wed, 21 Aug 2013 21:24:19 +0200, Arnout Vandecappelle wrote: > On second observation, I don't really like this change, because it > makes the extract and patch parts asymmetrical with the others. I would > prefer one patch that changes it for all the targets. But then, the > behaviour does change, because rebuilding one package will also trigger a > rebuild of the packages that depend on it. Which may be a good thing, of > course... When I did some experiments on top-level parallel build some years ago, it is also one of the problem I had seen. Today, if you decide to rebuild "libfoo", it rebuilds libfoo only and that's it. If libfoo is used by something else, it's your responsibility to rebuild this something else. Of course, this is all possible because the chain of dependencies uses virtual targets and not stamp files. If we use stamp files directly for the dependencies between the build steps, then rebuilding a package will automatically rebuild all its reverse dependencies. I believe this will be very very annoying for people who just want to test a small change in a library, for example, and make the whole OVERRIDE_SRCDIR thing used for development quite useless. Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com