From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: mchehab@s-opensource.com, hverkuil@xs4all.nl
Subject: [v4l-utils PATCH 1/2] Add instructions for building static binaries
Date: Thu, 5 Apr 2018 13:00:39 +0300 [thread overview]
Message-ID: <1522922440-8622-2-git-send-email-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <1522922440-8622-1-git-send-email-sakari.ailus@linux.intel.com>
Static binaries are useful e.g. when copying test binaries to other
systems. Document how to build them.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
INSTALL | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/INSTALL b/INSTALL
index 765fa26..8c98a76 100644
--- a/INSTALL
+++ b/INSTALL
@@ -53,6 +53,22 @@ export PKG_CONFIG_LIBDIR=/path/to/cross/root/lib
./configure --host=arm-linux-gnueabihf --without-jpeg
make
+Building static binaries:
+-------------------------
+
+Fully static binares can be built by setting LDFLAGS for the configure and
+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.
+
+In order to build binaries that are not dependent on libraries contained
+in v4l-utils, simply use the --disable-shared option:
+
+ $ ./configure --disable-shared
+
Android Cross Compiling and Installing:
----------------
--
2.7.4
next prev parent reply other threads:[~2018-04-05 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 10:00 [v4l-utils PATCH 0/2] v4l-utils fixes Sakari Ailus
2018-04-05 10:00 ` Sakari Ailus [this message]
2018-04-05 10:00 ` [v4l-utils PATCH 2/2] libdvb5: Fix unused local variable warnings Sakari Ailus
2018-04-05 10:18 ` [v4l-utils PATCH 0/2] v4l-utils fixes Mauro Carvalho Chehab
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=1522922440-8622-2-git-send-email-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.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