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. 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?
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?
Chris
> ---
> spec/build/bsps/pkgconfig.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/spec/build/bsps/pkgconfig.yml b/spec/build/bsps/pkgconfig.yml
> index a9462fcc95..8a3c3677a4 100644
> --- a/spec/build/bsps/pkgconfig.yml
> +++ b/spec/build/bsps/pkgconfig.yml
> @@ -22,7 +22,7 @@ content: |
> Name: ${ARCH}-rtems${__RTEMS_MAJOR__}-${BSP_NAME}
> Version: ${RTEMS_VERSION}
> Description: RTEMS BSP ${ARCH}/${BSP_NAME}
> - Cflags: $${ABI_FLAGS} -I$${includedir}
> + Cflags: $${ABI_FLAGS} -isystem$${includedir}
> Ldflags: -B$${libdir} ${PKGCONFIG_LDFLAGS}
> Libs: -B$${libdir} ${PKGCONFIG_LDFLAGS}
> copyrights:
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
