Compatibility should also judge from 'supports' from vcpkg.json in packages page #76
Open
Description
In packages page, it only judges the supported triplets from ci.baseline.txt in Update-PortIndex.ps1 currently, however we already moved to 'supports' and only left parts of port in ci.baseline.txt, that leads to wrong supported triplets in output.json, which our website reads from. the output.json is generated from Update-PortIndex.ps1.
Eg: yasm
It only supports "windows & !uwp & !arm" in vcpkg.json, however in our website, it says supported all triplets, which is wrong.
Metadata
Assignees
Labels
No labels