-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[openal-soft] Incorrect prefix in .pc file #19316
Labels
category:port-bug
The issue is with a library, which is something the port should already support
Comments
NancyLi1013
added
the
category:port-bug
The issue is with a library, which is something the port should already support
label
Aug 3, 2021
Hi @s0600204 Thanks for posting this issue. Needs to add |
s0600204
added a commit
to s0600204/0ad
that referenced
this issue
Sep 6, 2021
s0600204
added a commit
to s0600204/0ad
that referenced
this issue
Sep 27, 2021
s0600204
added a commit
to s0600204/0ad
that referenced
this issue
Jan 15, 2022
s0600204
added a commit
to s0600204/0ad
that referenced
this issue
Jan 15, 2022
s0600204
added a commit
to s0600204/0ad
that referenced
this issue
Jan 16, 2023
s0600204
added a commit
to s0600204/0ad
that referenced
this issue
Feb 24, 2023
s0600204
added a commit
to s0600204/0ad
that referenced
this issue
Apr 11, 2023
s0600204
added a commit
to s0600204/0ad
that referenced
this issue
May 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
category:port-bug
The issue is with a library, which is something the port should already support
Current problem
The
prefix
line written to theopenal.pc
file is incorrect. It currently looks something like:(Exact text will differ depending on triplet, and the location of where vcpkg is building things.)
Proposed solution
Based on other .pc files exported by vcpkg, it should read:
Describe alternatives you've considered
I'm currently employing a workaround (search-replace of text) in a project that relies on .pc files. Would like to remove that workaround if possible.
The text was updated successfully, but these errors were encountered: