Dear Mike Frysinger, In message <[email protected]> you wrote: > The env code is protected by the ENV_IS_EMBEDDED define, so attempting to > compile the code when this isn't defined is pointless. Now that the env > headers have unified around CONFIG_ENV_IS_EMBEDDED, convert the build > system to only build the env objects when this is enabled. And now that > the env code is conditionally compiled, we can drop the source code checks. > > For people who want to extract the environment manually, add a new option > that only enables the envcrc utility (CONFIG_ENV_IS_EMBEDDED_CUSTOM).
I see no users, and I hesitate to add dead code. And CONFIG_ENV_IS_EMBEDDED_CUSTOM is an ugly and misleading name. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected] All a hacker needs is a tight PUSHJ, a loose pair of UUOs, and a warm place to shift. _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
