From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Makefile.autotools.in does not work wellwith projects
Date: Wed, 30 Jul 2008 12:19:52 +0200 [thread overview]
Message-ID: <20080730101952.GB27907@mx.loc> (raw)
In-Reply-To: <1217235161.7955.12.camel@localhost>
On Mon, Jul 28, 2008 at 10:52:41AM +0200, Hans-Christian Egtvedt wrote:
>On Mon, 2008-07-28 at 18:50 +1000, Hamish Moffatt wrote:
>> On Mon, Jul 28, 2008 at 10:42:37AM +0200, Hans-Christian Egtvedt wrote:
>> > On Sun, 2008-07-27 at 11:33 +1000, Hamish Moffatt wrote:
>
><snipp>
>
>> > And two minutes later I have a RFC for this solution, see attached
>> > patch.
>> [..]
>> > # Install to target dir
>> > -$(BUILD_DIR)/%/.stamp_target_installed:
>> > +$(TARGET_DIR)/%/$($($(PKG)_NAME)_TARGET_INSTALLED_TOUCH_FILE):
>> > $(call MESSAGE,"Installing to target")
>> > - $($(PKG)_MAKE_ENV) $(MAKE) $($(PKG)_INSTALL_TARGET_OPT) -C $(@D)/$($(PKG)_SUBDIR)
>> > + $($(PKG)_MAKE_ENV) $(MAKE) $($(PKG)_INSTALL_TARGET_OPT) -C $($(PKG)_DIR)/$($(PKG)_SUBDIR)
>> [..]
>> > # define sub-target stamps
>> > -$(2)_TARGET_INSTALL_TARGET = $$($(2)_DIR)/.stamp_target_installed
>> > +$(2)_TARGET_INSTALL_TARGET = $$(TARGET_DIR)/$$($(2)_TARGET_INSTALLED_TOUCH_FILE)
>>
>> Will every package that uses Makefile.autotools.in need to be modified
>> to define the target installed file? If so, would you like to prepare a
>> large patch? :)
>
>Not really, since I do not have knowledge about each package and what
>they will need to depend on installed on target.
>
>> Alternatively, perhaps $(2)_TARGET_INSTALL_TARGET could
>> be fall back to the old definition if the new variable is not supplied,
>> using some ifeq logic.
>>
>
>Yes, there should be a fallback when the variable is not supplied. The
>Makefile should print a warning message as well, demanding an update ;)
>
>I'll see what I can figure out.
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).
next prev parent reply other threads:[~2008-07-30 10:19 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 [this message]
2008-08-06 6:31 ` Hans-Christian Egtvedt
2008-08-06 8:54 ` Bernhard Fischer
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=20080730101952.GB27907@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