Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Xserver file generation
Date: Tue, 07 Jul 2009 13:59:47 +0200	[thread overview]
Message-ID: <4A5338B3.4010108@gmail.com> (raw)
In-Reply-To: <1246866823.16040.102.camel@lenovo.internal.reciva.com>

Phil Blundell ha scritto:
> On Mon, 2009-07-06 at 09:32 +0200, Marco Cavallini wrote:
>> At last my questions and doubts are the following:
>> 1. Is it correct to consider xserver-xcommon the recipe responsible for
>> creating such file?
>> 2. How would be created the Xserver file?
>> 3. WHich patches flow is involved into its creation?
>>
>>
>> The file I get on the target contains the following :
>> http://pastebin.com/m42ba5037
> 
> That file does look like the one from xserver-common.  (There's also a
> competing version of Xserver in xserver-kdrive-common; I don't think
> this is what you have, but "opkg search" would tell you for sure.)
> 
> I'm not quite sure I understand your questions 2 and 3.  Xserver is just
> copied from the source directory into the output package; it isn't
> really "created" inside OE.  As for the patches, I don't know offhand
> which ones are applied but again, there is nothing special about the
> Xserver file; OE will use the same rules as for everything else.
> 
> What's the actual problem that you're trying to solve here?

I need to add a row with my customized configuration


/marco



  reply	other threads:[~2009-07-07 12:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06  7:32 Xserver file generation Marco Cavallini
2009-07-06  7:53 ` Phil Blundell
2009-07-07 11:59   ` Marco Cavallini [this message]
2009-07-07 12:38     ` Florian Boor

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=4A5338B3.4010108@gmail.com \
    --to=koansoftware@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox