WAF build system: configure to prepend .o to all links?

Peter Dufault dufault at hda.com
Sun Jul 4 13:02:28 UTC 2021


I want to build the i.MX RT BSP with a custom DTS file.  It's easy to build an application using ones own "dts.o" file, but I want to build all the BSP tests with my dts.o.  For now I just change the one in the tree but I don't want to do that.  I don't want a BSP variant, either, since it's a custom board that shouldn't have changes in the tree.

I want to get my "dts.o" in the link commands before the "-lrtemsbsp".  I looked through what is in "config.ini" and don't see what I need.  I can't over-ride LDFLAGS since that is appended in the command line after the libraries were already added.  So I want to add a .o to the sources or a flag that goes in after the "-o" for the program output.

Is there a way to do that?  I even tried setting LINK_CC but though "waf configure" warned be it was set it didn't use it.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 235 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.rtems.org/pipermail/devel/attachments/20210704/780fcd9c/attachment.bin>


More information about the devel mailing list