[U-Boot] ENV_IS_EMBEDDED vs CONFIG_ENV_IS_EMBEDDED

[Wolfgang Denk]

Dear Mike Frysinger,

In message <200907102250.57311.vapier at gentoo.org> you wrote:
>
> > Yes. It's IMHO silly to have to configure something manually (and
> > keep it in sync with potential changes of some other defines) when it
> > is as well possible to have that same value computed automatically at
> > build time.
>
> so i should convert ENV_IS_EMBEDDED to CONFIG_ENV_IS_EMBEDDED or i should add 
> to common code logic to force CONFIG_ENV_IS_EMBEDDED when ENV_IS_EMBEDDED is 
> defined by the board ?

If   it's   possible,    generating    CONFIG_ENV_IS_EMBEDDED    when
ENV_IS_EMBEDDED  is  defined  would  be  much  better  -  however, my
understanding is that CONFIG_ENV_IS_EMBEDDED is needed  by  the  make
proces,,i.   e.   before   actually   running   any  commands,  while
ENV_IS_EMBEDDED gets computed by the C preprocessor, i. e.  too  late
for  make  decisions  (unless you copy the part of code that computes
ENV_IS_EMBEDDED into some special script / file and  run  it  through
the  C preprocessor - which is not exactly a leaner design either, it
seems).

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: wd at denx.de
Cigarette, n.: A fire at one end, a fool at the other, and a  bit  of
tobacco in between.