From: Murray.Jensen at csiro.au <Murray.Jensen@csiro.au>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] sinclude board specific make fragment
Date: Fri, 01 Jul 2005 00:19:04 +1000 [thread overview]
Message-ID: <9571.1120141144@huldra> (raw)
In-Reply-To: Your message of "Thu, 30 Jun 2005 15:35:41 +0200" <20050630133541.9A9E3353A0E@atlas.denx.de>
On Thu, 30 Jun 2005 15:35:41 +0200, Wolfgang Denk writes:
>> As I said in the description, this allows board specific make targets
>> such as "install", or other board specific targets that might need to
>> be included in the $(ALL) make variable.
>>
>> If make targets are placed in the board specific "config.mk", the first
>> such target becomes the default make target, instead of "all", which is
>> declared later in the main Makefile.
>
>This is something I don't like. "config.mk" is intended to hold
>configration information needd for the make, nothing else. Definitely
>no make targets or rules or things like that.
Precisely - that is what I was saying. You cannot include targets or rules
in the board specific "config.mk" file.
>Actually the board specific "config.mk" files might be romved one
>day.
Umm.. this would be very bad. Why would you want to do that?
>> make targets placed in the board specific Makefile can't be called from
>> the top level directory.
>
>Do you reallyneed your own private make targets?
I gave two examples - "install", and a target for an image of the "boot
page" for our MPC8560 board (which I want to be added to the $(ALL) list).
I have others, but they are more trivial.
>Then make sure that an appropriate note about the patch being
>copyrighted by you and available under GPL is included with your
>patch.
...
>If you cannot avoid the trailer, then make clear that it does not
>apply, please.
Fair enough. I will do that in future. Cheers!
Murray...
--
Murray Jensen, CSIRO Manufacturing & Infra. Tech. Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 9662 7853
Internet: Murray.Jensen at csiro.au
To the extent permitted by law, CSIRO does not represent, warrant and/or
guarantee that the integrity of this communication has been maintained or
that the communication is free of errors, virus, interception or interference.
The information contained in this e-mail may be confidential or privileged.
Any unauthorised use or disclosure is prohibited. If you have received this
e-mail in error, please delete it immediately and notify Murray Jensen on
+61 3 9662 7763. Thank you.
next prev parent reply other threads:[~2005-06-30 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 5:39 [U-Boot-Users] [PATCH] sinclude board specific make fragment Murray.Jensen at csiro.au
2005-06-30 10:17 ` Wolfgang Denk
2005-06-30 13:09 ` Murray.Jensen at csiro.au
2005-06-30 13:35 ` Wolfgang Denk
2005-06-30 14:19 ` Murray.Jensen at csiro.au [this message]
2005-06-30 15:11 ` Wolfgang Denk
2005-07-14 7:20 ` Murray.Jensen at csiro.au
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=9571.1120141144@huldra \
--to=murray.jensen@csiro.au \
--cc=u-boot@lists.denx.de \
/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.