From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: wireless <linux-wireless@vger.kernel.org>
Subject: Minimal cross-compilation fix for CRDA
Date: Wed, 12 Aug 2009 18:45:38 -0700 [thread overview]
Message-ID: <4A837042.4000507@redfish-solutions.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
Reposting.
I think I've addresses all of the comments, and this fix is as short as
possible.
I considered passing in all of the variables from outside, but (a) this
doesn't scale well, and (b) things like $(NLLIBNAME) are "scratch"
variables used by the make process when doing discovery about the host
it's running on... they shouldn't be externally visible, much less
overridden by some encompassing make.
Putting the auto-discovery into its own path with a gating variable
seems like the cleanest, most robust, most maintainable approach.
[-- Attachment #2: crda-cross-compile.patch --]
[-- Type: text/plain, Size: 1543 bytes --]
Changes:
1. Move invariant definitions to before any cross-compilation conditional sections for clarity (and to avoid having to duplicate them).
2. Bracket any host (native) compilation sections with conditional based on $(CROSS_COMPILE) being empty.
4. Add 'else' section for cross-compilation using openssl and libnl-1 (or libnl-2 if explicitly selected).
--- crda-1.1.0/Makefile 2009-08-10 13:37:36.000000000 -0700
+++ crda-1.1.0/Makefile.new 2009-08-10 17:29:22.000000000 -0700
@@ -22,12 +22,17 @@
# with make PUBKEY_DIR=/usr/lib/crda/pubkeys
PUBKEY_DIR?=pubkeys
+MKDIR ?= mkdir -p
+INSTALL ?= install
+
CFLAGS += -Wall -g
all: all_noverify verify
all_noverify: crda intersect regdbdump
+ifeq ($(CROSS_COMPILE),)
+
ifeq ($(USE_OPENSSL),1)
CFLAGS += -DUSE_OPENSSL `pkg-config --cflags openssl`
LDLIBS += `pkg-config --libs openssl`
@@ -41,8 +46,6 @@
reglib.o: keys-gcrypt.c
endif
-MKDIR ?= mkdir -p
-INSTALL ?= install
NL1FOUND := $(shell pkg-config --atleast-version=1 libnl-1 && echo Y)
NL2FOUND := $(shell pkg-config --atleast-version=2 libnl-2.0 && echo Y)
@@ -64,6 +67,31 @@
NLLIBS += `pkg-config --libs $(NLLIBNAME)`
CFLAGS += `pkg-config --cflags $(NLLIBNAME)`
+else
+
+ifeq ($(USE_OPENSSL),1)
+CFLAGS += -DUSE_OPENSSL
+LDLIBS += -lssl
+
+reglib.o: keys-ssl.c
+
+else
+CFLAGS += -DUSE_GCRYPT
+LDLIBS += -lgcrypt
+
+reglib.o: keys-gcrypt.c
+
+endif
+
+ifeq ($(USE_LIBNL20),1)
+CFLAGS += -DCONFIG_LIBNL20
+NLLIBS = -lnl-genl -lnl-2.0
+else
+NLLIBS = -lnl
+endif
+
+endif
+
ifeq ($(V),1)
Q=
NQ=@true
reply other threads:[~2009-08-13 1:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A837042.4000507@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=linux-wireless@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).