On 11/9/22 11:30 pm, Kinsey Moore wrote: > On 9/10/2022 20:22, Chris Johns wrote: >> On 10/9/2022 12:07 pm, Kinsey Moore wrote: >>> This removes the default BSP include path from environment variables so >>> that rtems-lwip can build even when there's a stale version with >>> outdated headers installed in the BSP. >> >> I am not following what this does and what problem you are attempting to >> solve? >> >> I am not comfortable seeing rtems_waf being overridden like this. >> >> Chris >> > This is approximately the same change that you did for libbsd that shuffles > the > include paths so that lwip builds against local headers first and isn't broken > by a stale install of rtems-lwip in the BSP install directory.
Yes it is the workaround to the problem. It is not 100% fool proof but it is good enough for most cases (eg does not handle deleting a header that is installed). The correct method is sandboxing the prefix into a separate directory so you can delete the package you are working on. I am wondering if rtems_waf handle this so we avoid coping the solution to multiple places? Would having rtems_waf always append the BSP include work? Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
