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, 2018 02:09, "Andrzej Kaczmarek" <andrzej.kaczma...@codecoup.pl> wrote: > 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 > information about original commit id. > > Mynewt-core repository is configured with dependency to new > mynewt-nimble repository - this requires new "newt" version which will > be part of 1.4 release or if you work with master, please build "newt" > from current master and then upgrade project with "newt upgrade". > > To make migration seamless, all @apache-mynewt-core/net/nimble/* > packages have dependency created to corresponding packages in > @apache-mynewt-nimble. This is a temporary solution and we'll probably > remove this in one of future releases (for sure not in 1.4). > > Soon we will also close all pending PRs which touch NimBLE code (there > are only few of them) asking authors to port them to new repository. > > Best regards, > Andrzej >
