From: Jean Delvare <jdelvare-l3A5Bk7waGM@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC] i2c-tools: allow linker and compile flags from command line
Date: Tue, 7 Jul 2015 21:08:28 +0200 [thread overview]
Message-ID: <20150707210828.0e5caf05@endymion.delvare> (raw)
In-Reply-To: <1434705872-2866-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Hi Wolfram,
On Fri, 19 Jun 2015 11:24:32 +0200, Wolfram Sang wrote:
> Mainly for debugging, so one can pass stuff like -O0 or -static.
>
> Signed-off-by: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
> ---
> tools/Module.mk | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/Module.mk b/tools/Module.mk
> index 8efddbb..641ac81 100644
> --- a/tools/Module.mk
> +++ b/tools/Module.mk
> @@ -9,13 +9,13 @@
>
> TOOLS_DIR := tools
>
> -TOOLS_CFLAGS := -Wstrict-prototypes -Wshadow -Wpointer-arith -Wcast-qual \
> +TOOLS_CFLAGS += -Wstrict-prototypes -Wshadow -Wpointer-arith -Wcast-qual \
> -Wcast-align -Wwrite-strings -Wnested-externs -Winline \
> -W -Wundef -Wmissing-prototypes -Iinclude
> ifeq ($(USE_STATIC_LIB),1)
> -TOOLS_LDFLAGS := $(LIB_DIR)/$(LIB_STLIBNAME)
> +TOOLS_LDFLAGS += $(LIB_DIR)/$(LIB_STLIBNAME)
> else
> -TOOLS_LDFLAGS := -Llib -li2c
> +TOOLS_LDFLAGS += -Llib -li2c
Note that -Llib has become -L$(LIB_DIR) meanwhile.
> endif
>
> TOOLS_TARGETS := i2cdetect i2cdump i2cset i2cget
You can already overwrite CFLAGS and LDFLAGS on the command line, and
this works for the whole package. Do you really need to set different
CFLAGS (or LDFLAGS) for different parts of i2c-tools? Seems overkill to
me.
If you really need that then this should be done consistently for all
"modules": not just tools but also lib and now eeprog.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2015-07-07 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 9:24 [RFC] i2c-tools: allow linker and compile flags from command line Wolfram Sang
[not found] ` <1434705872-2866-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-07-07 19:08 ` Jean Delvare [this message]
[not found] ` <20150707210828.0e5caf05-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2015-07-09 16:50 ` Wolfram Sang
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=20150707210828.0e5caf05@endymion.delvare \
--to=jdelvare-l3a5bk7wagm@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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).