From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fs/iso9660: add dependencies for make source
Date: Sat, 18 Oct 2014 18:47:17 +0200 [thread overview]
Message-ID: <20141018184717.229346e1@free-electrons.com> (raw)
In-Reply-To: <CABbD_XBSjcCmHwiVAwA7Ac+H_tFuv_DP9Jp8mfd5KfbuV21pYw@mail.gmail.com>
Dear K?roly Kasza,
On Sat, 18 Oct 2014 16:17:46 +0200, K?roly Kasza wrote:
> > You should use $(ROOTFS_ISO9660_DEPENDENCIES) here.
> >
> Why? Non of the other rootfs target makefiles use that (fs/*/*.mk).
All the other rootfs target makefiles use <foo>_DEPENDENCIES. Except
that it's taken into account directly by the common filesystem logic in
fs/common.mk. However, iso9660 is special, and therefore we handle the
dependencies manually. But still, there's no need to repeat them twice.
So, in your patch, change:
ROOTFS_ISO9660_DEPENDENCIES = host-cdrkit host-fakeroot linux rootfs-cpio grub
$(BINARIES_DIR)/rootfs.iso9660: host-cdrkit host-fakeroot linux rootfs-cpio grub
To:
ROOTFS_ISO9660_DEPENDENCIES = host-cdrkit host-fakeroot linux rootfs-cpio grub
$(BINARIES_DIR)/rootfs.iso9660: $(ROOTFS_ISO9660_DEPENDENCIES)
> Technically, the dependencies variable is already at the top, before the
> first make target.
Agreed.
> Regarding the order: I don't really think that matters.
Well, it's indeed just a subjective thing, like most coding style
things. Still, when a core Buildroot contributor such as Arnout
suggests coding style changes, it's usually a good idea to follow suit
to get the patch merged quickly :)
That being said, I agree that we don't enforce any particular order for
the dependencies in the other packages.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-18 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 21:16 [Buildroot] [PATCH] fs/iso9660: add dependencies for make source Karoly Kasza
2014-10-18 10:31 ` Maxime Hadjinlian
2014-10-18 13:31 ` Arnout Vandecappelle
2014-10-18 14:17 ` Károly Kasza
2014-10-18 16:47 ` Thomas Petazzoni [this message]
2014-10-18 17:13 ` Károly Kasza
2014-10-18 17:23 ` 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=20141018184717.229346e1@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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