This looks like it should be fine for now to enable installing into
somewhere that isn't the installed BSP directory. Longer term, rtems-lwip
should probably support similar options to rtems-libbsd such that the RTEMS
path can be passed on the configure line using --rtems=<PATH>.

Kinsey


On Thu, Jan 4, 2024 at 12:55 PM <berndmoessne...@gmail.com> wrote:

> From: Bernd Moessner <berndmoessne...@gmail.com>
>
> ---
>  lwip.py | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/lwip.py b/lwip.py
> index bd743a1..65f1ead 100644
> --- a/lwip.py
> +++ b/lwip.py
> @@ -137,9 +137,10 @@ def build(bld):
>                  includes=' '.join(test_app_incl))
>
>      lib_path = os.path.join(bld.env.PREFIX, arch_lib_path)
> -    bld.read_stlib('telnetd', paths=[lib_path])
> -    bld.read_stlib('rtemstest', paths=[lib_path])
> -    bld.read_stlib('ftpd', paths=[lib_path])
> +    rtems_lib_path = os.path.join(bld.env.RTEMS_PATH, arch_lib_path)
> +    bld.read_stlib('telnetd', paths=[lib_path, rtems_lib_path])
> +    bld.read_stlib('rtemstest', paths=[lib_path, rtems_lib_path])
> +    bld.read_stlib('ftpd', paths=[lib_path, rtems_lib_path])
>
>      bld.program(features='c',
>                  target='telnetd01.exe',
> --
> 2.34.1
>
> _______________________________________________
> 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

Reply via email to