Newt run target name will run it in the container-- when using docker the sim binary is compiled under Linux to run on Linux.
Sterling (Thumb typing) > On May 28, 2016, at 1:07 PM, David Moshal <[email protected]> wrote: > > Not sure if this is the best place to put this, I managed to get > MyNewt to build, but ran into same error: > > This was the missing step (duh): > ``` > ⇒ eval $(docker-machine env default) > ``` > > then: > ``` > ⇒ ../newt install > apache-mynewt-core > ``` > > and: > ``` > ../newt test all > <snip> > All tests passed > ``` > > but: > ``` > ⇒ ./bin/my_blinky_sim/apps/blinky/blinky.elf > zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf > ``` > > David > > > >> On Sat, May 28, 2016 at 12:12 PM, David Moshal <[email protected]> wrote: >> Ok, >> >> The twin challenges for a double-newbie are: >> >> a) selecting the right toolchain and development tools, ide etc. >> - so far I've identified at least ten (mbed, platformio, Kiel, IVR, >> Crossworks, Clion, Sublime (seems most common), etc. >> >> b) evaluating MyNew against alternatives: >> - no OS (seems most common), FreeRTOS, mBed, etc. etc. >> >> In each case the defacto evaluation task seems to be blinking the onboard >> LED. >> >> So, with regards to MyNewt: >> - I used the Docker install option, but couldn't get the first >> project to work, the error was: >> >> ``` >> ../newt install >> docker: Cannot connect to the Docker daemon. Is the docker daemon >> running on this host?. >> See 'docker run --help'. >> ``` >> >> Note: Docker machine was started without any problem: >> ``` >> ⇒ docker-machine start default >> Starting "default"... >> (default) Check network to re-create if needed... >> (default) Waiting for an IP... >> Machine "default" was started. >> Waiting for SSH to be available... >> Detecting the provisioner... >> Started machines may have new IP addresses. You may need to re-run the >> `docker-machine env` command. >> >> ⇒ docker-machine env default >> export DOCKER_TLS_VERIFY="1" >> export DOCKER_HOST="tcp://192.168.99.100:2376" >> export DOCKER_CERT_PATH="/Users/davem/.docker/machine/machines/default" >> export DOCKER_MACHINE_NAME="default" >> # Run this command to configure your shell: >> # eval $(docker-machine env default) >> ``` >> >> also the simulated version didn't seem to want to run: >> >> ``` >> ⇒ ./bin/my_blinky_sim/apps/blinky/blinky.elf >> zsh: exec format error: ./bin/my_blinky_sim/apps/blinky/blinky.elf >> ``` >> >> >> So, that's as far as I got with MyNewt. >> Hope it helps. >> >> David >> >> ps: do we have a slack channel or Github issue system? >> Easier to past code with markdown than in email. >> >> >> >> >>> On Sat, May 28, 2016 at 11:54 AM, Sterling Hughes <[email protected]> >>> wrote: >>> Hi David, >>> >>> On 28 May 2016, at 11:47, David Moshal wrote: >>> >>>>> i’d be interested in what others (especially newcomers) would have found >>>>> helpful in the release tarballs in terms of documentation. i feel like we >>>>> have a fairly good set of docs on mynewt.apache.org, but that often people >>>>> want to see the docs next to the source code— and not have to wonder >>>>> what’s >>>>> on a website. but i’d take others thoughts here: i usually just go ahead >>>>> and try and break things, and then search for docs after they don’t work. >>>> >>>> >>>> Sterling: I'm a double newcomer, i.e: new to MyNewt, and new to embedded >>>> C. >>>> Does that count? >>> >>> Of course. We’ll take it in that context, but if you’re willing to take the >>> time to put your thoughts down- it will only help us. >>> >>> Thanks, >>> >>> Sterling
