From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Please help with pkg infrastructure
Date: Tue, 04 Sep 2012 07:50:31 +0200 [thread overview]
Message-ID: <504596A7.7040408@mind.be> (raw)
In-Reply-To: <1346689042.29515.6.camel@sven>
On 09/03/12 18:17, Sven Neumann wrote:
> So what am I doing wrong here, because PKG_VERSION ends up being
> "undefined" instead of defaulting to the value of
> $BR2_PACKAGE_RAUMFELD_BRANCH ?
>
I don't see anything wrong with your definitions. Try running 'make -p'
and see which _BRANCH symbols are defined.
BTW, if _BRANCH turns out to be an empty string, make interprets that
the same way as undefined. So in that case, the _VERSION can be expected
to de 'undefined'.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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
prev parent reply other threads:[~2012-09-04 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 16:17 [Buildroot] Please help with pkg infrastructure Sven Neumann
2012-09-04 5:50 ` Arnout Vandecappelle [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=504596A7.7040408@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