We now generate postgresql-extension.pc and postgresql-extension-warnings-uninstalled.pc, containing the correct flags to build an extension fairly easily, without otherwise using postgres' build infrastructure. I manually tested this on linux and windows, but we should have automated tests for this.
Likely just as part of our normal testsuite. If we do that, it might also be worth writing a test for building the same extension via pgxs.
My manual tests were just:
build against (pseudo-)installed postgres:
PKG_CONFIG_SYSROOT_DIR=/tmp/meson/tmp_install PKG_CONFIG_PATH=/tmp/meson/tmp_install/tmp/meson-install/lib/x86_64-linux-gnu/pkgconfig/ m setup build
ninja -C build -v
build against postgres build tree:
PKG_CONFIG_PATH=/tmp/meson/meson-uninstalled m setup build --wipe && ninja -C build -v
ninja -C build -v
on windows with msvc it likely would be worth testing both --buildtype vs and --buildtype ninja
We now generate postgresql-extension.pc and postgresql-extension-warnings-uninstalled.pc, containing the correct flags to build an extension fairly easily, without otherwise using postgres' build infrastructure. I manually tested this on linux and windows, but we should have automated tests for this.
Likely just as part of our normal testsuite. If we do that, it might also be worth writing a test for building the same extension via pgxs.
My manual tests were just:
build against (pseudo-)installed postgres:
build against postgres build tree:
on windows with msvc it likely would be worth testing both --buildtype vs and --buildtype ninja