All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFCv1 0/4] Per-package SDK and target directories
Date: Tue, 7 Nov 2017 21:54:19 +0100	[thread overview]
Message-ID: <32d492f8-4c57-16c9-1602-61117f556e3a@mind.be> (raw)
In-Reply-To: <20171107205558.315ce04c@windsurf>



On 07-11-17 20:55, Thomas Petazzoni wrote:
> Hello,
> 
> On Tue, 7 Nov 2017 18:55:20 +0100, Arnout Vandecappelle wrote:
> 
>>> in package/pkg-generic.mk. But of course, we need to exclude the
>>> host-ccache package from this, otherwise we would have a circular
>>> dependency. Do you want to try something like this?  
>>
>>  Ha, I didn't understand the original problem but now I see. The issue is that
>> ccache is part of DEPENDENCIES_HOST_PREREQ, and DEPENDENCIES_HOST_PREREQ is
>> *not* added to each package's DEPENDENCIES,
> 
> Exactly.
> 
>> instead it is added to the
>> core-dependencies target and each package depends on that. It's an easy way to
>> avoid circular dependencies, I guess.
>>
>>  So I think the proper solution would be to add DEPENDENCIES_HOST_PREREQ to the
>> dependencies of all packages except themselves, similar to how it's done for
>> toolchain.
> 
> Isn't this DEPENDENCIES_HOST_PREREQ thing a bit crappy in the first
> place?

 Nobody claimed it wasn't :-) It's a relic from 2007...

> Why isn't host-ccache simply added as a dependency of all
> packages, except itself?
> 
> Another example is that today, host-lzip is always built at the
> beginning of build, even if you're not building any package that needs
> the lzip "decompressor".
> 
> So perhaps this calls for a little bit of rework in this area, no?

 Yep. For cmake it is done the right way. The same could be done for the other
dependencies. And it may be useful to extend the mechanism to other system
packages. E.g. m4 is not really sensitive to version changes.

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2017-11-07 20:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5DBA847110A28B46BBA17BE675F0C9B2181A8D38@cnshjmbx01>
2017-11-07 17:13 ` [Buildroot] [RFCv1 0/4] Per-package SDK and target directories Thomas Petazzoni
2017-11-07 17:55   ` Arnout Vandecappelle
2017-11-07 19:55     ` Thomas Petazzoni
2017-11-07 20:54       ` Arnout Vandecappelle [this message]
2017-11-09  5:02     ` Chu, Zhuliang
2017-11-11 10:20       ` Arnout Vandecappelle
2017-11-09  4:32   ` Chu, Zhuliang
2017-11-11 10:37     ` Arnout Vandecappelle
2017-11-15  8:59       ` Chu, Zhuliang
2017-11-08 16:55 ` Thomas Petazzoni
2017-11-09  4:44   ` Chu, Zhuliang
2017-11-08 17:29 ` Yann E. MORIN
2017-11-08 18:35   ` Thomas De Schampheleire
2017-11-09  8:19   ` Chu, Zhuliang
2017-11-03 16:06 Thomas Petazzoni
2017-11-07 23:21 ` Arnout Vandecappelle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32d492f8-4c57-16c9-1602-61117f556e3a@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.