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

[Vijay Kumar Banerjee]

On Thu, Mar 4, 2021 at 8:33 AM Vijay Kumar Banerjee <vijay at rtems.org> wrote:
>
> On Thu, Mar 4, 2021 at 7:26 AM Joel Sherrill <joel at rtems.org> wrote:
> >
> >
> >
> > On Thu, Mar 4, 2021 at 8:22 AM Heinz Junkes <junkes at fhi-berlin.mpg.de> wrote:
> >>
> >> I have installed the legacy package but the files are not there.
> >> I guess they were just forgotten in the legacy package.
> >
> >
> > I'd guess Vijay forgot to install them. Certainly easy enough to do.
> >
> they're getting installed in the lib/ directory in the prefix:
> beatnik/lib/include/rtems/telnetd.h
> beatnik/lib/librtemsNfs.h
> beatnik/lib/rtems/rtems_bsdnet.h
>
> For rtems_bsdnet.h and librtemsNfs.h, the right place for install was
> supposed to be lib/include I guess (?) that might be the reason that
> it's not being found from your application as it's searching for it in
> the include directory. I'll push a fix to install it in the include

Here's the diff. Could you please try this diff and let me know if
it's getting installed in the expected location?
```
diff --git a/netlegacy.py b/netlegacy.py
index 037e2ee..fce2cc9 100644
--- a/netlegacy.py
+++ b/netlegacy.py
@@ -100,10 +100,10 @@ def build(bld):

     bld.install_files(os.path.join('${PREFIX}', arch_lib_path),
                       ["libnetworking.a"])
-    bld.install_files(os.path.join('${PREFIX}', arch_lib_path),
+    bld.install_files(os.path.join('${PREFIX}', arch_lib_path,
'include', 'libchip'),
                       [os.path.join('./bsps/include/libchip/', f)
                       for f in os.listdir('./bsps/include/libchip/')])
     for i in include_files:
         bld.install_files(os.path.join('${PREFIX}',
-                          arch_lib_path, i),
+                          arch_lib_path, 'include', i),
                           include_files[i])
```


> directory, but in the current state, these files do get installed in
> the prefix location somewhere. Could you please try the ./waf install
> again and see if these files are getting installed somewhere in the
> prefix?
>
>
> Best regards,
> Vijay
>
> > Eventually the NFSv2 client will need to be in the legacy stack
> > package. But until the port of the FreeBSD NFSv4 client is available
> > in libbsd, the existing NFSv2 client has to be used for both stacks.
> > I suppose this may end up being the one piece of lingering clean up.
> >
> > --joel
> >
> >>
> >> Heinz
> >>
> >>
> >> > On 4. Mar 2021, at 14:52, Joel Sherrill <joel at rtems.org> wrote:
> >> >
> >> > Did you install the legacy package? If you installed it in the same place
> >> > as the RTEMS 5 BSP, I would expect it to be there. This SHOULD be
> >> > equivalent to prior split.
> >>