All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] improved deps [was Re: svn commit: trunk/buildroot: package/config]
Date: Sun, 8 Jul 2007 14:59:52 +0200	[thread overview]
Message-ID: <20070708125948.GK4096@aon.at> (raw)
In-Reply-To: <20070708001049.GC4096@aon.at>

On Sun, Jul 08, 2007 at 02:10:49AM +0200, Bernhard Fischer wrote:
>On Sat, Jul 07, 2007 at 05:00:18PM -0700, aldot at uclibc.org wrote:
>>Author: aldot
>>Date: 2007-07-07 17:00:17 -0700 (Sat, 07 Jul 2007)
>>New Revision: 19025
>>
>>Log:
>>- silence a cosmetic warning (closes several issues in mantis).
>>  This also provides a nice up-to-date filestamp if something got reconfigured (e.g. c++ support got toggled) that can be used in the future to depend accordingly.
>
>e.g.:

I have applied this as an example for gcc as r19034.
A more generic way would be in order, e.g. emit a file that can be
pulled in that looks like (pseudo pathes):

/obj/buildroot/toolchain_build_i386/gcc-4.2.0-final/.configured: \
	/obj/buildroot/build_i386/include/config/br2/install/fortran.h

/obj/buildroot/toolchain_build_i386/uClibc/.configured: \
	/obj/buildroot/build_i386/include/config/br2/uclibc/feature1.h \
	/obj/buildroot/build_i386/include/config/br2/uclibc/feature2.h \
	/obj/buildroot/build_i386/include/config/br2/uclibc/feature3.h

I leave the impl of the above to the curious reader :P

      reply	other threads:[~2007-07-08 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08  0:00 [Buildroot] svn commit: trunk/buildroot: package/config aldot at uclibc.org
2007-07-08  0:10 ` [Buildroot] improved deps [was Re: svn commit: trunk/buildroot: package/config] Bernhard Fischer
2007-07-08 12:59   ` Bernhard Fischer [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=20070708125948.GK4096@aon.at \
    --to=rep.dot.nop@gmail.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 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.