From: rainbox2k12 via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org <buildroot@buildroot.org>
Subject: [Buildroot] package/vte: install to staging
Date: Mon, 17 Jan 2022 11:44:19 +0000 (UTC) [thread overview]
Message-ID: <20220117114419.B8EAB3F465@exit1-us.msgsafe.io> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 197 bytes --]
Yann,
Can you accept my patch as an attached text document?
Cheers,
Rainer
\-- Sent using MsgSafe.io's Free Plan Private, encrypted, online communication
For everyone. https://www.msgsafe.io
[-- Attachment #1.2: Type: text/html, Size: 480 bytes --]
[-- Attachment #2: vte-install-staging.patch --]
[-- Type: text/x-patch, Size: 648 bytes --]
package/vte: install to staging
vte also provides libvte, a library that can be linked to by other
programs, so install it in staging.
Signed-off-by: Rainer Jonsson <rainbox2k12@msgsafe.io>
------
diff --git a/package/vte/vte.mk b/package/vte/vte.mk
index 07e8136..ceb2f09 100644
--- a/package/vte/vte.mk
+++ b/package/vte/vte.mk
@@ -11,6 +11,7 @@ VTE_SITE = http://ftp.gnome.org/pub/gnome/sources/vte/$(VTE_VERSION_MAJOR)
VTE_DEPENDENCIES = host-pkgconf libgtk3 pcre2 $(TARGET_NLS_DEPENDENCIES)
VTE_LICENSE = LGPL-3.0+
VTE_LICENSE_FILES = COPYING.LGPL3
+VTE_INSTALL_STAGING = YES
ifeq ($(BR2_PACKAGE_ICU),y)
VTE_CONF_OPTS += -Dicu=true
[-- Attachment #3: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-01-17 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 11:44 rainbox2k12 via buildroot [this message]
2022-01-22 13:53 ` [Buildroot] package/vte: install to staging Thomas Petazzoni
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=20220117114419.B8EAB3F465@exit1-us.msgsafe.io \
--to=buildroot@buildroot.org \
--cc=rainbox2k12@msgsafe.io \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.