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

New pkg-config requirement to find libogg and libopus does not play well with Win32 #38

Open
silverbacknet opened this issue Oct 21, 2022 · 1 comment

Comments

@silverbacknet
Copy link

It used to be that I could use cmake to generate VC project files, manually specifying the location of headers and libs if necessary. Sometime recently, a new dependency on pkg-config was inserted in an effort to simplify the logic, which may work well for *nix, but seems to completely fail in a win32 environment. First configuration fails on a missing pkg-config, which is not a standard part of any win32 build-chain, and even once acquired, it's useless because builds simply aren't packaged that way in win32, despite using bog-standard cmake for libogg and libopus, which built just fine.

Now, short of butchering the cmake files, I have legitimately no idea how to add the library information or bypass a check that can never work on this system. Manually setting the location simply results in it being reset when pkg-config fails. I tried setting up vcpkg but that doesn't seem to work either.

@rillian
Copy link
Contributor

rillian commented Oct 22, 2022

I thought cmake had its own package description format, and the ogg and opus library locators were supposed to use that, and only fall back the pkg-config?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants