How to add a dependency on start.o to the test executables in waf?
sebastian.huber at embedded-brains.de
Fri Oct 25 05:38:53 UTC 2019
On 25/10/2019 07:33, Chris Johns wrote:
> On 25/10/19 4:26 pm, Sebastian Huber wrote:
>> On 25/10/2019 07:18, Sebastian Huber wrote:
>>>>> How can I add a dependency on start.o to the test executables? I tried several
>>>>> variants of bld.add_manual_dependency(), but nothing worked.
>>>> I am not sure, I would need to have a close look at how the test stuff is being
>>>> put together. I cannot see where start.o in the bld statement.
>>>> Is start.o treated in a special way, maybe hidden when linking in the linker
>>> The start.o is a start file and not a normal object. It is added either
>>> through the GCC specs or the linker command file STARTUP() directive.
>> The dependency tracking for start.o is a nice to have feature. The current build
>> system also lacks support for it.
> Then I would leave a comment and move on. Getting it perfect first time leaves
> us with nothing to do ;) ;)
Yes, this sounds like a good approach.
I will work on the following features next week:
* Add configure check to get the size of a type. My attempt to add
standard checks to waf was not really successful:
So, this must be added to the wscript.
* Add ability to install files.
* Add attributes to validate integer options read from the *.ini files,
e.g. min, max, power-of-two, custom validator in Python code, etc.
Before I start with the boring work to convert all tests and BSPs, I
would like to get the UID name support integrated in Doorstop:
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the devel