From: Rob Kramer <robk@starhub.net.sg>
To: openembedded-devel@openembedded.org
Subject: Trouble creating virtual library provider package [REPOST]
Date: Wed, 28 Jan 2009 11:00:11 +0800 [thread overview]
Message-ID: <glohnr$osq$1@ger.gmane.org> (raw)
[Aaaanyone?]
Hi all,
How would I go about if I'd like to have two packages that provide the same
thing? For example, I have package freetype, and freetype-led (which has a
device-specific hack). Or ffmpeg and ffmpeg-minimal (which builds the
smallest possible libavcodec/format). The right package is selected by the
image recipe, via a task.
Is the normal way to do this to make a virtual/freetype and
PREFERRED_PROVIDER? I tried to do this, but still have trouble with double
providers etc. It gets tricky if package-name munging is involved, where
the final package is called libfreetype6_2.3.7-r4_i586.ipk, and not
freetype_2.3.7-r4_i586.ipk (and freetype-led_2.3.7-r4_i586.ipk).
If this is the right way, can someone point to a good (simple) example of a
virtual library provider?
Cheers!
Rob
reply other threads:[~2009-01-28 3:07 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='glohnr$osq$1@ger.gmane.org' \
--to=robk@starhub.net.sg \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox