v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-718966030
Hi, you can find the PR here: #878
This is an automated message from the Apache Git Service.
To respond to the
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-698332246
Cool! I'm hoping I can merge the required change on NuttX side and then I
can open a PR here so we can discuss the changes on nimBLE side.
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-698332246
Cool! I'm hoping I can merge the required change on NuttX side and then I
can open a PR here so we can discuss the changes on nimBLE side.
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-696111317
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-696182614
I just tried that and it doesn't work. You cannot override include search
paths for `#include` directives using `"` instead of `<`/`>`. If it were
included as `#include ` you can
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-696159797
But `modlog.h` is also inside host/include and also uses `"` to include so I
cannot override it. You can see the include path here:
```
In file included from
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-696111317
I understand. The problem is that `modlog.h` (another file under
`porting/nimble/include`) does `#include "log/log.h"` so I cannot override it
with include flags. `modlog.h` in
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-695363772
Mmm, actually I just commented this definitions out in `log.h` so I guess
they are not needed. Is that correct?
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-695363265
Thanks for your response
> `MYNEWY_VAL` macros are not defined because relevant syscfg settings are
only defined when NimBLE Controller package is included in build. if you'd
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-695359710
> > However one issue I find is that NuttX requires an initial include in
every .c and .h as: `#include ` which holds the output of the
Kconfig configuration system. For the OS
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-693629093
I'm hitting an issue where some controller-related macros are not defined
(not that I'm not using controller), even after adding them to syscfg.yml. For
example, BLE_CONTROLLER,
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-693552683
> However one issue I find is that NuttX requires an initial include in
every .c and .h as: `#include ` which holds the output of the
Kconfig configuration system. For the OS
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-693549325
Ah, you're right. I see it there. Ok, I will continue then to build nimBLE
from within NuttX using this syscfg.h.
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-693545708
Thanks, yes, I've found some email in mailing list archive with similar
error and it was suggested to use newt from master. This problem disappeared
then. However, I'm struggling
v01d commented on issue #864:
URL: https://github.com/apache/mynewt-nimble/issues/864#issuecomment-693469399
I think I'm understanding that i need to generate a syscfg.h for my
platform. I've found some information in other issues here on how to
supposeddly do this. I've created a newt
15 matches
Mail list logo
