From: Thomas Senyk <thomas.senyk@pelagicore.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH v2 1/5] gpu-viv-bin-mx6q: Rework package for a single backend use
Date: Fri, 12 Apr 2013 17:09:09 +0200 [thread overview]
Message-ID: <2606466.EDyCjuJWjb@rudolf> (raw)
In-Reply-To: <CAP9ODKpohXNuNFOktFuT2U4rNeV-vmM7YmeaRwMM2aWbNOhfjQ@mail.gmail.com>
On Fri, April 12, 2013 08:44:05 AM Otavio Salvador wrote:
> On Fri, Apr 12, 2013 at 6:13 AM, Thomas Senyk
>
> <thomas.senyk@pelagicore.com> wrote:
> > On Thu, April 04, 2013 10:42:16 PM Otavio Salvador wrote:
> .>> + renamed=$backend
>
> >> + mv $f $(echo $f | sed "s,-$backend\.so,.so,g")
> >
> > I'd personally rather vote for a symlink then a mv.
> > It's nearly the same cost, but it let's people identify which
> > implementation is installed (besides other things)
>
> The other uses of libraries with the backend suffix where already
> fixed and as we cannot have both backends at same image, working, I
> see no gain in duplicate this information. Can you elaborate it a
> little more?
No strong vote! :)
And it's not duplicate information ... it's just keeping the original
information (file name) rather then destroying the information (by renaming
it)
It's just that during development it's nice to see that the 'right' version of
you egl implementation got deployed.
... otherwise some people (me once in a while) will double-check if the gpu.bb
toke the right one.
'ls' looks nicer with:
libEGL.so -> libEGL-wl.so
libEGL-wl.so
then just:
libEGL.so
;)
... but again: no strong vote, I can happily live with the current approach ;)
>
> --
> Otavio Salvador O.S. Systems
> E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
> Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
next prev parent reply other threads:[~2013-04-12 15:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 1:42 [meta-fsl-arm][PATCH v2 1/5] gpu-viv-bin-mx6q: Rework package for a single backend use Otavio Salvador
2013-04-05 1:42 ` [meta-fsl-arm][PATCH v2 2/5] xf86-video-imxfb-vivante: Add missing dependency of virtual/xserver Otavio Salvador
2013-04-05 1:42 ` [meta-fsl-arm][PATCH v2 3/5] Revert "pointercal-xinput: Add pointercal.xinput to mxs" Otavio Salvador
2013-04-05 1:42 ` [meta-fsl-arm][PATCH v2 4/5] gst-plugins-gl: Fix dependency definition Otavio Salvador
2013-04-05 1:42 ` [meta-fsl-arm][PATCH v2 5/5] gst-plugins-gl: Fix build of X11 backend Otavio Salvador
2013-04-05 2:25 ` Philip Craig
2013-04-05 3:07 ` Otavio Salvador
2013-04-05 3:21 ` Philip Craig
2013-04-05 11:20 ` Otavio Salvador
2013-04-05 12:03 ` Philip Craig
2013-04-05 13:41 ` Otavio Salvador
2013-04-05 6:44 ` [meta-fsl-arm][PATCH v2 1/5] gpu-viv-bin-mx6q: Rework package for a single backend use Eric Bénard
2013-04-05 11:23 ` Otavio Salvador
2013-04-12 9:13 ` Thomas Senyk
2013-04-12 11:44 ` Otavio Salvador
2013-04-12 15:09 ` Thomas Senyk [this message]
2013-04-12 15:55 ` Otavio Salvador
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=2606466.EDyCjuJWjb@rudolf \
--to=thomas.senyk@pelagicore.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.