Skip to content

Commit

Permalink
Test all Github Actions Windows - use LIBDIR replacing not fully correct
Browse files Browse the repository at this point in the history
  • Loading branch information
AndreMikulec committed Dec 2, 2023
1 parent ea5c4c9 commit 90e68dc
Showing 1 changed file with 9 additions and 2 deletions.
11 changes: 9 additions & 2 deletions .github/workflows/buildPLR.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2142,6 +2142,11 @@ jobs:
echo "pg_config SHAREDIR: ${SHAREDIR}"
export LIBDIR=$(pg_config | grep "^LIBDIR" | sed "s/ = /=/" | sed "s/^.*=//")
export LIBDIR="${LIBDIR}"
echo "pg_config LIBDIR: ${LIBDIR}"
#### END PG_HOME SECTION ####
#### BEGIN PKGCONFIG SECTION ####
Expand Down Expand Up @@ -2183,7 +2188,8 @@ jobs:
# We do not want to use that old "libpg" when compiling PL/R.
# Therefore, the PostgreSQL pkgconfig goes in front at the head.
#
export PKG_CONFIG_PATH="${PG_HOME}/lib/pkgconfig:${PKG_CONFIG_PATH}"
# export PKG_CONFIG_PATH="${PG_HOME}/lib/pkgconfig:${PKG_CONFIG_PATH}"
export PKG_CONFIG_PATH="${LIBDIR}/pkgconfig:${PG_HOME}/lib/pkgconfig:${PKG_CONFIG_PATH}"
export PKG_CONFIG_SYSTEM_INCLUDE_PATH="${PG_HOME}/include:${PKG_CONFIG_SYSTEM_INCLUDE_PATH}"
export PKG_CONFIG_SYSTEM_LIBRARY_PATH="${PG_HOME}/bin:${PG_HOME}/lib:${PKG_CONFIG_SYSTEM_LIBRARY_PATH}"
Expand All @@ -2199,7 +2205,8 @@ jobs:
# From the libpq.pc file, create a libpostgres.pc file.
if [ ! -f "${PG_HOME}/lib/pkgconfig/libpostgres.pc" ]
then
cat "${PG_HOME}/lib/pkgconfig/libpq.pc" | sed "s/libpq/libpostgres/g" | sed "s/-lpq/-lpostgres/" > "${PG_HOME}/lib/pkgconfig/libpostgres.pc"
# cat "${PG_HOME}/lib/pkgconfig/libpq.pc" | sed "s/libpq/libpostgres/g" | sed "s/-lpq/-lpostgres/" > "${PG_HOME}/lib/pkgconfig/libpostgres.pc"
cat "${LIBDIR}/pkgconfig/libpq.pc" | sed "s/libpq/libpostgres/g" | sed "s/-lpq/-lpostgres/" > "${PG_HOME}/lib/pkgconfig/libpostgres.pc"
fi
# This is Part 2 of 2 of a hack to make "meson" think that "libpostgres" is a library
Expand Down

0 comments on commit 90e68dc

Please sign in to comment.