On Thu, Jan 4, 2024 at 4:40 PM Bernd Moessner <berndmoessne...@gmail.com> wrote:
> > On 04.01.2024 23:26, Kinsey Moore wrote: > > On Thu, Jan 4, 2024 at 4:03 PM Bernd Moessner <berndmoessne...@gmail.com> > wrote: > >> >> On 04.01.2024 22:33, Kinsey Moore wrote: >> > 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 >> > >> >> Hmm --rtems=<PATH> works on my side now. I use >> >> ./waf configure --prefix=${RTEMS_LWIP_INSTALL_DIR} >> --rtems=${RTEMS_OS_INSTALL_DIR} >> --rtems-tools=${RTEMS_TOOLCHAIN_INSTALL_DIR} >> --rtems-bsps=${RTEMS_BSP_ARCH}/${RTEMS_BSP_NAME} >> >> to build the project. >> > > Ah, sounds like this patch can be dropped, then. Being able to set the > RTEMS path is part of the generic rtems_waf functionality. > > Kinsey > > 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. > Ok, sorry. I misunderstood. The patch is fine to go in. Kinsey
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel