i note that the current incarnation of kbuild is amazingly forgiving
in terms of defining dependencies -- any one of "depends on" or
"depends" or "requires" is acceptable based on
scripts/kconfig/zconf.y:
...
depends: T_DEPENDS T_ON expr T_EOL
{
menu_add_dep($3);
printd(DEBUG_PARSE, "%s:%d:depends on\n", zconf_curname(),
zconf_lineno());
}
| T_DEPENDS expr T_EOL
{
menu_add_dep($2);
printd(DEBUG_PARSE, "%s:%d:depends\n", zconf_curname(),
zconf_lineno());
}
| T_REQUIRES expr T_EOL
{
menu_add_dep($2);
printd(DEBUG_PARSE, "%s:%d:requires\n", zconf_curname(),
zconf_lineno());
};
...
OTOH, Documentation/kconfig-language.txt says merely:
- dependencies: "depends on"/"requires" <expr>
This defines a dependency for this menu entry ...
no mention of just "depends", although there are several Kconfig files
that use that shorter form (eg., drivers/leds/Kconfig). why not just
pick one or the other and go with that?
and regarding "requires", AFAICT, there is not a single Kconfig file
that uses that form. why not just toss it?
rday
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
kbuild-devel mailing list
kbuild-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
