From: Eric Nelson <eric.nelson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V4 2/2] i.MX: Update versions to match latest Freescale release
Date: Thu, 13 Feb 2014 17:31:25 -0700 [thread overview]
Message-ID: <52FD63DD.2000208@boundarydevices.com> (raw)
In-Reply-To: <20140213225218.GC3259@free.fr>
Hi Yann,
On 02/13/2014 03:52 PM, Yann E. MORIN wrote:
> Eric, All,
>
> On 2014-02-12 19:00 -0700, Eric Nelson spake thusly:
>> On 02/12/2014 04:41 PM, Yann E. MORIN wrote:
>>> However, The cleanest in my opinion would be to extract the archive into
>>> a subdir of $(@D), like:
>>>
>>> # Blurb about auto-extract in a properly-named dir
>>> define IMX_LIB_EXTRACT_CMDS
>>> cd $(@D); \
>>> sh $(DL_DIR)/$(IMX_LIB_SOURCE) --force --auto-accept
>>
>> And then move them?
>> i.e.
>> mv $(@D)/packagemname/* $(@D)/
>> rm -r $(@D)/packagemname/
>
> No, we would not need to move it. We'd just use it as-is in the
> following commands, like I showed below:
>
>>> define IMX_LIB_BUILD_CMDS
>>> $(IMX_LIB_MAKE_ENV) $(MAKE1) -C $(@D)/imx-lib-$(FREESCALE_IMX_VERSION)
>>> endef
>
>> It seems like over-kill to keep the directory around.
>
> Well, maybe not overkill, but not-so-clean, yes.
>
>> And what about the patch step references?
>
> Boom! :-)
>
I'm still not quite grokking this, but I'll take a stab.
I just sent a patch set with things done the other way.
Please just Nak patch 3 of 3.
I left it in because I already had the notes in place
and it might be useful for comparison.
Regards,
Eric
next prev parent reply other threads:[~2014-02-14 0:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 3:05 [Buildroot] [PATCH V4 0/2] i.MX updates Eric Nelson
2013-10-09 3:05 ` [Buildroot] [PATCH V4 1/2] i.MX: Use FREESCALE_IMX_SITE for Freescale packages Eric Nelson
2014-02-12 18:10 ` Yann E. MORIN
2014-02-12 19:01 ` Eric Nelson
2013-10-09 3:05 ` [Buildroot] [PATCH V4 2/2] i.MX: Update versions to match latest Freescale release Eric Nelson
2014-02-12 18:23 ` Yann E. MORIN
2014-02-12 18:27 ` Yann E. MORIN
2014-02-12 19:03 ` Yann E. MORIN
2014-02-12 19:10 ` Eric Nelson
2014-02-12 20:20 ` Eric Nelson
2014-02-12 21:58 ` Arnout Vandecappelle
2014-02-12 22:15 ` Mike Zick
2014-02-12 22:55 ` Eric Nelson
2014-02-12 23:53 ` Eric Nelson
2014-02-12 23:59 ` Yann E. MORIN
2014-02-12 22:20 ` Peter Korsgaard
2014-02-12 22:45 ` Eric Nelson
2014-02-12 23:41 ` Yann E. MORIN
2014-02-13 2:00 ` Eric Nelson
2014-02-13 22:52 ` Yann E. MORIN
2014-02-13 22:54 ` Thomas Petazzoni
2014-02-14 0:34 ` Eric Nelson
2014-02-14 0:31 ` Eric Nelson [this message]
2014-02-12 23:25 ` Eric Nelson
2014-02-12 23:46 ` Yann E. MORIN
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=52FD63DD.2000208@boundarydevices.com \
--to=eric.nelson@boundarydevices.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