Hi Sterling,
Thanks for the quick reply and solution.
You're correct, the compiler was missing the reference to the repo and I
can build local BSPs with the following changes from the source BSP:
pkg.compiler: "@apache-mynewt-core/compiler/arm-none-eabi-m0"
pkg.deps:
- "@apache-mynewt-core/hw/mcu/nordic/nrf51xxx"
- "@apache-mynewt-core/libs/baselibc"
pkg.deps.BLE_DEVICE:
- "@apache-mynewt-core/net/nimble/drivers/nrf51"
Being able to clone or create packages from newt might make life easier
for newcomers, yes, as well as a slightly friendlier error message.
Thanks for generating the issue. There seems to be an inconsistency in
the last line, although I believe the `pkg.name` field should be the
same as the folder location, despite the issue saying "can not match".
I'm sure it's clear to the appropriate individuals though:
* Currently pkg.name and the name of the package directory can not
match, and the pkg.name will be taken over the pkg directory. There
should be a warning issued if the package directory does not match
the package name.
Best regards,
Kevin
On 11/05/16 23:57, Sterling Hughes wrote:
Hi Kevin,
I was able to reproduce the issue, it looks like you didn't update the
repository descriptor for the pkg.compiler -- that should point to a
package in the @apache-mynewt-core repository as well. If you do that,
you should get past that error. I was able to get your target to
compile.
I've filed a bug in JIRA to capture some of the improvements we'll put
into the next release:
https://issues.apache.org/jira/browse/MYNEWT-293
As a fresh a user of Mynewt, if you can add any thoughts you have to
the ticket (or thread), that would be helpful. We'll make sure to
consider them as we improve newt.
Cheers,
Sterling
