Find PostgreSQL correctly #8435
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nerzhul
approved these changes
Mar 31, 2019
nerzhul
added
@ Build
|
Just fixed a typo in the commit message. |
nerzhul
approved these changes
Apr 2, 2019
SmallJoker
approved these changes
Apr 7, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@nerzhul , You implemented the original part, please review. Thanks.
ce42ff9
As there might be questions:
See https://cmake.org/cmake/help/v3.14/module/FindPostgreSQL.html
The bulk to get an
PostgreSQL_ADDITIONAL_SEARCH_PATHSdid not work correctly the whole years, so I consider it as not needed.This makes PostgereSQL usable on Windows too