Wow, what an assumption! Anyway, adding the correct machconfig for
my target fixes the problem.
As the author, I decided that the choice of keyboard or not by default is pretty much a coin toss, but I suspect the development boards are more likely to have a keyboard than a working touchscreen.