I can confirm that newt is unusably slow via docker on osx as well. I also
rebuilt from develop so nothing upstream helping there. (btw the jlink
dependency isnt documented currently)

On Fri, Jan 6, 2017 at 11:56 AM, Christopher Collins <[email protected]>
wrote:

> Hi Cris,
>
> On Fri, Jan 06, 2017 at 12:54:03PM -0500, Cris Frusina wrote:
> > Fixed the TCP issue by restarting Virtualbox, did an newt upgrade and a
> > newt install with the 0-dev in the project file.
> >
> > Still missing something as -j is not recognized.
>
> The -j option is only supported in the develop branch.  To get the
> develop version of newt:
>
>     cd $GOPATH/src/mynewt.apache.org/newt/newt &&
>        git checkout develop
>        git pull origin develop
>        go install
>
> But be careful: the develop version of newt is not compatible with
> Mynewt version 1.0.0-b1.  If you use newt develop, then you'll also need
> to use Mynewt develop.  You can upgrade your Mynewt repositories to the
> develop branch as follows:
>
>     1. Open your project.yml in an editor.
>     2. Change all the "vers" fields to 0-dev (they are probably
>        currently set to 0-latest).
>     3. Run "newt upgrade"
>
> If you ever want to revert back to 1.0.0-b1, you can reverse the above
> process, i.e., set the vers fields to 0-latest and run "newt upgrade".
>
> Chris
>
> >
> > ~/newt version
> > Apache Newt (incubating) version: 1.0.0-b1
> >
> > ~/newt build -j 5 ble_usb
> > Error: unknown shorthand flag: 'j' in -j
> > Usage:
> >    newt build <target-name> [target-names...] [flags]
> >
> > Global Flags:
> >    -l, --loglevel string   Log level (default "WARN")
> >    -o, --outfile string    Filename to tee output to
> >    -q, --quiet             Be quiet; only display error output
> >    -s, --silent            Be silent; don't output anything
> >    -v, --verbose           Enable verbose output when executing commands
> >
> > Cris
> >
> >
> >
> > On 1/6/2017 12:27 PM, David G. Simmons wrote:
> > > That looks like your network isn't working from your Docker instance.
> If that's actually the case, it could also (possibly) explain the
> torturously long compile times. Maybe.
> > >
> > > dg
> > >> On Jan 6, 2017, at 12:24 PM, Cris Frusina <[email protected]> wrote:
> > >>
> > >> David,
> > >>
> > >> I've tried what you suggested I'm getting this error:
> > >>
> > >> *apache-mynewt-core**
> > >> **Error: Get https://api.github.com/repos/
> apache/incubator-mynewt-core/contents/repository.yml?ref=master: dial
> tcp: lookup api.github.com on 10.0.2.3:53: read udp 172.17.0.2:38728->
> 10.0.2.3:53: i/o timeout*
> > >>
> > >>
> > >> My project file looks like this now:
> > >>
> > >> project.name: "my_project"
> > >>
> > >> project.repositories:
> > >>     - apache-mynewt-core
> > >>
> > >> # Use github's distribution mechanism for core ASF libraries.
> > >> # This provides mirroring automatically for us.
> > >> #
> > >> repository.apache-mynewt-core:
> > >>     type: github
> > >>     vers: 0-dev
> > >>     user: apache
> > >>     repo: incubator-mynewt-core
> > >>
> > >>
> > >> Am I missing something?
> > >>
> > >> Thanks,
> > >> Cris
> > >>
> > >> On 1/6/2017 12:05 PM, David G. Simmons wrote:
> > >>> You could do that, but if you don't want to remake the whole Docker
> instance, you should be able to simply edit the project.yml file and change
> the vers strin for repository.apache-mynewt-core to 0-dev and then run newt
> install
> > >>>
> > >>> Best regards,
> > >>> dg
> > >>>
> > >>>> On Jan 6, 2017, at 5:23 AM, Fabio Utzig <[email protected]> wrote:
> > >>>>
> > >>>> I'm not using the docker version myself, but I think you could try
> > >>>> rebuilding the docker image:
> > >>>>
> > >>>> https://github.com/runtimeinc/newt-docker <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
> <https://github.com/runtimeinc/newt-docker/blob/master/Makefile#L15>
> > >>>>
> > >>>> Att,
> > >>>> Fabio Utzig
> > >>> --
> > >>> 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.
> > >>>
> > >>>
> > >>>
> > > --
> > > 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.
> > >
> > >
> > >
> >
>

Reply via email to