Makefile: don't run "menuconfig" automatically
authorArnout Vandecappelle <arnout@mind.be>
Sat, 1 Jul 2017 08:24:46 +0000 (10:24 +0200)
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Sat, 1 Jul 2017 08:26:06 +0000 (10:26 +0200)
commitc3493069f28368739a7ccf670bd2eecbb2524d96
treebecf2bf07c1a90f09bcf57efb9d2f1cb6abb351e
parente79c574a9e17cd742fc4020545de9e33d8fdef38
Makefile: don't run "menuconfig" automatically

Since forever, we run 'menuconfig' automatically on an unconfigured
tree. However, this does not help users that much:
- If they read the documentation, they should already know to run
  make menuconfig first.
- If they haven't read the documentation, dropping them in menuconfig
  isn't very helpful.
- It's a likely that the user didn't intend to be in an unconfigured
  tree (e.g. wrong O= specified), so starting menuconfig (and polluting
  this wrong O= directory) is not very helpful.
- It's possible that the user really doesn't want menuconfig, but
  instead needs xconfig, or some defconfig, or ...

So, instead of trying to guess what the user needs, print an error and
let the user decide what to do next.

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Makefile