RTEMS Source Builder | Generate custom pkgconfig files for dependencies (#131)

[Amar Takhar (@amar)]

Amar Takhar created an issue: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/131



## Summary

<!--Please provide as much information as possible such as error messages or attaching logs-->

Right now the RSB uses pkgconfig files generated by the the dependencies themselves.  The problem is if a dependency picks up a system library it will happily refer to that in the `.pc` file and we'll never know.

If we generate our own `.pc` files we'll be able to force it to use our includes and libraries.  This way it will always blow  up if it's for some reason wanting a system library or we've forgotten to add a dependency for a new package.

The QEMU recipe in the RSB doesn't use the RSB pkgconfig so it's bee pulling in system libraries.  This was discovered by @opticron 

There are a few ways we can go about this:

1. Generate our own `.pc` files from scratch
2. Search and replace system paths in the `.pc` files and point them back to the rsb
3. Blow up the build if a system path is found in the `.pc` file and figure out in the recipe how to do this.

Either way we want the RSB to be completely isolated from the system and a way to enforce doing this.

## Steps to reproduce

<!--Pre-set options
- milestone-->

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/131
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20251009/46836052/attachment.htm>