On 4/30/16 6:07 PM, Justin Mclean wrote:
Hi,
mynewt-core is a project, just like any project you create with newt new.
So is a “newt build mynewt-core” expected to work?
Nope. mynewt-core is a project (think of it like a workspace in eclipse
or an IDE.)
Within a project, there are applications and board support packages.
So, for example, within core i have a target:
$ newt target show
targets/blinky_sim
app=apps/blinky
arch=sim
bsp=hw/bsp/native
build_profile=debug
this says build the apps/blinky application within the project, and use
the native board support package (stub definitions to run simulated on
OS X.) build_profile=debug means include debugging symbols, and
arch=sim is entirely unnecessary (used to be required, now the bsp
defines the architecture.)
Here are the apps you can try building within core:
drwxr-xr-x 4 sterling staff 136 Apr 28 12:13 bleprph
drwxr-xr-x 4 sterling staff 136 Apr 28 12:13 bletest
drwxr-xr-x 4 sterling staff 136 Apr 28 12:13 bletiny
drwxr-xr-x 4 sterling staff 136 Mar 24 10:09 blinky
drwxr-xr-x 4 sterling staff 136 Apr 28 12:13 boot
drwxr-xr-x 4 sterling staff 136 Mar 14 17:43 ffs2native
drwxr-xr-x 4 sterling staff 136 Mar 14 17:43 luatest
drwxr-xr-x 4 sterling staff 136 Apr 28 12:13 slinky
drwxr-xr-x 4 sterling staff 136 Mar 14 17:43 test
To try bletiny, look at this tutorial:
http://mynewt.apache.org/os/tutorials/bletiny_project/
You don't need to create a new project, you can just checkout core, and
build bletiny. To do that, you just omit the repository descriptor when
creating targets within apache-mynewt-core (repository descriptor =
@apache-mynewt-core), because you are in the local context.
Cheers,
Sterling
