BSD licensed Picolibc 1.0 released

[Chris Johns]

On 25/9/19 1:03 am, Gedare Bloom wrote:
> Hi mko,
> 
> RTEMS has a fairly strong relationship (dependency) with newlib, and
> that has been working well for a long time. Although the prospect of
> having a way to 'drop-in' alternative libc could be nice for small
> targets, it would be of more interest to us to see ways to optimize
> newlib to shrink it if needed. The use of stripped-down libc for
> low-resource targets usually means a feature-rich RTOS like RTEMS will
> not be needed either. These kinds of libc are more interesting for
> baremetal or low-complexity RTOSs, and some hypervisor-like systems
> that want an extremely small, trusted code base.

I agree and it builds with meson which is also interesting.

I am finding the license a little confusing. The repo on github [1] contains
GPL2, GPL3, LGPL, Newlib and more licenses while the README.md says there is no
GPL bits from newlib in the repo and it is basically a mix of 2 and 3 clause
BSD. Why have a copy of the GPL licenses in the repo?

Chris

[1] https://github.com/keith-packard/picolibc

> 
> But, thanks for the heads up about the picolibc.
> 
> Gedare
> 
> On Tue, Sep 24, 2019 at 5:09 AM mko <me at mko.io> wrote:
>>
>> Hi List,
>> I just got this news from my RSS feed, after a brief read, I think this is a better and simpler alternative of newlib library, Does anyone know how to use it in rtems project?
>>
>> mko
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>