From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 17 Jun 2019 21:02:23 +0200 Subject: [Buildroot] [External] Re: [PATCH v2 1/1] package/hostapd: add debug information options In-Reply-To: References: <20190617153533.26255-1-jared.bents@rockwellcollins.com> <20190617194121.64c14291@windsurf> Message-ID: <20190617210223.77a97ee2@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Mon, 17 Jun 2019 12:56:08 -0500 Jared Bents wrote: > > Could you explain what CONFIG_DEBUG_FILE is doing compared to > > CONFIG_DEBUG_SYSLOG, and why one is conditional and not the other ? Do > > we really want CONFIG_DEBUG_FILE unconditionally ? > > I based it off of wpa_supplicant's implementation for each. In > wpa_supplicant, CONFIG_DEBUG_FILE is turned on unconditionally while > CONFIG_DEBUG_SYSLOG is optional. CONFIG_DEBUG_FILE enables a runtime > option (-f) to specify a file to direct the hostapd output to instead > of stdout. CONFIG_DEBUG_SYSLOG enables a runtime option (-s) to have > the output go to syslog instead of stdout. These are purely optional > at runtime as if neither of the -f or -s command line arguments are > used, the output will go to stdout as before. What is the size impact of each option, compared to the overall installation size of hostapd ? Thomas -- Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com