From: Mike Frysinger Date: Thu, 11 Feb 2010 05:20:54 -0500 Subject: [U-Boot] [RFC] regenerating u-boot.lds Message-ID: <201002110520.54552.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de the current u-boot.lds target in u-boot depends only on the source file (typically a u-boot.lds.S). this works fine if someone changes the u- boot.lds.S file -- it'll force a regeneration. however, if the u-boot.lds.S file includes u-boot headers such as board config options via config.h, there is no dependency expressed which will cause the file to be regenerated. looking through the build system, i'm not sure there is a way to easily express this. considering the u-boot.lds is trivial to generate (it only gets preprocessed), and every `make` forces a relink of the final u-boot binary, i wonder if we should just label the top level u-boot.lds as phony ? +.PHONY: $(obj)u-boot.lds -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20100211/348e88e6/attachment.pgp