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
[libpq] Update to 12.2 and some feature fixes #10915
[libpq] Update to 12.2 and some feature fixes #10915
Conversation
fix some issues with features feature combination client+nls does not compile with latest VS due to libpq src's accessing an implementation detail (needs upstream fix)
Hi @Neumann-A |
Related issue #9866 |
/azp run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
@Neumann-A On Windows:
When I run
But if I remove It's so weird. On Visual Studio 2019, On Linux:
Current;y, feature
Note: On x64-windows-static
Personally, it might be better to remove these features that are not supported or implemented currently. What do you think about this? @Neumann-A I also have a question about the first kind of error: |
Missing vcpkg ports. Need to be added to make those work. Especially kerberos enables gssapi in libpq which should be added to get everything included into libpq. The other features mainly influence details or include other contributions.
intentionally. Those features are not supported on Windows. Give me a Supports:-Field for features ;)
means if somebody wants/needs to use these feature they need to implement it in the portfile.
Needs to be fixed upstream.
I personally don't like to remove work already done. Extracting the possible features of a port is always kind of a headache and that is why I personally always add all features which I can see even if they might not yet be supported by VCPKG. One way to deal with something like that would be to allow comments in the
Looking through the perl scripts feature client is currently not supported on x64-windows-static. Requires a lot of changes to make it work
The ports do not exists. So they need to be added to vcpkg. python was just missing the version. |
@Neumann-A Since vcpkg currently does not support the |
@Neumann-A |
…atures # Conflicts: # ports/libpq/CONTROL
Alright, this looks good to me! Thanks @Neumann-A :D |
should fix some issues mentioned in #10875 + and update to 12.2