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
On 5/11/16 10:12 AM, microBuilder.eu wrote:
This is slightly modified since it now points to the repo folder but the
structure and files are basically identical:
targets/adablink
app=@apache-mynewt-core/apps/blinky
bsp=@apache-mynewt-core/hw/bsp/blefriend32
build_profile=debug
targets/bleper_nrf51
app=@apache-mynewt-core/apps/bleprph
bsp=@apache-mynewt-core/hw/bsp/blefriend32
build_profile=debug
targets/nrf51_boot
app=@apache-mynewt-core/apps/boot
bsp=@apache-mynewt-core/hw/bsp/blefriend32
build_profile=optimized
K.
On 11/05/16 17:49, Christopher Collins wrote:
Ouch... there is clearly a bug in the newt tool. There should be no
problem with creating a BSP package in the local repo. Could you send
the output of 'newt target show'? I would like to see what specifically
triggered this crash. I'll also look see if I have the same issues with
local BSPs.
Thanks,
Chris
