Why the __ around RTEMS_ADA and no other option? I think the first order of business is to explain how to translate existing configure and build steps to the new one. I think adding a simple example with a couple of enable/disable and the corresponding waf would help. Every user has to face this.
Then explaining multiple bsps but I don't know how common that is in actual use. Let's focus on getting folks across the transition hurdle first. On Sat, Sep 26, 2020, 6:37 AM Chris Johns <chr...@rtems.org> wrote: > > > On 26 Sep 2020, at 1:17 am, Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > > > > On 25/09/2020 17:12, Gedare Bloom wrote: > > > >>> +Migration from Autoconf/Automake > >>> +================================ > >>> + > >>> +The Autoconf/Automake based build system used a ``configure`` command > to > >>> +configure a single BSP and ``make`` to build it. The ``configure`` > command is > >> You can make multiple BSPs, so it is a little bit imprecise. Maybe: > >> "configure a single target architecture and one or more BSPs" and > ``make`` ... > >> > > Ok, but I am not sure if it was an intentional feature that you could > build more than one BSP. > > It was. As Gedare says it was only one architecture due to the single > —target option. I think no BSP option built the lot which was painful due > to the time it took and the disk space. > > Chris > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
