Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vcpkg is now difficult to use. #209

Open
cmaughan opened this issue Oct 2, 2023 · 4 comments
Open

vcpkg is now difficult to use. #209

cmaughan opened this issue Oct 2, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@cmaughan
Copy link

cmaughan commented Oct 2, 2023

The latest vcpkg for tomlplusplus now requires pkgconfig, which is a seperate install on windows. Previously I could just add tomlplusplus to my CMakelists.txt. I tried adding the extra PkgConfig stuff, and tried to install the extra findpackage binaries on windows, but gave up. I've just copied tomlplusplus into my tree.

@cmaughan cmaughan added the bug Something isn't working label Oct 2, 2023
@marzer
Copy link
Owner

marzer commented Oct 2, 2023

Ah that sucks. I don't know much about vcpkg but I'll look into at some point. Thanks for letting me know :)

gottyduke added a commit to gottyduke/DKUtil that referenced this issue Dec 14, 2023
@davidharabagiu
Copy link

Installing pkgconfig using choco worked for me:

choco install pkgconfiglite

You could also use the vcpkg port for toml++ 3.1.0 which doesn't require PkgConfig.

@cdacamar
Copy link

Is there any way of reverting the offending change? Taking a dependency on PkgConfig for a straight-forward library (it's usable as header-only) seems like massive overkill.

@gkoreman
Copy link

+1 to this. The PkgConfig dependency on vcpkg seriously detracts from the allure of a header only library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants