Closed n0toose closed 3 years ago
The variables have to be set if it can't guess them automatically, I wouldn't remove that section.
The variables have to be set if it can't guess them automatically, I wouldn't remove that section.
I mean, is there any other option that could be chosen over instead?
I mean, is there any other option that could be chosen over instead?
Elaborate.
I mean, is there any other option that could be chosen over instead?
Elaborate.
There are options such as BL60X
and BL606
for hal_drv
, but they are not projected to be used due to the way that the Makefile
's are written under customer_app
. There's no way that any other option other than BL602
, without the user explicitly desiring to do so.
For the same reason, I wouldn't understand why guessing the directory could go wrong under a Unix-like environment either.
Anything apart from that should be considered as an edge case and should be documented differently, IMHO. (I can take care of that as well, if necessary.)
For the same reason, I wouldn't understand why guessing the directory could go wrong under a Unix-like environment either.
It assumes the examples are inside the SDK folder, this would break when someone copies an example out and doesn't set the variable. The documentation would be better if it mentioned this nuance.
For the same reason, I wouldn't understand why guessing the directory could go wrong under a Unix-like environment either.
It assumes the examples are inside the SDK folder, this would break when someone copies an example out and doesn't set the variable. The documentation would be better if it mentioned this nuance.
Will correct in a bit.
Fixed the conflict.