[En-Nut-Discussion] UI feaure request

[Ulrich Prinz]

Hi all,

as a result of a little discussion with Uwe, I would like to request a
feature to the graphical NutO/S configuration tools. I request this, as I
do not have enough knowledge to implement it myself.
I request this feature as I found that it would be very helpful when I
developed systems based on NutO/S in teams of 2..8 people over the past 5
years.

The biggest request is an option to save more project details inside the
project conf file.
Everyone who deveopls for a series of chips with NutO/S probably ran into
the problem that he modifies code again and again until he figures out,
that the build runs on the wrong subdirectory...
This likely happens if you need to code on very similar chips like
STM32L152 and STM32L034 and STM32L151... You try many times until you see
that you compile in L151/ while the libraries are building for L152/lib...

So my wish is to implement an option to the (q)nutconf utility that
optionally saves the project settings into the conf file. This could be
done by adding another checkbox that, if enabled, saves all directory
settings in the project too.

I would NOT save the compiler and programmer options with this checkbox
enabled, but add a different one on the corresponding pages. The reason for
this is, that different people have set up their systems in a different
way. So one has compilers in /opt/arm-none-.../ while another one uses
/usr/share/ or C:\Program Files\...
And even the programmer dongles may ber different...

But If you prepare a setup with
nutbld-l151-gcc/
nutbld-l151-gcc/lib/
and
nutapp-l151-gcc/your-project

And then again
nutbld-l152-gcc/
nutbld-l152-gcc/lib/
and
nutapp-l152-gcc/your-other/project

itwould really help, if loading l151.conf would load library path and
application path too instead of still compiling code for the previously
loaded l152 project.

How about that idea?

Regards
Ulrich