Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master] Makefile: cleanup *clean targets
Date: Fri, 20 Nov 2009 15:22:26 +0100	[thread overview]
Message-ID: <87r5rtgtst.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <200911200809.17924.minimod@morethan.org> (Michael S. Zick's message of "Fri\, 20 Nov 2009 08\:08\:57 -0600")

>>>>> "Michael" == Michael S Zick <minimod@morethan.org> writes:

 >> As discussed on the list, fixup the *clean targets, so we now have:
 >> 

 Michael> a newbee here, I missed that discussion -

The original thread is here:

http://lists.busybox.net/pipermail/buildroot/2009-October/029707.html

 >> -dirclean: $(TARGETS_DIRCLEAN)
 >> -	rm -rf $(STAGING_DIR) $(TARGET_DIR) $(IMAGE) $(BUILD_DIR)/.root $(STAMP_DIR)
 >> -

 Michael> If "dirclean" is now dead. . .
 Michael> Shouldn't the form:
 Michael> make PackageName-dirclean also die?

Well, perhaps long term it should - But that would involve touching all
packages, not something I would want to do this close to the release. I
plan on getting 2009.11-rc1 out this weekend.

 Michael> What is catching my eye is section of the makefile about:
 Michael> TARGETS_CLEAN:
 Michael> TARGETS_SOURCE:
 Michael> TARGETS_DIRCLEAN:
 Michael> TARGETS_ALL:

 Michael> Please keep in mind I missed out on the discussion and
 Michael> also have very limited knowledge of this build system.

Those are still used to mark them phony and ensuring all enabled
packages gets built.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2009-11-20 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 13:34 [Buildroot] [git commit master] Makefile: cleanup *clean targets Peter Korsgaard
2009-11-20 14:08 ` Michael S. Zick
2009-11-20 14:17   ` Michael S. Zick
2009-11-20 14:22   ` Peter Korsgaard [this message]

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=87r5rtgtst.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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