On Tue, Jul 25, 2023 at 5:13 AM Sebastian Huber
<sebastian.hu...@embedded-brains.de> wrote:
>
> This allows application and library build systems to derive option
> values from the BSP base and family names.
> ---
> spec/build/bsps/pkgconfig.yml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/spec/build/bsps/pkgconfig.yml b/spec/build/bsps/pkgconfig.yml
> index e08c83fe27..afaffbbf0f 100644
> --- a/spec/build/bsps/pkgconfig.yml
> +++ b/spec/build/bsps/pkgconfig.yml
> @@ -15,6 +15,8 @@ content: |
> ABI_FLAGS=${ABI_FLAGS}
> RTEMS_ARCH=${ARCH}
> RTEMS_BSP=${BSP_NAME}
> + RTEMS_BSP_BASE=${BSP_BASE}
> + RTEMS_BSP_FAMILY=${BSP_FAMILY}
These expose a little bit of the internal working of the build system.
I think it's fine, since these two fields should not change over time.
But, it commits us to maintain this mapping and these variables.
> RTEMS_MAJOR=${__RTEMS_MAJOR__}
> RTEMS_MINOR=${__RTEMS_MINOR__}
> RTEMS_REVISION=${__RTEMS_REVISION__}
> --
> 2.35.3
>
> _______________________________________________
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
