All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Gstreamer and rpath
Date: Sun, 05 Aug 2007 12:32:43 +0100	[thread overview]
Message-ID: <1186313563.5962.36.camel@localhost.localdomain> (raw)
In-Reply-To: <1186132901.5972.314.camel@hammer.suse.cz>

On Fri, 2007-08-03 at 11:21 +0200, Stanislav Brabec wrote:
> Richard Purdie wrote:
> 
> > I'm actually semi against forcing staging to look like an image. The
> > fact gcc requires this for its sysroot option is a sign that they
> > haven't got this right yet.
> > 
> > With packaged staging we need to decide which way we go, separate
> > staging packages or use the same ones as we use for images.
> > 
> > My personal gut feeling is that separate ones will work better. They
> > also mean we can handle the extra staging files like pkgmaps and perhaps
> > handle multi machine easier.
> 
> Well, the point of gcc --sysroot is a simplification of cross
> compilation for those using complete sysroot environment.

Yes, I understand that and I appreciate it does solve a certain mount of
the problem! I just think it could be better and that it isn't a "solves
everything" solution for OE.

> But maybe there is possible to invent better method than the sysroot
> design is.
> 
> A random idea:
> 
> Define TARGET_ROOT_MAP, which may use similar syntax like overlay
> filesystems have. It will allow to construct sysroot by these
> filesystems on fly as well, e. g. for use with emulators.

That would be a much nicer solution. Staging could them have its own
mapping and it should solve most of the problems we see. Have you any
idea how difficult that would be to implement?

Regards,

Richard





  reply	other threads:[~2007-08-05 11:35 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02  6:10 Gstreamer and rpath Koen Kooi
2007-08-02 10:50 ` Michael Krelin
2007-08-02 11:23   ` Stanislav Brabec
2007-08-02 11:59     ` Michael Krelin
2007-08-02 12:38       ` Stanislav Brabec
2007-08-02 12:40         ` Philip Balister
2007-08-02 12:58           ` Michael Krelin
2007-08-02 13:27           ` Stanislav Brabec
2007-08-02 13:47             ` Koen Kooi
2007-08-02 14:15               ` Stanislav Brabec
2007-08-02 14:20                 ` Koen Kooi
2007-08-02 14:47                   ` Stanislav Brabec
2007-08-02 15:26                     ` Michael Krelin
2007-08-02 15:46                       ` Koen Kooi
2007-08-02 15:52                         ` Michael Krelin
2007-08-02 17:00                           ` Koen Kooi
2007-08-02 17:08                             ` Michael Krelin
2007-08-02 22:16                             ` Richard Purdie
2007-08-02 22:43                               ` Michael Krelin
2007-08-03  8:04                                 ` Richard Purdie
2007-08-03  9:34                                   ` Michael Krelin
2007-08-05 11:29                                     ` Richard Purdie
2007-08-05 16:27                                       ` Michael Krelin
2007-08-05 20:21                                         ` Stanislav Brabec
2007-08-03  9:21                               ` Stanislav Brabec
2007-08-05 11:32                                 ` Richard Purdie [this message]
2007-08-05 20:16                                   ` Stanislav Brabec
2007-08-05 20:27                                   ` Michael Krelin
2007-08-06 10:15                                     ` Stanislav Brabec
2007-08-06 16:28                                       ` Michael Krelin
2007-08-06 17:02                                         ` Stanislav Brabec
2007-08-05  5:55               ` Dr. Michael Lauer
2007-08-05  6:47                 ` Mike (mwester)
2007-08-05  7:17                   ` Dr. Michael Lauer
2007-08-02 12:56         ` Michael Krelin
2007-08-02 13:06           ` Koen Kooi

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=1186313563.5962.36.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --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.