Skip to content

using vcpkg release static libraries in Visual Studio debug builds fails #2153

@BeErikk

Description

@BeErikk

If I understand it right, the idea is that you should use debug versions of your vcpkg builds when you are doing Visual Studio debug builds of your project. It's a different approach compared with for example the Windows SDK where all libraries are release builds. I guess it can be useful in some circumstances, but it surely adds complexity. I think if I add the -nodefaultlib linker option and the -Zl compiler option to vcpkg static library builds, I have a choice to do either way. If so, how can I add these options in a convenient way?

edit:
There's also the issue of mixing vcpkg static library with dynamic linked libraries. A thing you most certainly want to do.

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