Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] wpa_supplicant: rework .config file editing
Date: Fri, 28 Sep 2012 00:44:26 +0200	[thread overview]
Message-ID: <5064D6CA.7030602@mind.be> (raw)
In-Reply-To: <1348755331-22000-3-git-send-email-s.neumann@raumfeld.com>

On 27/09/12 16:15, Sven Neumann wrote:
> Do all substitutions on the .config file in a single sed command.
> Make the .config file editing a lot more readable. Based on ideas
> brought up by Arnout Vandecappelle on the mailing-list.
>
> Signed-off-by: Sven Neumann<s.neumann@raumfeld.com>
[snip]
>  # Try to use openssl or gnutls if it's already available
>  ifeq ($(BR2_PACKAGE_OPENSSL),y)
>  	WPA_SUPPLICANT_DEPENDENCIES += openssl
> -define WPA_SUPPLICANT_TLS_CONFIG
> -	$(SED) 's/\(#\)\(CONFIG_TLS=openssl\)/\2/' $(WPA_SUPPLICANT_CONFIG)
> -	$(SED) 's/\(#\)\(CONFIG_EAP_PWD.*\)/\2/' $(WPA_SUPPLICANT_CONFIG)
> -endef
> +	WPA_SUPPLICANT_CONFIG_EDITS += 's/\#\(CONFIG_TLS=openssl\)/\1/'

  The \ in front of # is a leftover from \(.  Same below.

> +	WPA_SUPPLICANT_CONFIG_ENABLE += CONFIG_EAP_PWD
>   else
>   ifeq ($(BR2_PACKAGE_GNUTLS),y)
>   	WPA_SUPPLICANT_DEPENDENCIES += gnutls
> -define WPA_SUPPLICANT_TLS_CONFIG
> -	$(SED) 's/\(#\)\(CONFIG_TLS=\).*/\2gnutls/' $(WPA_SUPPLICANT_CONFIG)
> -endef
> +	WPA_SUPPLICANT_CONFIG_EDITS += 's/\#\(CONFIG_TLS=\).*/\1gnutls/'
>   else
> -define WPA_SUPPLICANT_TLS_CONFIG
> -	$(SED) 's/\(#\)\(CONFIG_TLS=\).*/\2internal/' $(WPA_SUPPLICANT_CONFIG)
> -endef
> +	WPA_SUPPLICANT_CONFIG_EDITS += 's/\#\(CONFIG_TLS=\).*/\1internal/'
>   endif
>   endif
>
> @@ -87,9 +80,7 @@ ifeq ($(BR2_PACKAGE_DBUS),y)
>   		PKG_CONFIG_PATH="$(STAGING_DIR)/usr/lib/pkgconfig"
>
>   ifeq ($(BR2_PACKAGE_WPA_SUPPLICANT_DBUS_OLD),y)
> -define WPA_SUPPLICANT_DBUS_OLD_CONFIG
> -	$(SED) 's/\(#\)\(CONFIG_CTRL_IFACE_DBUS=\)/\2/' $(WPA_SUPPLICANT_CONFIG)
> -endef
> +	WPA_SUPPLICANT_CONFIG_ENABLE += CONFIG_CTRL_IFACE_DBUS=

  Why the trailing = ?



  Have you tested a few variations of the config?  Especially the TLS options...

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-09-27 22:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 12:55 [Buildroot] wpa_supplicant changes, the next round Sven Neumann
2012-09-25 12:55 ` [Buildroot] [PATCH 1/4] wpa-supplicant: add options to enable the new DBus interface Sven Neumann
2012-09-25 12:55 ` [Buildroot] [PATCH 2/4] wpa_supplicant: remove redundant escaping from sed commands Sven Neumann
2012-09-25 12:55 ` [Buildroot] [PATCH 3/4] wpa_supplicant: introduce macros for editing the .config file Sven Neumann
2012-09-25 12:55 ` [Buildroot] [PATCH 4/4] wpa-supplicant: rework .config file editing Sven Neumann
2012-09-25 21:56   ` Arnout Vandecappelle
2012-09-27 14:15     ` [Buildroot] wpa_supplicant changes Sven Neumann
2012-09-27 14:15       ` [Buildroot] [PATCH 1/2] wpa-supplicant: add options to enable the new DBus interface Sven Neumann
2012-09-27 14:15       ` [Buildroot] [PATCH 2/2] wpa_supplicant: rework .config file editing Sven Neumann
2012-09-27 22:44         ` Arnout Vandecappelle [this message]
2012-09-28  7:05           ` Sven Neumann

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=5064D6CA.7030602@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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