Dylan Baker

That makes my point though. If they go in a `tools` section, then there's no need for either a major version bump or reading/writing two fields, `tools/pkg-config-compat` (whatever that does),...

`A` on `sc`, `srb`, and `sep`. `SF` on `vendor` `F` on the rest

Meson has support for them, by running CMake with some custom cmake files that find a dependency and then use `message()` to communicate, haha. But I guess that's not something...

Actually, thinking about this more and looking at the sample, it has this: ```json "sample-shared": { "Type": "dylib", "Requires": [ ":sample-core" ], "Configurations": { "Optimized": { "Location": "@prefix@/lib64/libsample.so.1.2.0" }, "Debug":...

I'm not an expert on Windows, but you never link to the `.dll`, only the `.lib`, right?. If so there would never be a reason to specify the .dll, since...

> Link, yes, but you load the .dll. There are instances in which you want to know both paths. (For one, if something is trying to do automatic PATH mangling....

Okay, then I would settle from "must" to "should" language like: "A compliant Link-Location must point to a location to be passed to the linker, this location should conform to...

Here's my thoughts (because LLVM is such a pain, and always on my mind): I think it makes sense to encourage one CPS file per conceptual project (it's possible a...

> This fits naturally for some things like CMake, Meson, and bazel (maybe substituting :: for a / to make the name path-like). I'm not sure it's as natural a...

> Should CPS files adopt RelWithDebInfo as an explicit default or should it be unqualified like the pkg-config metadata? This probably deserves a separate discussion. On Linux at least it...