From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] fs: Add common rootfs dependencies to PACKAGES
Date: Mon, 12 Nov 2018 18:44:58 +0100 [thread overview]
Message-ID: <20181112174458.GF10271@scaer> (raw)
In-Reply-To: <aedf0524-07eb-5e4d-8309-a97eea515058@mind.be>
Arnout, All,
On 2018-11-12 18:32 +0100, Arnout Vandecappelle spake thusly:
> On 12/11/2018 17:46, Yann E. MORIN wrote:
> > Andreas, All,
> >
> > On 2018-11-12 13:53 +0100, Andreas Naumann spake thusly:
> >> Am 09.11.18 um 23:11 schrieb Arnout Vandecappelle:
> >>> On 08/11/2018 14:04, Andreas Naumann wrote:
> >> ...
> >>>> +PACKAGES += $(ROOTFS_COMMON_DEPENDENCIES)
> >>>
> >>> I don't really like this, for the simple reason that it will enable the
> >>> dependencies even if they are not needed because we're not building any rootfs.
> >>
> >> good point, I dont like that either. I'd propose to change/move the patch
> >> into something like
> >> PACKAGES += $$(filter-out $$(PACKAGES),$$(ROOTFS_COMMON_DEPENDENCIES))
> >> inside the rootfs-conditional clause at the bottom of fs/common.mk. Actually
> >> I'm not sure the filter-out stuff is really needed since duplicate targets
> >> may accumulate in PACKAGES anyway.
> >
> > Yes, that would be OK to moce them to the per-filesystem macro, but we
> > already have:
> >
> > ROOTFS_$(2)_DEPENDENCIES += rootfs-common
> >
> > So maybe just do:
> >
> > ROOTFS_$(2)_DEPENDENCIES += \
> > rootfs-common \
> > $$(ROOTFS_COMMON_DEPENDENCIES)
>
> It's about adding to PACKAGES, not _DEPENDENCIES.
Yeah, but _DEPENDENCIES are added to PACKAGES.
And I think with the series I just posted [0]. there is no reason to
have dependencies in the common step anymore, since there are now only
calls to 'cat' and 'printf' in there. So it makes sense to make those
dependencies, dependencies of each individual filesystem now.
Regards,
Yann E. MORIN.
> >
> > Regards,
> > Yann E. MORIN.
> >
> >>>
> >>> It's a small thing though, and working around it is a lot more complicated (you
> >>> could e.g. select a new Config.in symbol that is selected by all the rootfses).
> >>> And when we ever get the Config.in.host for all host packages, it's solved
> >>> already. So
> >>>
> >>> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> >>>
> >>> Regards,
> >>> Arnout
> >>>
> >>>> $(ROOTFS_COMMON_TAR): ROOTFS=COMMON
> >>>> $(ROOTFS_COMMON_TAR): FAKEROOT_SCRIPT=$(FS_DIR)/fakeroot.fs
> >>>>
> >>> _______________________________________________
> >>> buildroot mailing list
> >>> buildroot at busybox.net
> >>> http://lists.busybox.net/mailman/listinfo/buildroot
> >>>
> >> _______________________________________________
> >> buildroot mailing list
> >> buildroot at busybox.net
> >> http://lists.busybox.net/mailman/listinfo/buildroot
> >
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-11-12 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 13:04 [Buildroot] [PATCH 0/2] Preparation for per-package host/target Andreas Naumann
2018-11-08 13:04 ` [Buildroot] [PATCH 1/2] fs: Add common rootfs dependencies to PACKAGES Andreas Naumann
2018-11-09 22:11 ` Arnout Vandecappelle
2018-11-12 12:53 ` Andreas Naumann
2018-11-12 16:46 ` Yann E. MORIN
2018-11-12 17:32 ` Arnout Vandecappelle
2018-11-12 17:44 ` Yann E. MORIN [this message]
2018-11-13 14:51 ` Thomas Petazzoni
2018-11-13 15:30 ` Andreas Naumann
2018-11-08 13:04 ` [Buildroot] [PATCH 2/2] linux: Make dtc install step more reliable Andreas Naumann
2018-11-09 22:14 ` Arnout Vandecappelle
2018-11-12 12:55 ` Andreas Naumann
2018-11-12 13:59 ` Arnout Vandecappelle
2018-11-08 13:23 ` [Buildroot] [PATCH 0/2] Preparation for per-package host/target Thomas Petazzoni
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=20181112174458.GF10271@scaer \
--to=yann.morin.1998@free.fr \
--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