Closed iyanging closed 3 years ago
It sounds reasonable as users should not touch PostgreSQL header directly, but use TaoPQ instead.
Thank you for your report, could you please open a pull request with your suggestion?
It sounds reasonable as users should not touch PostgreSQL header directly, but use TaoPQ instead.
Thank you for your report, could you please open a pull request with your suggestion?
Ok! I'll open a PR.
Maybe try removing the find_package(PostgreSQL REQUIRED)
from your CMakeLists.txt, as this should come in transparently from taoPQ. Maybe there's a conflict there that two different versions are now installed/used? (I'm just guessing)
In my CMakeLists.txt, vcpkg is installed in build directory by FetchContext. Then vcpkg installs the other dependencies in its source directory, which is still in my project's build directory. When taopq exports libpq's include directory in target_include_directory as public/interface, cmake will check if the path is prefixed in my project's build/source directory.
BOOM!
So, there is nothing wrong with taopq. Thanks very much for your kind helps!
I have a
CMakeLists.txt
like this:But it failed with:
After I applied the following patch, CMake can be successfully configured.
So I think maybe the change can directly happen on the code to avoid this patch ?
BTW,
taoPQ
is a very wonderful thing, THANKS for your libraries!