From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Refactoring Freescale's iMX software revision levels
Date: Fri, 03 May 2013 19:13:13 +0200 [thread overview]
Message-ID: <5183F029.1000907@mind.be> (raw)
In-Reply-To: <42565.217.149.209.147.1367582464.squirrel@webmail.internl.net>
On 03/05/13 14:01, H.Fijnvandraat at inter.nl.net wrote:
> Sorry,
>
> But I have to withdraw these patches.
>
> Due to the sequence in which the .mk files are included IMX_VERSION_LEVEL
> is defined when imx-lib.mk is processed, while it is already needed for
> firmware-imx (and gpu-viv-bin-mx6q if it would be introduced)
>
> Placing it in firmware-imx would do for now, but then no dependencies can
> be placed alphabetically before it later.
>
> It appears we need some other mechanism to rule them all.
Ah, yes stupid of me. Normally the order of assignments doesn't matter,
but the generic-target contains an 'ifndef $(2)_VERSION'.
So the only solution is to collect the imx packages in an imx
subdirectory, like qt5. I've told Henk earlier that we try to avoid
creating subdirectories in the package directory, but perhaps this is a
good reason to do it. What do the others think?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-05-03 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 8:27 [Buildroot] [PATCH 1/2] Refactoring Freescale's iMX software revision levels Henk Fijnvandraat
2013-05-03 8:27 ` [Buildroot] [PATCH 2/2] firmware-imx-version: bump to version 1.1.0 Henk Fijnvandraat
2013-05-03 12:01 ` [Buildroot] [PATCH 1/2] Refactoring Freescale's iMX software revision levels H.Fijnvandraat at inter.nl.net
2013-05-03 17:13 ` Arnout Vandecappelle [this message]
2013-05-05 19:41 ` Peter Korsgaard
2013-05-03 17:29 ` Thomas Petazzoni
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=5183F029.1000907@mind.be \
--to=arnout@mind.be \
--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