[En-Nut-Discussion] RE: Nutconf /s option

[Jesper Hansen]

I have to join in here after spending hours on this.
First, I was not aware that the configurator used a common file instead 
of having all info in the CONF file (which would be the only sensible 
way), so after trying to remake my new 3.9.9 a number of times, and it 
still didn't show up correctly in the build dir, I realized that I had 
totally broken my old 3.9.8 project, and all the changes I had made to 
makefiles, and various files were overwritten and lost.
I then spend a while trying to find all the places were I needed to 
change the patch to 3.9.9 instead of 3.9.8 which I've previously been 
using. I only have to change 5 places instead of 7. It's still 5 places 
too many!
I finally managed to get the new 3.9.9 built. But then I had to go back 
and change all 5 places again, to rebuild my old 3.9.8 project. After I 
changed all the files back to normal, I wanted to use the configurator 
again on 3.9.9 and had to change 5 places again.
Man, you were NOT a popular person at that moment, Harald !

Now, I've finally heard that you can use the /S parameter, but that's 
just not the right way. First of all, the nutconf is a nice little icon 
that is clickable, I don't want to fuddle around with an undocumented 
command line option everytime I need to use the configurator.
Secondly, as this is apparently necessary for using NutConf properly, 
why is this not documented ?
PLEASE move ALL settings to the CONF file, so opening a conf will pull 
in all the settings for a project.
I'm quite sure many have been extremely frustrated over how Nutconf 
handles settings.

/Jesper



Rob van Lieshout (PragmaLab) wrote:
>  Hi Lars,
> 
> I don't think you did something clumsy. I'm shure more Nut-users run into
> this 'problem'. The idea should be (imo) that loading the config file
> settles all information needed for the configurator. But, for some reason
> one decided to put the information in 2 places: the configuration file AND
> in the (Windows)register. Alhtough this makes some sense (all information
> needed to build NutOS is put in the config-file, all meta-info that is
> needed for the tool itself is put in the register), it confuses people and
> (most important) it triggers errors beacause after upgrading to a different
> (new) Nut-release, you are not aware of the fact that all meta-info still
> points to the previously used build of NutOS (paths!).
> 
> OK, as Harald pointed out some days ago in this list, there is a solution
> using the /S=somename option when starting 'nutconf' from the commandline.
> As Harald only mentioned the solution and not HOW to use it, it took me some
> time to figure it out. But it works very simple: 
> 
> STORE:
> Storing the meta-info (eg the info you had to change in 7 places):
> 'nutconf /S=3.9.9' (the string after the '=' is up to you) -> opens the
> configurator and you can enter all meta-info under the 'Edit' menu, like
> paths, etc.
> 
> RECALL:
> Then next time you want to use the configurator with the same meta-info, you
> retype 'nutconf /S=3.9.9' and it wil start the configurator and recalling
> the meta-info using the register entry that was created the first time.
> 
> This way you can handle several NutOS builds without entering all meta-info
> over and over again. Very useful when you need to switch between NutOS
> versions. 
> 
> Sad thing is that the meta-info does NOT store the name of the config-file
> and so you will be asked which config-file you want to load each time you
> start 'nutconf'. I'm shure this minor mistake will be fixed in the near
> future, since the configurator is still 'a bit under construction' as I
> understood
> 
> Hope this helps.....
> 
> regards
> 
> Rob van Lieshout
> 
> 
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
> 
>