* [U-Boot] how are "CONFIG_*" variables processed by Makefiles?
@ 2012-11-14 15:35 Robert P. J. Day
2012-11-14 15:58 ` Benoît Thébaudeau
0 siblings, 1 reply; 3+ messages in thread
From: Robert P. J. Day @ 2012-11-14 15:35 UTC (permalink / raw)
To: u-boot
i'm sure there's a trivial explanation for this that i'm missing but
i'm looking at this snippet from arch/arm/cpu/armv7/omap3/Makefile:
... snip ...
COBJS += board.o
COBJS += clock.o
COBJS += mem.o
COBJS += sys_info.o
ifdef CONFIG_SPL_BUILD
COBJS-$(CONFIG_SPL_OMAP3_ID_NAND) += spl_id_nand.o
endif
COBJS-$(CONFIG_DRIVER_TI_EMAC) += emac.o
COBJS-$(CONFIG_EMIF4) += emif4.o
COBJS-$(CONFIG_SDRC) += sdrc.o <--- this line, eg.
SRCS := $(SOBJS:.o=.S) $(COBJS:.o=.c)
OBJS := $(addprefix $(obj),$(COBJS) $(COBJS-y) $(SOBJS))
... snip ...
how does the fact that the beagle that i'm building for, which
defines:
include/configs/omap3_beagle.h:#define CONFIG_SDRC
translate that simple #define into a value that can be used by the
Makefile to select sdrc.o to be compiled?
i'm used to the linux kernel config process which explicitly sets
the variables to the string "y", so that, in the above, the variable
$(COBJS-y) would pick up those conditional compilations.
but what is happening here? i'm sure it's simple, i just don't see
where it's happening in the config and build process. thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 3+ messages in thread* [U-Boot] how are "CONFIG_*" variables processed by Makefiles?
2012-11-14 15:35 [U-Boot] how are "CONFIG_*" variables processed by Makefiles? Robert P. J. Day
@ 2012-11-14 15:58 ` Benoît Thébaudeau
2012-11-14 15:55 ` Robert P. J. Day
0 siblings, 1 reply; 3+ messages in thread
From: Benoît Thébaudeau @ 2012-11-14 15:58 UTC (permalink / raw)
To: u-boot
Dear Robert P. J. Day,
On Wednesday, November 14, 2012 4:35:15 PM, Robert P. J. Day wrote:
> i'm sure there's a trivial explanation for this that i'm missing
> but
> i'm looking at this snippet from arch/arm/cpu/armv7/omap3/Makefile:
>
> ... snip ...
> COBJS += board.o
> COBJS += clock.o
> COBJS += mem.o
> COBJS += sys_info.o
> ifdef CONFIG_SPL_BUILD
> COBJS-$(CONFIG_SPL_OMAP3_ID_NAND) += spl_id_nand.o
> endif
>
> COBJS-$(CONFIG_DRIVER_TI_EMAC) += emac.o
> COBJS-$(CONFIG_EMIF4) += emif4.o
> COBJS-$(CONFIG_SDRC) += sdrc.o <--- this line, eg.
>
> SRCS := $(SOBJS:.o=.S) $(COBJS:.o=.c)
> OBJS := $(addprefix $(obj),$(COBJS) $(COBJS-y) $(SOBJS))
> ... snip ...
>
> how does the fact that the beagle that i'm building for, which
> defines:
>
> include/configs/omap3_beagle.h:#define CONFIG_SDRC
>
> translate that simple #define into a value that can be used by the
> Makefile to select sdrc.o to be compiled?
>
> i'm used to the linux kernel config process which explicitly sets
> the variables to the string "y", so that, in the above, the variable
> $(COBJS-y) would pick up those conditional compilations.
>
> but what is happening here? i'm sure it's simple, i just don't see
> where it's happening in the config and build process. thanks.
Take a look at the following rule in the main Makefile:
$(obj)include/autoconf.mk: $(obj)include/config.h
Best regards,
Beno?t
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-11-14 15:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-14 15:35 [U-Boot] how are "CONFIG_*" variables processed by Makefiles? Robert P. J. Day
2012-11-14 15:58 ` Benoît Thébaudeau
2012-11-14 15:55 ` Robert P. J. Day
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.