On 1 August 2013 12:18, Laszlo Papp <[email protected]> wrote: >> It cannot be more specific without dumping the entire machine >> configuration, which won't help because a variable is *not* set. > > No no, it could print out the concrete file to look up, not just a name. > Besides, I would probably even print a warning about the entry point and > load address not set.
This is a simple "can I even build?" check, and UBOOT_MACHINE is sufficient. Our users are not totally useless, I think they can find their own machine configuration files. >> By "machine configuration can be in the command line" do you mean >> MACHINE=foo? And if so, why does that mean the statement is vague? > > Well, you could place a warning for instance when it is set to the same as > in the config file. That is probably not what the user intended. I'm not sure what you meant here. Do you mean a situation where the local.conf says MACHINE=foo and the user also sets MACHINE=foo in the environment? Ross _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
