From: Nikolay Dimitrov <picmaster@mail.bg>
To: Daiane Angolini <daiane.list@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-demos][PATCH] riotboard: Fix broken image builds against linux-fslc
Date: Mon, 04 May 2015 22:38:30 +0300 [thread overview]
Message-ID: <5547CAB6.5040706@mail.bg> (raw)
In-Reply-To: <CA+jg_OU6NdK7YYqCzba7SiE7m=8XSdO+NrDUFU71EEvpW2z=6g@mail.gmail.com>
Hi Daiane,
On 05/04/2015 08:06 PM, Daiane Angolini wrote:
> On Mon, May 4, 2015 at 10:33 AM, Nikolay Dimitrov <picmaster@mail.bg>
> wrote:
>> Hi Fabio,
>>
>> On 05/04/2015 03:41 PM, Fabio Estevam wrote:
>>>
>>> Hi Nikolay,
>>>
>>> On Thu, Apr 30, 2015 at 12:49 PM, Nikolay Dimitrov
>>> <picmaster@mail.bg> wrote:
>>>
>>>> +# FIXME: Workaround for building against linux-fslc
>>>> +RDEPENDS_${PN}_remove_imx6dl-riotboard = "gst-plugins-gl"
>>>
>>>
>>> This doesn't seem to scale very well as we would need to put
>>> every mx6q/dl board that uses linux-fslc in this list.
>>>
>>> Regards,
>>>
>>> Fabio Estevam
>>
>>
>> I completely understand and agree, but I don't feel qualified to
>> force all other mx6 maintainers to use the same approach. If others
>> decide to go this way, we can then use the "_remove" clause for all
>> "mx6" SOCs, and put appropriate comment in the file. But as of
>> today, I don't see such push.
>
> gst-plugins-gl is included in the image by:
> https://github.com/Freescale/meta-fsl-demos/blob/master/recipes-fsl/packagegroups/packagegroup-fsl-gstreamer-full.bb#L21
>
> right?
>
> So, remove opengl from your DISTRO_FEATURES and it should work.
>
>
> However, we have already this line:
>
> https://github.com/Freescale/meta-fsl-demos/blob/master/recipes-fsl/packagegroups/packagegroup-fsl-gstreamer-full.bb#L27
>
> Which means mx6sl cannot handle gst-plugins-gl. Riot is not mx6sl,
> so maybe you have spoted another corner case.
Thanks for your comments. I've already sent an email with same analysis
just before sending the patch, which uses the described above method.
>> Considering the amount of discussion my patches provoke, I'm now
>> more inclined to propose micro-changes that are more obvious/easier
>> to approve and move forward.
>
> Please, keep the discussion up and running. Please, keep the
> questions and the patches, we really need more experienced board
> maintainers for the community boards.
Regards,
Nikolay
next prev parent reply other threads:[~2015-05-04 19:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 15:49 [meta-fsl-arm-extra][PATCH v3] riotboard: Fix broken image builds against linux-fslc Nikolay Dimitrov
2015-04-30 15:49 ` [meta-fsl-demos][PATCH] " Nikolay Dimitrov
2015-05-04 12:41 ` Fabio Estevam
2015-05-04 13:33 ` Nikolay Dimitrov
2015-05-04 17:06 ` Daiane Angolini
2015-05-04 17:12 ` Gary Thomas
2015-05-04 19:38 ` Nikolay Dimitrov [this message]
2015-05-11 16:43 ` Nikolay Dimitrov
2015-05-11 17:09 ` Otavio Salvador
2015-05-11 17:24 ` Nikolay Dimitrov
2015-05-11 17:46 ` Otavio Salvador
2015-05-11 23:42 ` Nikolay Dimitrov
2015-05-12 12:41 ` Otavio Salvador
2015-05-13 4:09 ` Nikolay Dimitrov
2015-05-13 11:06 ` Otavio Salvador
2015-05-11 16:42 ` [meta-fsl-arm-extra][PATCH v3] " Nikolay Dimitrov
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=5547CAB6.5040706@mail.bg \
--to=picmaster@mail.bg \
--cc=daiane.list@gmail.com \
--cc=meta-freescale@yoctoproject.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.