From: Philipp Zabel <p.zabel@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 1/4] libjpeg: enable building libturbojpeg
Date: Fri, 18 Feb 2022 17:08:35 +0100 [thread overview]
Message-ID: <20220218160838.759601-1-p.zabel@pengutronix.de> (raw)
Enable building libturbojpeg for users of the simplified API.
Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
---
rules/libjpeg.in | 7 +++++++
rules/libjpeg.make | 5 ++++-
2 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/rules/libjpeg.in b/rules/libjpeg.in
index 53a9d9e09701..3304c6ac896f 100644
--- a/rules/libjpeg.in
+++ b/rules/libjpeg.in
@@ -19,4 +19,11 @@ config LIBJPEG_BIN
cjpeg and djpeg are simple bineries to convert some basic image
formats to jpeg (cjpeg) or convert them back from jpeg (djpeg)
+config LIBJPEG_TURBO
+ bool
+ prompt "Build and install libturbojpeg"
+ help
+ In addition to the traditional libjpeg API, also provide the less
+ powerful but more straightforward TurboJPEG API.
+
endif
diff --git a/rules/libjpeg.make b/rules/libjpeg.make
index 559a6d08d504..704f810a4bd4 100644
--- a/rules/libjpeg.make
+++ b/rules/libjpeg.make
@@ -60,7 +60,7 @@ LIBJPEG_CONF_OPT := \
-DWITH_JPEG8=ON \
-DWITH_MEM_SRCDST=ON \
-DWITH_SIMD=$(call ptx/onoff,LIBJPEG_SIMD) \
- -DWITH_TURBOJPEG=OFF
+ -DWITHOUT_TURBOJPEG=$(call ptx/ifdef, PTXCONF_LIBJPEG_TURBO,OFF,ON)
# ----------------------------------------------------------------------------
# Target-Install
@@ -76,6 +76,9 @@ $(STATEDIR)/libjpeg.targetinstall:
@$(call install_fixup, libjpeg,DESCRIPTION,missing)
@$(call install_lib, libjpeg, 0, 0, 0644, libjpeg)
+ifdef PTXCONF_LIBJPEG_TURBO
+ @$(call install_lib, libjpeg, 0, 0, 0644, libturbojpeg)
+endif
ifdef PTXCONF_LIBJPEG_BIN
@$(call install_copy, libjpeg, 0, 0, 0755, -, /usr/bin/cjpeg)
@$(call install_copy, libjpeg, 0, 0, 0755, -, /usr/bin/djpeg)
--
2.30.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2022-02-18 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 16:08 Philipp Zabel [this message]
2022-02-18 16:08 ` [ptxdist] [PATCH 2/4] aml: new package Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-18 16:08 ` [ptxdist] [PATCH 3/4] neatvnc: " Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-18 16:08 ` [ptxdist] [PATCH 4/4] wayvnc: " Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-18 16:27 ` [ptxdist] [PATCH 1/4] libjpeg: enable building libturbojpeg Christian Melki
2022-02-22 7:35 ` Michael Olbrich
2022-02-22 12:03 ` Philipp Zabel
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=20220218160838.759601-1-p.zabel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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