Open Akshay-Belsare opened 1 year ago
Hi, We use this hard dependency because when we install the accelize-drmselftest application from our package feed on a Kria with Petalinux 2022.1, the Xilinx petalinux package feed install last version of XRT (2.14.0) which is not compatible with Petalinux 2022.1.
There is no separation in Xilinx package feed between rpm for petalinux 2022.1 and those for petalinux 2022.2 to prevent petalinux dnf dependency solver to install package for 2022.2 in a 2022.1 setup.
Furthermore, these recipe is tested and validated just for petalinux 2022.1 as Xilinx do not released 2022.2 bsp and platform for KV260 starter kit.
Hello - Given the fixed alignment of the version and the testing of this layer only with 2022.1 my suggestion would be to pull a release tag marked as "xlnx_2022.1" or similar which will include the specific version presently designated. This will make it clear that this version is specific to 2022.1 Xilinx tools and has been tested as part of a release testing. The "main" branch can then relax the specific XRT version and allow on-going collaborative development as we migrate tools versions moving forward. When ready with a next tested and aligned version then pull the next release tag.
Hi, We have created the release tag associated to petalinux 2022.1 (https://github.com/Accelize/meta-accelize/tree/REL221027_PL20221) and a dedicated branch for development of petalinux 2022.2 (https://github.com/Accelize/meta-accelize/tree/prerelease_2022.2). Let me know if it fits your request so I can close this issue.
In https://github.com/Accelize/meta-accelize/blob/honister/recipes-core/accelize-drmselftest/accelize-drmselftest.bb#L23 there is a hard dependency on ZOCL version 202210.2.13.479 The above zocl version is for Petalinux 2022.1 release, this dependency will be resolved only in the Petalinux 2022.1 release tool and BSP and will fail for any other version. A test build on Petalinux 2022.2 release with meta-accelize enabled has failed due to dependency version mismatch for ZOCL.
To resolve this the hard dependency on ZOCL version needs to be relaxed.