public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Steven Zedeck <saz@proliphix.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot Makefile question
Date: Tue, 17 Feb 2009 05:43:31 -0800 (PST)	[thread overview]
Message-ID: <22057574.post@talk.nabble.com> (raw)


Hi all,
I am new to u-boot. But I am ramping up pretty fast. My primary issue is
understanding the Makefile syntax. Is there a good tutorial somewhere that
explains how u-boot uses the Makefiles and their syntax?

For example, I'm having problems understanding what this means in a
Makefile:

COBJS-$(CONFIG_HAS_DATAFLASH) += at45.o
COBJS-$(CONFIG_FLASH_CFI_DRIVER) += cfi_flash.o
COBJS-$(CONFIG_HAS_DATAFLASH) += dataflash.o
COBJS-$(CONFIG_FLASH_CFI_LEGACY) += jedec_flash.o
COBJS-$(CONFIG_MW_EEPROM) += mw_eeprom.o

COBJS	:= $(COBJS-y)
SRCS	:= $(COBJS:.o=.c)
OBJS	:= $(addprefix $(obj),$(COBJS))

This is from drivers/mtd/Makefile.

How does COBJS get initially defined upon entry into the Makefile?

Does at45.o get added to the list of objects to be built only if the
CONFIG_HAS_DATAFLASH flag is set?

What does the "-" sign mean before the "$" ?

What does this mean?  COBJS	:= $(COBJS-y)

I'm sorry for the "dumb" questions. Any help with the understanding of
Makefiles would be greatly appreciated.

Thanks in advance,
Steve
-- 
View this message in context: http://www.nabble.com/U-Boot-Makefile-question-tp22057574p22057574.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

             reply	other threads:[~2009-02-17 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 13:43 Steven Zedeck [this message]
2009-02-17 15:03 ` [U-Boot] U-Boot Makefile question Michael Lawnick
2009-02-17 16:02 ` Mike Frysinger
2009-02-18  9:34 ` Frank Svendsbøe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22057574.post@talk.nabble.com \
    --to=saz@proliphix.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox