ignore the pop up screen and provide options in a script

[iamagui]

hi

is it possible to ignore the pop up screen and provide the options in a script to automate the build process, thanks in advance.

[Rubberman]

Huh? What popup screen? What are you trying to build?

[iamagui]

When you 'make menuconfig' under ~/src/snapgear, the sreen pops up, refer attachment. We are using 'make menuconfig' in the build script as oldconfig is broken in our setup. So we want to ingore this screen and provide the selection in a script so that we can run the build script without manual inputs. Let me know if i am not clear and need more info, thanks.

[Rubberman]

Ah, the "friendly" configuration tool. I thought it had an optional command line interface. So, "make configure" doesn't work for you? You could go into scripts/kconfig and edit the mconf source file to take an optional input file argument so could it take its input from that file. You would also have to alter the Makefile in scripts/kconfig to call mconf with your file name if you implement an environment variable that tells it what to do, that would work both ways. Change the mconf call in the make file to use the variable as an argument, such as:

configure:
mconf $(MCONF_INPUT)

if MCONF_INPUT wasn't defined, then it works like now. If you set that environment variable (export MCONF_INPUT=myconf.txt), then it gets passed to mconf, which you can alter so that if there is an input file name passed, that is processed manually instead of calling the "user-friendly" menu.

[iamagui]

Thanks Rubberman, I will try your recommendation.

fyi...I was able to fix the oldconfig by adding

@chmod u+x config/setconfig
@config/setconfig defaults

to the oldconfig's command in the Makefile

and adding

cp .tmpconfig.h autoconf.h

in the build script.

[Rubberman]

I hope that works for you. Let us know.

[iamagui]

Mine worked. Yet to try yours. Thanks for your time and advise.

[Rubberman]

Mine worked. Yet to try yours. Thanks for your time and advise.

Glad you got thru the knothole. You way is probably more efficient than mine, and less error-prone. I'm just learning how to do kernel-level stuff with Linux.