On Mon, Aug 12, 2019 at 10:14 AM Mark Brown <broonie@xxxxxxxxxx> wrote: > > On Tue, Aug 13, 2019 at 01:37:14AM +0900, Masahiro Yamada wrote: > > Only the problem I see is the situation where > > a user directly runs scripts/kconfig/merge_config.sh > > without using make as a start-point. Further, if it's possible to detect if merge_config.sh was invoked from Make or not, it might be useful to warn or error when not invoked via Make. > > This is really a very common thing for testing infrastructure to do, > it'll combine a base defconfig with a fragment enabling extra stuff > either to directly cover that extra stuff or to ensure that > configuration options needed for testsuites get turned on. > > > A user can wrap merge_config.sh with a simple Makefile > > if they want to override CC, HOSTCC, etc. > > If we want to do that it seems sensible to provide that Makefile > upstream so there's a standard thing, it might also help people notice > that they need to do this and avoid getting surprised. -- Thanks, ~Nick Desaulniers
