It's already in a common objxilinxsupport.yml file. The problem is that
it is being included by two different drivers both imported from the
xilinx upstream driver repo, so it currently attempts to install those
shared headers twice. I suppose the solution could be to bundle the
shared code together with any drivers that depend on it in a single
obj*.yml.
Kinsey
On 2/3/2023 1:11 PM, Sebastian Huber wrote:
On 03.02.23 19:45, Kinsey Moore wrote:
This is my first stab at solving this duplicate install problem. I
could manually solve the problem by deduplicating the object includes
and moving it up to the BSP, but that is less intuitive since these
drivers both depend on the same code and the BSP doesn't depend on it
directly.
Why don't you add the shared stuff to a objxilcommon.yml?
The approach in the wscript is a bit complex from my point of view.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
