Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Buildroot cleanup, v2
Date: Wed, 23 Sep 2009 01:13:24 +0200	[thread overview]
Message-ID: <20090923011324.20577fe7@surf> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190901D422D6@mi8nycmail19.Mi8.com>

Le Tue, 22 Sep 2009 18:56:32 -0400,
"H Hartley Sweeten" <hartleys@visionengravers.com> a ?crit :

> One thing I did notice.
> 
> You default BR2_DL_DIR to $(BASE_DIR)/dl a better default might be
> $(TOPDIR)/dl.  This would make the default work for multiple
> make O=<directory> without having to create the <directory>/dl symlink
> or export BUILDROOT_DL_DIR.

True. It always bothered me as well. Care to prepare a patch and submit
it ?

> > That's definitely on my TODO-list. But don't hesitate to step-up
> > with a patch, since I'm very busy these days and don't know when
> > I'll be able to work on this again (next week ?).
> 
> I'll just wait for you to reach it on your TODO-list ;-)

Ooh, come on :-)

> Having a common package removal would be great!  Removing a single
> package from the filesystem can be a real pain...

It is basically unsupported these days. Some packages work more or
less, but on overall it just doesn't work.

> zlib.mk isn't even the worse one.  That one at least looks like it
> could be converted to the a Makefile.autotools.in target.  Some of the
> older *.mk files are a real mess...

Yes, they are. They are part of the work, but it will take quite some
time to implement the infrastructure and then convert the packages.

Cheers,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2009-09-22 23:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 21:07 [Buildroot] [pull request] Buildroot cleanup, v2 Thomas Petazzoni
2009-09-16 21:07 ` [Buildroot] [PATCH 1/6] Remove the "project" feature Thomas Petazzoni
2009-09-17 16:17   ` Bernhard Reutner-Fischer
2009-09-17 17:30     ` Thomas Petazzoni
2009-09-19 15:26     ` Peter Korsgaard
2009-09-19 15:15   ` Peter Korsgaard
2009-09-16 21:07 ` [Buildroot] [PATCH 2/6] Remove the BOARD/LOCAL feature Thomas Petazzoni
2009-09-16 22:00   ` Thiago A. Corrêa
2009-09-16 22:08     ` Thomas Petazzoni
2009-09-16 22:21       ` Thiago A. Corrêa
2009-09-17  5:43         ` Thomas Petazzoni
2009-09-17 12:02           ` Peter Korsgaard
2009-09-16 21:07 ` [Buildroot] [PATCH 3/6] By default, put the output in an output/ directory Thomas Petazzoni
2009-09-16 21:07 ` [Buildroot] [PATCH 4/6] Remove BR2_TOPDIR_PREFIX and BR2_TOPDIR_SUFFIX Thomas Petazzoni
2009-09-16 21:07 ` [Buildroot] [PATCH 5/6] Rename the output directories Thomas Petazzoni
2009-09-16 21:07 ` [Buildroot] [PATCH 6/6] documentation: update after major changes Thomas Petazzoni
2009-09-19 15:27 ` [Buildroot] [pull request] Buildroot cleanup, v2 Peter Korsgaard
2009-09-20  9:08   ` Thomas Petazzoni
2009-09-21  2:37     ` Steve Calfee
2009-09-22 22:16 ` H Hartley Sweeten
2009-09-22 22:38   ` Thomas Petazzoni
2009-09-22 22:56     ` H Hartley Sweeten
2009-09-22 23:13       ` Thomas Petazzoni [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=20090923011324.20577fe7@surf \
    --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