From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: rajmohan.mani@intel.com, yong.zhi@intel.com, hverkuil@xs4all.nl
Subject: [v4l-utils PATCH 1/4] Update static build instructions
Date: Mon, 14 Jan 2019 16:13:05 +0200 [thread overview]
Message-ID: <20190114141308.29329-2-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <20190114141308.29329-1-sakari.ailus@linux.intel.com>
It appears that the required libraries may depend on whether linking is
done statically or dynamically. The pkg-config thus needs to know. Update
the instructions accordingly.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
INSTALL | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/INSTALL b/INSTALL
index d55f56cd9f..b7546aa61e 100644
--- a/INSTALL
+++ b/INSTALL
@@ -62,12 +62,10 @@ using an option for disabling shared libraries:
$ LDFLAGS="--static -static" ./configure --disable-shared
Note that this requires static variants of all the libraries needed for
-linking which may not be available in all systems.
+linking which may not be available in all systems. Then run the configure
+script as follows:
-In order to build binaries that are not dependent on libraries contained
-in v4l-utils, simply use the --disable-shared option:
-
- $ ./configure --disable-shared
+ $ PKG_CONFIG="pkg-config --static" ./configure --disable-shared
Android Cross Compiling and Installing:
----------------
--
2.11.0
next prev parent reply other threads:[~2019-01-14 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 14:13 [v4l-utils PATCH 0/4] Metadata output support for v4l2-ctl Sakari Ailus
2019-01-14 14:13 ` Sakari Ailus [this message]
2019-01-14 14:13 ` [v4l-utils PATCH 2/4] Sync the latest headers Sakari Ailus
2019-01-14 14:13 ` [v4l-utils PATCH 3/4] v4l2-ctl: Print metadata capture formats on --all Sakari Ailus
2019-01-14 14:13 ` [v4l-utils PATCH 4/4] v4l2-ctl: Add support for META_OUTPUT buffer type Sakari Ailus
2019-01-22 8:19 ` Hans Verkuil
2019-01-22 9:47 ` Sakari Ailus
2019-01-22 10:21 ` Hans Verkuil
2019-01-22 12:31 ` Sakari Ailus
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=20190114141308.29329-2-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=rajmohan.mani@intel.com \
--cc=yong.zhi@intel.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 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.