[En-Nut-Discussion] Disabling drivers during compile time
Thiago A. Corrêa
thiago.correa at gmail.com
Mon Oct 7 18:45:04 CEST 2013
I mean stuff like this: (nut\arch\arm\dev\atmel\charlcd_at91.c)
#define LCD_ROWS 2
#define LCD_COLS 16
No one selected those values anywhere, they are just stub to make sure
it builds. Boards that don't even have that device will build the
On Mon, Oct 7, 2013 at 1:38 PM,
<bon at elektron.ikp.physik.tu-darmstadt.de> wrote:
>>>>>> "Thiago" == Thiago A Corrêa <thiago.correa at gmail.com> writes:
> Thiago> Hi, In all of Nut/OS, we are constantly comming up with bogus
> Thiago> driver settings just to satisfy the build. Stuff there were not
> Thiago> in the board .conf file or selected by the user in the
> Thiago> configurator but needs to end up in one of the cfg headers.
> Shouldn't include/dev/board.h on exit set all needed values not set so long?
> Otherwise: Can you give an example how to get some of these errors?
> Compiling all default .conf files for avr8/avr32 and arm didn't show me such
> a problem, or it got by unnoticed, as Harald changed the default behaviour
> not to abort compile on error...
> Uwe Bonnes bon at elektron.ikp.physik.tu-darmstadt.de
> Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
> --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
More information about the En-Nut-Discussion