RTEMS 6 branching

Chris Johns chrisj at rtems.org
Thu Apr 25 00:08:03 UTC 2024

On 25/4/2024 12:06 am, Peter Dufault wrote:
>> On Apr 24, 2024, at 9:27 AM, Kinsey Moore <kinsey.moore at oarcorp.com> wrote:
>> That use case definitely wasn't considered for rtems-lwip and I don't know that it's ever been discussed. If that were intended, I'd expect a "./waf uninstall" target to exist that would remove the installed network stack so that you could install a different one since the different stacks install vastly different sets of headers. IIRC, Chris advocates for installing the network libraries into a different location than the installed BSP to allow you to choose which you want at a later time.
> I've been moving a driver from legacy to bsd so I definitely need to easily switch back and forth for the same BSP for testing.
> I agree with Chris, but it's apparently a desirement, not a requirement, so it shouldn't hold up the branching.

Agreed. It would be nice but is it something user would really want or use? I
get there are use cases like the one you raise but a single installed network
stack in a single install prefix makes it easier to write build system checks to
detect the type of stack. I have applications that can switch between legacy and
libbsd and that is important when migrating stacks and debugging.


More information about the devel mailing list