Skip to content

Consider generating CMake config scripts for packages that don't natively provide them #616

@ras0219-msft

Description

@ras0219-msft

Relevant to several ports which required rewriting their buildsystems from scratch in CMake (#603).

Because Vcpkg has opinions about how packages should be laid out and linked, we have all the information needed to generate general-purpose CMake configure scripts for every library we package (even those that don't use CMake!). This would greatly simplify the job of maintainers who need to rewrite library buildsystems in CMake to better support our configuration options (UWP, static linking the CRT, etc) because they would be able to rely on find_package() to do the heavy lifting.

Now, it is certainly not our intention to permanently fork libraries, so if a library did decide to start supplying its own native CMake configure scripts, we would have to make (breaking!) changes to switch.

Metadata

Metadata

Assignees

No one assigned

    Labels

    category:vcpkg-featureThe issue is a new capability of the tool that doesn’t already exist and we haven’t committed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions