On Tue, 25 Jun 2024, Hal Murray via devel wrote:
$ grep rtems wscript */wscript wafhelpers/*
wscript: if ctx.options.enable_rtems_trace:
wscript: ctx.find_program("rtems-tld", var="BIN_RTEMS_TLD",
wscript: path_list=[ctx.options.rtems_trace_path,
wscript:# Borrowed from https://www.rtems.org/
wscript: ctx.load('rtems_trace', tooldir='wafhelpers/')
ntpd/wscript: features="c rtems_trace cprogram",
wafhelpers/options.py: grp.add_option('--enable-rtems-trace',
action='store_true',
wafhelpers/options.py: grp.add_option('--rtems-trace-path',
type='string', default="",
wafhelpers/options.py: help="Path to rtems-tld.")
wafhelpers/rtems_trace.py:@feature("rtems_trace")
wafhelpers/rtems_trace.py:def rtems_trace(self):
$
What does it do?
Is it likely to be useful or should we dump it?
Most of the git history just relates to moving options around, but there's
this:
commit dd880e86dbdb55926e99b6fc05e8e811f3d8e861
Author: Amar Takhar <v...@darkbeer.org>
Date: Tue Dec 8 20:17:25 2015 -0500
Add support for RTEMS trace.
This doesn't work yet. Chris will help me iron out the issues.
[...]
Fred Wright
_______________________________________________
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
