From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Makefile.autotools.in does not work wellwith projects
Date: Wed, 6 Aug 2008 10:54:17 +0200 [thread overview]
Message-ID: <20080806085417.GC7191@mx.loc> (raw)
In-Reply-To: <1218004314.29697.10.camel@localhost>
On Wed, Aug 06, 2008 at 08:31:54AM +0200, Hans-Christian Egtvedt wrote:
>> Let me suggest to rename that variable to $(2)_TARGET_FILES
>> and do
>> $(2)_TARGET_INSTALL_TARGET = $(firstword $($(2)_TARGET_FILES))
>>
>> foo_tmp=$(firstword $($(2)_TARGET_FILES))
>> or somthing like $(if $(foo_tmp),$(foo_tmp),$($(2).old_stamp_file))
>>
>> Reasoning:
>> You really want to only have a few files in $(TARGET_DIR) as opposed to
>> $(STAGING_DIR). Those $(2)_TARGET_FILES should ideally be the only files
>> installed into the final image (think of a gazillion superfluous termcap
>> entries or other unneeded files).
>
>Then you need to overwrite the install rule anyway, my patch was
>intended to fix the general installation of applications.
>
>You seem to want a rule which will install only the binaries needed?
Yes. Ideally only the needed files should end on the target.
>
>Some applications and libraries are actually installed quite minimal and
>correct by using make DESTDIR install :)
true, but for those who don't, such target files should be used.
next prev parent reply other threads:[~2008-08-06 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 14:43 [Buildroot] Makefile.autotools.in does not work well with projects Hans-Christian Egtvedt
2008-07-25 0:12 ` Hamish Moffatt
2008-07-26 6:53 ` [Buildroot] Makefile.autotools.in does not work wellwith projects Ulf Samuelsson
2008-07-27 1:33 ` Hamish Moffatt
2008-07-28 8:35 ` Hans-Christian Egtvedt
2008-07-28 8:42 ` Hans-Christian Egtvedt
2008-07-28 8:50 ` Hamish Moffatt
2008-07-28 8:52 ` Hans-Christian Egtvedt
2008-07-30 10:19 ` Bernhard Fischer
2008-08-06 6:31 ` Hans-Christian Egtvedt
2008-08-06 8:54 ` Bernhard Fischer [this message]
2008-08-06 9:04 ` Hans-Christian Egtvedt
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=20080806085417.GC7191@mx.loc \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox