I have an OpenEmbedded environment using bitbake to do some builds. I wanted to get something \"interactive\" going on where bitbake would pause and ask for input then continue
While there is nothing wrong with the other answers bitbake does accept a --postread
argument as documented here. That means that you can write as many bitbake variables as you want to some temporary configuration file and have it read after bitbake.conf by specifying the name of the file on the command-line. For example:
bitbake --postread=./extra.conf
I personally find this more convenient than dealing with environment variables.