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?
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. dg > On Feb 7, 2017, at 11:07 AM, Christopher Collins <[email protected]> wrote: > > Hi David, > > Could your version of the newt tool be out of date? Some backwards > compatibility breaking changes were made about two weeks ago. If that > isn't the problem, could you grab a backtrace in gdb at the point of the > crash ("bt" or "where" in gdb)? > > Thanks, > Chris -- David G. Simmons (919) 534-5099 Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • Linkedin <http://linkedin.com/in/davidgsimmons> • Twitter <http://twitter.com/TechEvangelist1> • GitHub <http://github.com/davidgs> /** Message digitally signed for security and authenticity. * If you cannot read the PGP.sig attachment, please go to * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!! * Public key available at keyserver.pgp.com <http://keyserver.pgp.com/> **/ ♺ This email uses 100% recycled electrons. Don't blow it by printing! There are only 2 hard things in computer science: Cache invalidation, naming things, and off-by-one errors.
signature.asc
Description: Message signed with OpenPGP
