Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] Added linux drivers backports project
Date: Mon, 20 Apr 2015 22:42:28 +0200	[thread overview]
Message-ID: <553564B4.2060303@mind.be> (raw)
In-Reply-To: <20150419190321.19200e70@free-electrons.com>

On 19/04/15 19:03, Thomas Petazzoni wrote:
> Dear Yann E. MORIN,
> 
> On Sun, 19 Apr 2015 18:28:39 +0200, Yann E. MORIN wrote:
> 
>> Well, I would not be very happy with that, since that would make the
>> following use-case a real pain:
>>
>>     $ make foo_defconfig
>>     $ make linux-menuconfig
>>
>> Currently, all it needs is the linux kernel to be extracted and patched,
>> and none of its depedencies to be built. Otherwise, it would require the
>> toolchain to be built, plus a sh.tload of other stuff (lzo, for one, and
>> all its own dependencies).
> 
> We could remove the mandatory host-lzo dependency from the linux
> package, by adding an option for that. Remember the recent patches also
> adding host-xz to the dependencies of linux, which I rejected?
> 
> This would leave host-kmod as the only dependency of the linux package
> I believe. But well host-kmod as AUTORECONF = YES, so it pulls a whole
> bunch of crap.

 As mentioned before, it pulls in the toolchain as well. That's a lot worse than
host-lzo and host-xz - even extracting an external toolchain takes longer than
host-xz (at least for me).


 However, we can add the dependency specifically for linux-backports. There is
something to be said for the reasoning that usually/sometimes you don't need the
dependencies to be present, so doing it per package sounds OK.

 So in this case, adding

$(LINUX_BACKPORTS_KCONFIG_FILE): linux

to linux-backports.mk should be sufficient.


 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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2015-04-20 20:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 23:01 [Buildroot] [PATCH v4 1/1] Added linux drivers backports project Petr Vorel
2015-04-19  9:03 ` Thomas Petazzoni
2015-04-19 13:15   ` Yann E. MORIN
2015-04-19 16:20   ` Arnout Vandecappelle
2015-04-19 16:28     ` Yann E. MORIN
2015-04-19 17:03       ` Thomas Petazzoni
2015-04-19 21:19         ` Petr Vorel
2015-04-19 21:28           ` Yann E. MORIN
2015-04-20 20:42         ` Arnout Vandecappelle [this message]
2015-04-20 20:56           ` Thomas Petazzoni
2015-04-20 21:08             ` Arnout Vandecappelle
2015-04-20 21:00           ` Yann E. MORIN

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=553564B4.2060303@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox