On 20/01/2023 7:44 pm, Anthony PERARD wrote: > When there isn't a version-script for a shared library (like for > unstable libs), we create one based on the current Xen version. But > that version-script became out-of-date as soon as Xen's version > changes and make as no way to regenerate the version-script on > rebuild. > > For unstable libs, we only needs the symver to be different from a > previous release of Xen. There's an option "--default-symver" which > allow to use the soname as symver and as the soname have the Xen > release version, it will be different for every release. With > --default-symver we don't need to generate a version-script. > > But we also need to know if there's already an existing version script > , for that we introduce $(version-script) to be used to point to the > path of the existing script. (Guessing if a version script exist for a > stable library with for example $(wildcard) won't work as a file will > exist when building the library without this patch.) > > We don't need the version-script unless we are making the shared > library so it is removed from the "all" target. > > Signed-off-by: Anthony PERARD <anthony.per...@citrix.com>
Acked-by: Andrew Cooper <andrew.coop...@citrix.com>
