<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 4, 2024 at 4:40 PM Bernd Moessner <<a href="mailto:berndmoessner80@gmail.com">berndmoessner80@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<p><br>
</p>
<div>On 04.01.2024 23:26, Kinsey Moore
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jan 4, 2024 at
4:03 PM Bernd Moessner <<a href="mailto:berndmoessner80@gmail.com" target="_blank">berndmoessner80@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
On 04.01.2024 22:33, Kinsey Moore wrote:<br>
> This looks like it should be fine for now to enable
installing into <br>
> somewhere that isn't the installed BSP directory.
Longer term, <br>
> rtems-lwip should probably support similar options to
rtems-libbsd <br>
> such that the RTEMS path can be passed on the configure
line using <br>
> --rtems=<PATH>.<br>
><br>
> Kinsey<br>
><br>
><br>
> On Thu, Jan 4, 2024 at 12:55 PM <<a href="mailto:berndmoessner80@gmail.com" target="_blank">berndmoessner80@gmail.com</a>>
wrote:<br>
><br>
> From: Bernd Moessner <<a href="mailto:berndmoessner80@gmail.com" target="_blank">berndmoessner80@gmail.com</a>><br>
><br>
> ---<br>
> lwip.py | 7 ++++---<br>
> 1 file changed, 4 insertions(+), 3 deletions(-)<br>
><br>
> diff --git a/lwip.py b/lwip.py<br>
> index bd743a1..65f1ead 100644<br>
> --- a/lwip.py<br>
> +++ b/lwip.py<br>
> @@ -137,9 +137,10 @@ def build(bld):<br>
> includes=' '.join(test_app_incl))<br>
><br>
> lib_path = os.path.join(bld.env.PREFIX,
arch_lib_path)<br>
> - bld.read_stlib('telnetd', paths=[lib_path])<br>
> - bld.read_stlib('rtemstest', paths=[lib_path])<br>
> - bld.read_stlib('ftpd', paths=[lib_path])<br>
> + rtems_lib_path =
os.path.join(bld.env.RTEMS_PATH, arch_lib_path)<br>
> + bld.read_stlib('telnetd', paths=[lib_path,
rtems_lib_path])<br>
> + bld.read_stlib('rtemstest', paths=[lib_path,
rtems_lib_path])<br>
> + bld.read_stlib('ftpd', paths=[lib_path,
rtems_lib_path])<br>
><br>
> bld.program(features='c',<br>
> target='telnetd01.exe',<br>
> -- <br>
> 2.34.1<br>
><br>
> _______________________________________________<br>
> devel mailing list<br>
> <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
><br>
<br>
Hmm --rtems=<PATH> works on my side now. I use<br>
<br>
./waf configure --prefix=${RTEMS_LWIP_INSTALL_DIR} <br>
--rtems=${RTEMS_OS_INSTALL_DIR} <br>
--rtems-tools=${RTEMS_TOOLCHAIN_INSTALL_DIR} <br>
--rtems-bsps=${RTEMS_BSP_ARCH}/${RTEMS_BSP_NAME}<br>
<br>
to build the project.<br>
</blockquote>
<div><br>
</div>
<div>Ah, sounds like this patch can be dropped, then. Being
able to set the RTEMS path is part of the generic rtems_waf
functionality.</div>
<div><br>
</div>
<div>Kinsey <br>
</div>
</div>
</div>
</blockquote>
<p>The RTEMS_PATH was set up, but without the patch stated above it
wasnt showing on the linker comand line as library search dir. You
are absolutely right that my patch is only a temporary solution. I
think we should not have to set up the RTEMS_PATH in the way shown
above for every executable. I have simply to less knowledge of waf
and scripts around to provide a better and more general solution.
I just wanted to let you know that the configure line is okay -
the "real fix" must be somewhere deeper down.<br>
</p></div></blockquote><div>Ok, sorry. I misunderstood. The patch is fine to go in.</div><div><br></div><div>Kinsey <br></div></div></div>