[oe] [PATCH][meta-oe] freerdp: get out of "nonworking", fix build, improve

Otavio Salvador otavio.salvador at ossystems.com.br
Thu Oct 8 16:30:21 UTC 2015


On Thu, Oct 8, 2015 at 12:24 PM, Martin Jansa <martin.jansa at gmail.com> wrote:
> On Wed, Oct 07, 2015 at 06:36:41PM -0700, Khem Raj wrote:
>>
>> > On Oct 6, 2015, at 3:29 PM, Martin Jansa <martin.jansa at gmail.com> wrote:
>> >
>> > On Tue, Oct 06, 2015 at 06:58:25PM -0300, Otavio Salvador wrote:
>> >> On Sun, Oct 4, 2015 at 6:13 AM, Manuel Bachmann <manuel.bachmann at iot.bzh> wrote:
>> >>> We make the "freerdp" recipe active again, fix the build
>> >>> by pulling a more recent version (the "stable" branches are
>> >>> buggy and useless), and fix ARM runtime with -fPIC.
>> >>>
>> >>> We can then :
>> >>> - make X11 non-mandatory ;
>> >>> - add support for Wayland ("wlfreerdp" client) ;
>> >>> - add support for DirectFB ("dfreerdp" client) ;
>> >>> - add support for GStreamer 1.0 ;
>> >>> - make "heavy" features such as pulseaudio, cups...
>> >>> non-mandatory.
>> >>>
>> >>> We really want to install the "winpr-makecert" tool to have
>> >>> TLS, but CMake does not position its RPATH cleanly, so let
>> >>> us have a custom patch for that until it gets sorted out.
>> >>>
>> >>> Signed-off-by: Manuel Bachmann <manuel.bachmann at iot.bzh>
>> >>
>> >> I fully agree with the changes and those are very welcome. However, it
>> >> would be good if you could move from nonworking in one patch and do
>> >> the changes here in another patch.
>> >
>> > I wanted to get rid of all nonworking directories, I'm sending patch
>> > series which reverts the recipe moves and replaces it with PNBLACKLIST.
>>
>> PNBLACKLIST still causes parsing overhead. I would suggest to move it to a layer under meta-openembedded
>> like meta-trash or some such, if someone gets it to work move it back to the appropriate layer.
>
> Lets move all blacklisted recipes to meta-broken or some such after
> jethro is branched.
>
> Big advantage of PNBLACKLIST is that it's easy to unblacklist from
> distro/local.conf and that bbappends in upper layer are still parsed
> corectly, moving the recipes to separate layer (which wont be included
> in any sane buidls) will force bbappends to be removed and then possibly
> reintroduced when the original recipe is fixed and moved back to
> appropriate layer.

I like to meta-broken proposal however I think it should still have
the blacklist. It helps highlight a possible cause and allow for easy
development of fixup patch.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750



More information about the Openembedded-devel mailing list