Hello Simon,
On 04-08-14 12:09, Simon Glass wrote:
Hi Jeroen,
On 1 August 2014 13:28, Jeroen Hofstee <jer...@myspectrum.nl> wrote:
The switch to KConfig break the [board]_config target. This breaks
backwards compatibility and hence all documentation about how to
build u-boot is no longer valid. It is also annoying for general
recipes to build u-boot as contained in buildroot, crochet, oe,
poky, eldk etc. Hence restore the *_config target.
cc: Tom Rini <tr...@ti.com>
cc: Masahiro Yamada <yamad...@jp.panasonic.com>
cc: Simon Glass <s...@chromium.org>
Signed-off-by: Jeroen Hofstee <jer...@myspectrum.nl>
Is there any way we can emit a deprecation warning without breaking these tools?
I guess the number of ways to do that are just limited by our imagination:
- abusing the bell character can be quite annoying, but is broken /
fixed in the
linux distro's I know.
- echo "Hi there, U-boot folks over here, please STOP using _config, use
_defconfig instead!" | write $USER
will scare quite a few users I guess.
- sendmail + git config user.email of the OE tree should be annoying enough
- lpr ;)
- play ?
- figure out which oe recipe invoked it and patch it from u-boot ;)
And as a serious answer, no I don't know a decent method
to do it. As far as I know OE e.g. just logs to a file and only
displays its contents if an error occurred.
Afaiac, the target is just kept. Just to prevent wasting time
updating all wikis, docs etc, recipe etc. (it is not that it is a
big pile of code or something). I can add an echo of course,
but it won't be noticed by such build tools.
Regards,
Jeroen
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
