Skip to content

vcpkg port requirements #36

@sandercox

Description

@sandercox

There are a few issues with the library that start leaking defines and includes #32 #33 and also setting up the libntv2 target has some entries that are making it custom which I don't think they need to be #34

If those PRs can be merged we can provide an easy vcpkg based workflow. At present I have a private vcpkg-port that has these PRs as patches but export fixes are not something they support on the vcpkg side as they think they should be upstream. Had some discussion about that in the past.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions