I'm not using the docker version myself, but I think you could try rebuilding the docker image:
https://github.com/runtimeinc/newt-docker Inside the Makefile, change the branch that is checked out from "-b mynewt_1_0_0_b1_tag" to "-b develop": https://github.com/runtimeinc/newt-docker/blob/master/Makefile#L15 Att, Fabio Utzig On Fri, Jan 6, 2017, at 01:14 AM, Cris Frusina wrote: > Stupid question... Is there any way to try out the development branch > while using the docker method on a Windows machine? > > Cris > > > On 1/5/2017 8:20 PM, Sterling Hughes wrote: > > This is awesome, timing on the new build (after a clean): > > > > Target successfully built: targets/nrf52 > > > > real 0m6.327s > > user 0m26.972s > > sys 0m9.276s > > $ newt target show nrf52 > > targets/nrf52 > > app=apps/slinky > > bsp=hw/bsp/nrf52dk > > build_profile=debug > > > > 6 seconds for a full build. Not bad! > > > > Sterling > > > > On 5 Jan 2017, at 11:57, Christopher Collins wrote: > > > >> On Thu, Jan 05, 2017 at 09:00:11AM -0500, Cris Frusina wrote: > >>> Hi David, > >>> > >>> Sounds like a pain! > >>> > >>> So I got an Ubuntu VM running on the Windows machine and installed > >>> the myNewt natively. I didn't really see much of a speed bump (needs > >>> a bit further testing). I'll try a different computer later today. > >>> Worst case I'll find a Mac to try it on. > >> > >> Just an note - I ended up adding multithreaded build support to newt > >> yesterday. In the develop branch, you can enable it with the > >> "-j <num-parallel-jobs>" command line option, e.g., > >> > >> newt -j 5 build my_blinky_sim > >> > >> A word of warning, though: don't upgrade your newt to develop if you > >> are using Mynewt 1.0-b1 and aren't prepared to upgrade that as well. > >> Since the 1.0-b1 release, some backwards-compatible changes were made to > >> the newt tool. > >> > >> Thanks, > >> Chris > > > > >
