Sam, All,
Well, while I was fighting on this on my side... ;-)
On 2013-07-17 23:16 +0200, Sam Ravnborg spake thusly:
> > We could extend the symbol option part to retreive values from a binary.
> > Something like this:
> >
> > config FOOBAR
> > bool
> > option exec="true"
> >
> > FOOBAR would assume the value "y" if the command true has exit code == 0, otherwise "n".
> > And similar conversions for other types.
> >
> > This only extendt Kconfig slightly - using an already present method to import
> > external values.
> >
> > The drawback I see with this approach is that we may execute a lot of small programs
> > where the value is never used.
>
> Following is a quick patch implmenting this idea.
> You need to run gperf manually to enable this.
>
> "gperf -C scripts/kconfig/zconf.gperf > scripts/kconfig/zconf.hash.c"
>
> I did not figure out how to use the built-in rules to generate this file :-(
make REGENERATE_PARSERS=y menuconfig
> I have tested this lightly - as we should discuss if this is a viable way forward.
Instead of extending the Kconfig language, I was thinking (as initially
suggested by Andrew) of generating a Kconfig file before all config
targets, and source that Kconfig file from $(TOPDIR)/Kconfig.
I'm not a fan od extending the Kconfig language in this way. It feels
weird to me. Especially when we have a way to solve this specific issue
with a script that generates the needed Kconfig symbols before any
config target is called.
At the very least we'd have to decide if this is available only for
booleans/tristates, or for any type? Your implementation seems to make
it valid for strings/ints, too.
> For now I used popen() - so return value of the executed program are ignored.
Yet, pclose returns the exit status of the command.
If option exec was to be valid only for booleans, we could use the exit
value rather than the output, which would seem more logical. It would be
however a bit moretriclky for tristates, though...
Maybe using output is the best, after all...
So, how do you expect we use that to check for an external tool?
Something like this?
config HAVE_LZ4
bool
option exec="which lz4c >/dev/null 2>&1 && echo y"
config KERNEL_LZ4
bool "compress the kernel with lz4"
depends on HAVE_LZ4
Ot did I miss something?
> diff --git a/scripts/kconfig/symbol.c b/scripts/kconfig/symbol.c
> index d550300..b7179a6 100644
> --- a/scripts/kconfig/symbol.c
> +++ b/scripts/kconfig/symbol.c
[--SNIP--]
> @@ -1379,3 +1381,56 @@ static void prop_add_env(const char *env)
> else
> menu_warn(current_entry, "environment variable %s undefined", env);
> }
> +
> +static void exec_command(const char *command, struct symbol *sym)
> +{
> + char buffer[2048];
> + FILE *stream;
> +
> + stream = popen(command, "r");
> +
> + if (stream != NULL) {
> + if (fgets(buffer, sizeof(buffer), stream) != NULL) {
> + int i;
> +
> + buffer[sizeof(buffer) - 1] = '\0';
> +
> + /* Drop any trialing newlines */
> + i = strlen(buffer);
> + while (i > 0 && buffer[i - 1] == '\n') {
> + buffer[i - 1] = '\0';
> + i--;
> + }
> + /* Validate the output of the command */
> + if (strlen(buffer) == 0) {
> + menu_warn(current_entry,
> + "command '%s' - invalid (empty?) return value: \"%s\"",
> + command, buffer);
> + return;
Missing pclose() before return.
[--SNIP--]
I'll give it a spin here. Thank you!
BTW, I still need your help on solving that one:
randconfig does randomise choice entries, unless KCONFIG_ALLCONFIG
is specified.
http://marc.info/?l=linux-kernel&m=137209757414433&w=2
My two previous attempts failed due to introducing regressions, so they
were both reverted... :-(
Any suggestion? ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
