From: Babanpreet Singh <bbnpreetsingh@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>, Ross Burton <ross.burton@arm.com>,
Babanpreet Singh <bbnpreetsingh@gmail.com>
Subject: [meta-oe][PATCH 2/3] pgxs.bbclass: add class for PostgreSQL extensions
Date: Wed, 11 Nov 2026 20:39:56 +0000 [thread overview]
Message-ID: <20261111203957.7-3-bbnpreetsingh@gmail.com> (raw)
In-Reply-To: <20261111203957.7-1-bbnpreetsingh@gmail.com>
Extensions that build with PGXS need the same dependency, make
arguments and FILES. Put them in a class so a recipe only has to
inherit pgxs.
Signed-off-by: Babanpreet Singh <bbnpreetsingh@gmail.com>
---
meta-oe/classes/pgxs.bbclass | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
create mode 100644 meta-oe/classes/pgxs.bbclass
diff --git a/meta-oe/classes/pgxs.bbclass b/meta-oe/classes/pgxs.bbclass
new file mode 100644
index 0000000000..b1c7aca264
--- /dev/null
+++ b/meta-oe/classes/pgxs.bbclass
@@ -0,0 +1,22 @@
+#
+# Copyright OpenEmbedded Contributors
+#
+# SPDX-License-Identifier: MIT
+#
+
+# Class for PostgreSQL extensions that are built with PGXS
+
+DEPENDS += "postgresql"
+
+# USE_PGXS is for makefiles that can also build inside the PostgreSQL tree
+EXTRA_OEMAKE:append = " USE_PGXS=1 PG_CONFIG=pg_config"
+
+pgxs_do_install() {
+ oe_runmake install DESTDIR=${D}
+}
+
+EXPORT_FUNCTIONS do_install
+
+FILES:${PN} += "${libdir}/postgresql ${datadir}/postgresql"
+
+RDEPENDS:${PN} += "postgresql"
--
2.43.0
next prev parent reply other threads:[~2026-11-11 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 20:39 [meta-oe][PATCH 0/3] postgresql: add PGXS extension support and pg_cron Babanpreet Singh
2026-11-11 20:39 ` [meta-oe][PATCH 1/3] postgresql: make PGXS usable for cross-building extensions Babanpreet Singh
2026-11-11 20:39 ` Babanpreet Singh [this message]
2026-11-11 20:39 ` [meta-oe][PATCH 3/3] pg-cron: add recipe Babanpreet Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261111203957.7-3-bbnpreetsingh@gmail.com \
--to=bbnpreetsingh@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross.burton@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox