Re: [ANNOUNCE] NimBLE code moved to separate repository

2018-03-22 Thread Simon Ratner
Ah yes, that would make a lot of sense :) Probably because "core/net" sorts before "nimble". On Thu, Mar 22, 2018 at 2:00 AM, Andrzej Kaczmarek < andrzej.kaczma...@codecoup.pl> wrote: > > Anyway, it's always good to do newt clean after some major upgrade ;-) > > Indeed :)

Re: [ANNOUNCE] NimBLE code moved to separate repository

2018-03-22 Thread Andrzej Kaczmarek
Hi Simon, On Thu, Mar 22, 2018 at 3:18 AM, Simon Ratner wrote: > Heads up - make sure you clean your targets after upgrading. > > For some reason the newt tool is unable to detect that the files have > changed, perhaps because they are at a new path; had fun debugging >

Re: [ANNOUNCE] NimBLE code moved to separate repository

2018-03-21 Thread Simon Ratner
Heads up - make sure you clean your targets after upgrading. For some reason the newt tool is unable to detect that the files have changed, perhaps because they are at a new path; had fun debugging exceptions in the data segment because of mismatched compilation units  Cheers, simon On Mar 16,

[ANNOUNCE] NimBLE code moved to separate repository

2018-03-16 Thread Andrzej Kaczmarek
Hi all, A few minutes ago I merged https://github.com/apache/mynewt-core/pull/907 which removed NimBLE code from mynewt-core repository. NimBLE code can be now found in mynewt-nimble repository https://github.com/apache/mynewt-nimble which has complete history of NimBLE files imported with extra