On 30/5/2024 6:44 am, Miroslaw Dach wrote:
> Hi John and Joel,
>
>> It is enable/disable networking (e.g. --enable-networking when you configure
> RTEMS itself) and then do not reference the legacy repository at all.
> I built RTEMS 5 with --enable-networking
>>and then do not reference the legac
Hi John and Joel,
> It is enable/disable networking (e.g. --enable-networking when you
configure RTEMS itself) and then do not reference the legacy repository at
all.
I built RTEMS 5 with --enable-networking
>and then do not reference the legacy repository at all.
How to build then rtems-net-ser
Hi
rtems-net-legacy only works with 6+. It was still included in the rtems
source tree in versions 5 and earlier. It is enable/disable networking
(e.g. --enable-networking when you configure RTEMS itself) and then do not
reference the legacy repository at all.
For 6, there is waf and no network s
Hello.
Thanks for the example configuring waf. I built v5.3 for Raspberry Pi using RSB
after failing with waf.
Legacy components are more likely to build using “legacy” RSB instead of WAF.
I don’t know where you can find that missing test-info.h file. But you probably
don’t need it at first bu
Hi All,
I have tried first to build rtems-net-services.
The configure faction:
waf configure --prefix=/my_devl/rtems-5/5 --rtems-version=5
--rtems-archs=powerpc --rtems-bsps=powerpc/mvme3100
failed:
Checking for library bsd : not found
Checking for library networking
