No worries: try setting the feature vs CFLAGS. (Note: all good efforts
learning about features will be unfortunately useless, as we’ve
changed to sys config in develop :-( ).
# clear cflags
newt target set bootloader cflags=
# set feature
newt target set bootloader features=BOOT_SERIAL
That will enable extra dependencies and automatically set cflags. I
believe marko also had a comment in the pkg.yml about uncommenting
libs/console/stub — worth looking at that if you have conflicts with
console after enabling the BOOT_SERIAL feature.
On 23 Sep 2016, at 9:20, Kevin Townsend wrote:
Hi Sterling,
Thanks for the heads up. I added the cflag via '$ newt target set
bootloader cflags=-DBOOT_SERIAL' and I can see that it exists in
'/repos/apache-mynewt-core/libs/boot_serial', though when I try to
build I'm getting:
$ newt build bootloader
Building target targets/bootloader
Compiling boot.c
Error: boot.c:33:37: fatal error: boot_serial/boot_serial.h: No
such
file or directory
#include <boot_serial/boot_serial.h>
^
compilation terminated.
The target definition seems fine though (I'm on the 'master' branch
just as a FYI):
$ newt target show
targets/bootloader
app=@apache-mynewt-core/apps/boot
bsp=hw/bsp/feather52
build_profile=optimized
cflags=-DBOOT_SERIAL
I also tried 'newt install' and 'newt upgrade' to refresh the local
setup but same results. Perhaps I need to update something in the
local BSP, though ... I'll have a look at that.
Thanks for the heads up about this library, though. Somehow it never
ended up on my radar, but I'll try to get this building and test it
out this weekend.
BR,
Kevin
