On Tue, Feb 07, 2017 at 03:37:47PM -0500, David G. Simmons wrote:
> Ok, now I'm very confused ...
>
> The newt tool is what is used to BUILD newt apps, etc. The newt-core
> stuff is what the apps are built out of. So what I'm getting here is
> that an out-of-date newt tool will build bad mynewt apps, even if all
> the parts that are used in the app are correct?
The newt tool generates some C code at build time, namely:
* syscfg.h (system configuration)
* <target>-sysflash.c (default flash map)
* <target>-sysinit-app.c (app system initialization sequence)
* <target>-sysinit-loader.c (loader system initialization sequence)
It is unfortunate that this dependency exists. There might be some
smart things that cna be done to replace some of the generated code in
the future.
> If that's correct, I think the newt tool desperately needs a
> 'self-update' command that will update newt itself, and possibly
> detect when newt is out of date, because ... well, having the software
> built by the tool be bad because the tool is out of date is no so good
> and will definitely confuse users sooner rather than later.
Yes, that would certainly be a useful feature. As an aside, newt does
perform the reverse check: it warns you if a mynewt repo is too old for
your version of newt. However, the opposite is not done. It would be
more difficult, as the newt git log is generally not available.
By the way - were you able to try an updated version of newt to see if
you still get the crashes?
Thanks,
Chris
