Hi Then,
It may be useful to look at how we bundle chip vendor SDKs when looking
at incorporating this project.
If there are an additional set of options that would help make this easy
to work with newt, don’t hesitate to suggest them. We want to make
this easy.
Here is a pkg.yml file which specifies how to build the Nordic SDK:
https://github.com/runtimeinc/mynewt_nordic/blob/master/hw/mcu/nordic_sdk/pkg.yml
You can notice a few things:
pkg.type: sdk
Tells newt that this is an external SDK package. When newt sees that,
it looks in the src/ext directory of the package, and has a few rules:
1- Recurse all sub-directories of ext, and add them directly to the
include path (allowing the include path to resolve.)
2- Recursively build all sub-directories of ext.
As you can see in the pkg.yml there are then additional rules you can
apply to the complication, like which directories to build (if you
don’t want to build all of ext/*, use pkg.src_dirs), and what types of
files to ignore (ign_files) and what type of directory names to ignore
(ign_dirs).
Hope this helps. Again, if there are additional things you need to make
this easier, let us know. We can look at making newt work better for
your scenario.
Best,
Sterling
On 21 Dec 2016, at 21:37, then yon wrote:
Dear Support,
Can i know how to use include path in myNewt?
Currently i having an existing project that i wish to port into myNewt
platform; it will be a big hassle without include path feature.
Thank you.
Regards,
Then Yoong Ze
