On 9/28/2022 19:03, Chris Johns wrote:
On 29/9/2022 7:13 am, Kinsey Moore wrote:
This allows any builds targeting an installed RTEMS BSP to override
headers in the installed BSP reliably, including headers previously
installed by that or other builds. This includes applications, network
stacks, libraries, and any other builds.
I am a little confused by these comments. This change effects the generated .pc
file for a BSP so it is only used once it is installed.
Correct, this is a fix for things like rtems-libbsd and rtems-lwip that
allows them to build correctly even if there are existing conflicting
installations of that library already installed in the BSP install.
An install should update
the headers at the same time the .pc is installed and made available so what is
old or previous? What are the "builds targeting" you refer too?
"builds targeting an installed RTEMS BSP" refers to any external build
that uses installed RTEMS headers and libraries. These external builds
can install their own files in the BSP install.
I think defining the include search of RTEMS BSP and any vertical stack packages
headers installed under the same prefix as system headers seems like the right
thing to do. However this change will silence warnings from RTEMS (and installed
packages). Is that want we want?
What warnings will this silence? It shouldn't affect RTEMS builds
because RTEMS doesn't use the pkgconfg while building. It still places
installed headers before actual system/tools headers in the include
hierarchy, so any build errors generated that way should be preserved.
Kinsey
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
