From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Cc: bitbake-dev@lists.berlios.de
Subject: Syntax of ASSUME_PROVIDED
Date: Thu, 21 Oct 2010 00:42:15 +0200 [thread overview]
Message-ID: <4CBF7047.7040809@opendreambox.org> (raw)
Hi all,
I observed some unexpected behavior with BitBake 1.10.1.
After having added ASSUME_PROVIDED += "gconf" to my distro conf, bitbake
pixman didn't succeed anymore (a clean build after removing tmp). It
couldn't find pkgconfig macros used by configure. When I tried bitbake
pkgconfig-native, BitBake looped forever, as Khem already reported in an
earlier mail to bitbake-dev [1].
I noticed that gconf is part of pk-gconf-ig, so I suspected that there
was something going wrong matching the strings.
BitBake uses re_match_strings, which contains the following code:
for name in strings:
if (name==target or
re.search(name,target)!=None):
return True
return False
Looking at other occurences of ASSUME_PROVIDED, I noticed that everybody
seems to assume that the syntax for this variable is a space-separated
list of targets, and nobody uses regular expressions for it.
So, should I use something like "^gconf$" in my config? Or should
re_match_strings be modified instead?
Regards,
Andreas
[1] http://www.mail-archive.com/bitbake-dev@lists.berlios.de/msg00736.html
reply other threads:[~2010-10-20 22:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CBF7047.7040809@opendreambox.org \
--to=obi@opendreambox.org \
--cc=bitbake-dev@lists.berlios.de \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.