From: Steven Zedeck <saz@proliphix.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot makefiles question
Date: Fri, 27 Mar 2009 05:35:19 -0700 (PDT) [thread overview]
Message-ID: <22740727.post@talk.nabble.com> (raw)
Hi,
I have a general question about the U-Boot Makefiles. When I want to add a
file to one of the sub-Makefiles (such as in drivers/net/Makefile or
board/atmel/at91xxxx/Makefile), it seems I need to go through several steps
in order for the new file to get compiled. I must be doing something wrong.
I've been doing this everytime I add a new file to be compiled by a
makefile:
make distclean
make at91sam9rlek_config
make at91sam9rlek_config
make clean
make -B
It seems that if I don't do all those steps, the new file is ignored and not
compiled. I think its an issue with dependencies.
I have a similar problem when I add a new .h file to an existing .c file. It
doesn't always cause the particular .c file to get recompiled.
thanks in advance,
Steve
--
View this message in context: http://www.nabble.com/U-Boot-makefiles-question-tp22740727p22740727.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
reply other threads:[~2009-03-27 12:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=22740727.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