[En-Nut-Discussion] qnutconf path mysteries

Ole Reinhardt ole.reinhardt at embedded-it.de
Tue Dec 8 16:24:28 CET 2009


Hi Thiago,

> About the "allow multiple configurations" I agree. It doesn't work
> propery at all (nutconf). The problem with saving it in the .conf file
> is that the command line would have to be extended in the same way. I
> thought of creating a "project" with xml containing a reference for
> the .conf file and the compiler settings. 

That's a nice idea and could solve Haralds objection that one have to do
all these configuration steps again if there is just a small change in
the board.conf file.

What about some kind of hierarchical approach where you reference a
board.conf file in the selected NutOS folder and can overwrite every
setting by the ones that are saved in your xml project file? 

> I didn't consider fixing the
> nutrepository.nut path problem (or, Nut/OS version problem), but on
> the other hand, the compiler settings is more anoying. If you have
> boards with atmega and arm or atmega and uc3 (different boards,
> different confs), then whenever you need to build for another board,
> you need to change the compiler settings.

Right. A project file would help here too.

Bye,

Ole

-- 

Thermotemp GmbH, Embedded-IT

Embedded Hard-/ Software and Open Source Development, 
Integration and Consulting

Geschäftsstelle Siegen - Steinstraße 67 - D-57072 Siegen - 
tel +49 (0)271 5513597, +49 (0)271-73681 - fax +49 (0)271 736 97

Hauptsitz - Hademarscher Weg 7 - 13503 Berlin
Tel +49 (0)30 4315205 - Fax +49 (0)30 43665002
Geschäftsführer: Jörg Friedrichs, Ole Reinhardt
Handelsregister Berlin Charlottenburg HRB 45978 UstID DE 156329280 




More information about the En-Nut-Discussion mailing list