From: Angelo Compagnucci <angelo@amarulasolutions.com>
To: linux-i2c@vger.kernel.org
Cc: jdelvare@suse.de, Angelo Compagnucci <angelo@amarulasolutions.com>
Subject: [PATCH 2/2] i2c-tools: README: adding documentation for BUILD_DYNAMIC_LIB
Date: Wed, 6 Dec 2017 11:45:57 +0100 [thread overview]
Message-ID: <1512557157-17467-2-git-send-email-angelo@amarulasolutions.com> (raw)
In-Reply-To: <1512557157-17467-1-git-send-email-angelo@amarulasolutions.com>
This patch adds the documentation for the newly introduced
BUILD_DYNAMIC_LIB flag and clarify the use of the other
variables USE_STATIC_LIB and BUILD_STATIC_LIB.
Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
---
README | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/README b/README
index 4ccdf5b..d127f25 100644
--- a/README
+++ b/README
@@ -66,6 +66,15 @@ setting prefix to wherever you want. You may change the C compiler and the
compilation flags as well, and also decide whether to build the static
library or not.
+In cases where you need to compile only the static or dynamic variant of
+the library, you can use BUILD_STATIC_LIB and BUILD_DYNAMIC_LIB at compile time:
+ $ make BUILD_DYNAMIC_LIB=1 BUILD_STATIC_LIB=0
+If you disable both, the compilation will abort with an error message.
+
+If you want to compile against the static version of the library
+you can do:
+ $ make USE_STATIC_LIB=1
+
Optionally, you can run "make strip" prior to "make install" if you want
smaller binaries. However, be aware that this will prevent any further
attempt to debug the library and tools.
--
2.7.4
prev parent reply other threads:[~2017-12-06 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 10:45 [PATCH 1/2] i2c-tools: Makefile: add flag to disable dynamic libraries Angelo Compagnucci
2017-12-06 10:45 ` Angelo Compagnucci [this message]
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=1512557157-17467-2-git-send-email-angelo@amarulasolutions.com \
--to=angelo@amarulasolutions.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).