All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Adding support for DirectFB across the board
Date: Mon, 24 Sep 2007 13:08:00 +0200	[thread overview]
Message-ID: <46F79A90.6090709@student.utwente.nl> (raw)
In-Reply-To: <1190628401.6176.39.camel@localhost.localdomain>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Purdie schreef:
> On Sun, 2007-09-23 at 15:20 -0400, shanevolpe@gmail.com wrote:
>> I have been adding in support for directFB to as many packages as
>> possible, however one issue I have ran into several times is what do I
>> do when there are packages that can be compiled with X11 or directfb
>> support and then what do you do with packages that may depend on a
>> package compiled with directfb or X11.  Ok that was pretty confusing,
>> let me give an example.
>>
>> I have added cairo-directfb which compiles cairo with directfb instead
>> of X11.  Next I wanted to add (update) gtk+-directfb to use
>> cairo-directfb instead of cairo.  That part was easy I just changed
>> the DEPENDS cairo in gtk+-directfb to cairo-directfb..  The issue came
>> when I noticed that gtk+ also requires pango which requires cairo so
>> what do I do here, do I make a new pango called pango-directfb?  It
>> seems like the better thing would be set up a virtual/cairo and set it
>> to either cairo or cairo-directfb.  If I go that route how do I set it
>> up so it does not break everyone's build that does not have
>> virtual/cairo set, is there a way to default it to something like
>> cairo?
> 
> The thing you need to consider is that pango compiled with a standard
> cairo is a different package to pango compiled with cairo-directfb.
> 
> The virtual namespace is used to show things that are equivalent and
> pango is different to pango-directfb since I couldn't interchange them.
> 
> You therefore need to create a pango-directfb, ugly as that may be (.inc
> files can minimise the ugliness though).

Don't forget to add RCONFLICTS statements, since the resulting binary has the same name (IIRC)

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFG95qQMkyGM64RGpERAvWrAKCfPDULCnbztGCa/Op+4r6TFR4i3QCeIAoR
c6DOEu6KMroHJYKzzbeNZOI=
=BNa1
-----END PGP SIGNATURE-----



  reply	other threads:[~2007-09-24 11:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-23 19:20 Adding support for DirectFB across the board shanevolpe
2007-09-24 10:06 ` Richard Purdie
2007-09-24 11:08   ` Koen Kooi [this message]
2007-09-24 13:36     ` shanevolpe
2007-09-25 22:02       ` Mike (mwester)
2007-09-25 23:49         ` shanevolpe
2007-09-26  0:08         ` Paul Sokolovsky
2007-09-26  1:47           ` Mike (mwester)

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=46F79A90.6090709@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --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 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.