Date: Mon, 25 Nov 2024 16:10:10 +0200
Harald Achitz via SG15 <sg15_at_[hidden]> writes:
> Probably this: https://cps-org.github.io/cps/
I don't think it is. From the linked website:
> Like pkg-config files and CMake package configuration files, CPS files
> are intended to be produced by the package provider, and included in
> the package’s distribution. Additionally, the CPS file is not intended
> to cover all possible configurations of a package; rather, it is meant
> to be generated by the build system and to describe the artifacts of
> one or more extant configurations for a single architecture.
In other words, this format describes an artifact produced by one
build system to be consumed by another. What James is asking for is
a standardized description of how to produce said artifact.
> Probably this: https://cps-org.github.io/cps/
I don't think it is. From the linked website:
> Like pkg-config files and CMake package configuration files, CPS files
> are intended to be produced by the package provider, and included in
> the package’s distribution. Additionally, the CPS file is not intended
> to cover all possible configurations of a package; rather, it is meant
> to be generated by the build system and to describe the artifacts of
> one or more extant configurations for a single architecture.
In other words, this format describes an artifact produced by one
build system to be consumed by another. What James is asking for is
a standardized description of how to produce said artifact.
Received on 2024-11-25 14:09:04