Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository

["Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov>]

On Mar 3, 2021, at 6:45 PM, Chris Johns via Core-talk <core-talk at aps.anl.gov> wrote:

We should encourage users to add BSP build stacks to the RSB. I remember Andrew
Johnson posted on for a Coldfire. We should merge that one.

That file was trivial to create, it ought to be easy to automate generating it.

However one drawback is that it always builds the compiler and toolchain as well as the BSP, so anyone working on more than one BSP will be wasting cycles if they use that. I don’t know if RSB could be taught to not do toolchain builds unnecessarily, or if you could provide a different set of recipes that don’t have them as a component to be built?

Michael Davidsaver taught me to run commands like this instead to avoid wasting cycles when I had already built the toolchain:

../source-builder/sb-set-builder \

    --host=powerpc-rtems5 --target=powerpc-rtems5 \

    --prefix=/home/anj/RTEMS-5.1/rtems-5.1 \

    --with-rtems-bsp=mvme3100 \

    5/rtems-kernel 5/rtems-libbsd

BTW why do both the --host= and --target= options there (equivalent to %defines in the .bset file) specify the RTEMS target? That seems weird to me.

- Andrew

-- 

Complexity comes for free, simplicity you have to work for.