Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Add (Freescale) elftosb host package
Date: Wed, 14 Mar 2012 12:11:21 +0100	[thread overview]
Message-ID: <4F607CD9.2080300@lucaceresoli.net> (raw)
In-Reply-To: <20120314104146.0e75b488@skate>

Thomas Petazzoni wrote:
> Hello,
>
> Le Wed, 14 Mar 2012 01:05:44 +0100,
> Arnout Vandecappelle<arnout@mind.be>  a ?crit :
>
>> On Tuesday 13 March 2012 13:52:10 Eric Jarrige wrote:
>>> +define HOST_ELFTOSB_CLEAN_CMDS
>>> +       rm -rf $(@D)/bld/linux
>>> +       rm -f $(HOST_DIR)/usr/bin/elftosb
>>> +       rm -f $(HOST_DIR)/usr/bin/keygen
>>> +       rm -f $(HOST_DIR)/usr/bin/sbtool
>>> +endef
>>   These look like UNINSTALL commands, not CLEAN commands.
> Ah right. Actually the first line should be part of CLEAN commands, and
> the three last lines should be part of the UNINSTALL commands.
>
> Are they people who actually care about those CLEAN and UNINSTALL
> commands? Is it worth keeping support for them?

IIRC these targets cannot in general work correctly with the Buildroot
structure, and making them work would require a massive change, with a
big increase in complexity.

Moreover, many packages do not implement the CLEAN and UNINSTALL targets:

$ git grep -l GENTARGETS package/|grep -E '^package/[a-z]'|wc -l
111
$ git grep -l GENTARGETS package/|grep -E '^package/[a-z]'| \
     xargs grep -l '_CLEAN_CMDS'|wc -l
51
$ git grep -l GENTARGETS package/|grep -E '^package/[a-z]'| \
     xargs grep -l '_UNINSTALL_.*_CMDS'|wc -l
73

meaning that probably they are not so interesting to everybody out there.

As for me, I have never been relying on them. I prefer to distclean and
rebuild when necessary. It's reliable, and not that painful with a
reasonably recent build machine and ccache enabled.

So, my vote for dropping them.
(Or should there be a specific thread for this topic?)

Luca

  reply	other threads:[~2012-03-14 11:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 12:52 [Buildroot] [PATCH 0/2] add u-boot.sb file format and elftosb tools Eric Jarrige
2012-03-13 12:52 ` [Buildroot] [PATCH 1/2] Add (Freescale) elftosb host package Eric Jarrige
2012-03-13 15:10   ` Thomas Petazzoni
2012-03-14  0:05   ` Arnout Vandecappelle
2012-03-14  9:41     ` Thomas Petazzoni
2012-03-14 11:11       ` Luca Ceresoli [this message]
2012-03-14 11:57         ` Thomas Petazzoni
2012-03-15 21:06         ` [Buildroot] Remove clean and uninstall targets [was: Re: [PATCH 1/2] Add (Freescale) elftosb host package] Arnout Vandecappelle
2012-03-15 21:28           ` Thomas Petazzoni
2012-03-15 21:32             ` Arnout Vandecappelle
2012-03-13 12:52 ` [Buildroot] [PATCH 2/2] u-boot: add support for u-boot.sb file format Eric Jarrige
2012-03-13 14:17   ` Thomas Petazzoni
2012-03-13 14:52     ` Eric Jarrige
2012-03-13 15:06       ` Thomas Petazzoni
2012-03-13 15:11   ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2012-07-18 16:02 [Buildroot] [PATCH 1/2] Add (Freescale) elftosb host package Maxime Ripard
2012-07-20 22:37 ` 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=4F607CD9.2080300@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --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