On 9/9/2022 01:46, Chris Johns wrote:
On 9/9/2022 2:52 am, Kinsey Moore wrote:
At some point, the lwIP build needs to get better about managing which BSPs it
supports, but that's not a task for you here and now.
I think this is needed. Can lwip be built generically for a BSP that is not
specific covered in a list?
lwIP is not currently buildable for BSPs that have not been explicitly
added to the build. The first step would be a mostly-unified lwipopts
that provides defaults that are overridable by BSP-specific or possibly
user-provided configuration. The only reason I see to allow this is if
we want to let users bring their own lwIP drivers without incorporating
them into the rtems-lwip integration repository.
I ask because lwip has been added to the RSB 6/rtems-packages and I could not
build the erc32 BSP stack because lwip had an error.
I am fine with lwip being in ?/rtems-packages if it can be built for every bsp
at some generic level.
I'll look into better management of BSP-specific configuration and
making a generic build available for BSPs that don't have a particular
configuration available.
Kinsey
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
