[En-Nut-Discussion] qnutconf snapshots

[Ulrich Prinz]

Hi Thiago!

I needed just a free C compiler for a quick helper program to decode an 
unknown protocol. So why take a bit if you can get the full version :)
I installed Qt and used it's mingw as a C compiler for my litte command 
line application.

But for a quick test I loaded your qnutconf and gave it a try.
Respect! Good work so far.

I have a little problem with entering the correct paths. I run the 
program out of the qnutconf directory, but I changed the execution path 
to my nutos top level directory.
Then in settings I entered the paths like I had them in the old nutconf.
This doesn't work. If I give '/nut' it goes from the root of the drive 
(q:/nut/conf/repository.nut)
If I put 'nut' it redefines to nut//conf/repository.nut (yes with 
double-slash)
If I put some absolute path, It doesn't work either, but I had no time 
to follow that.

Ah, I use the trunk version from sourceforge, as that was the one laying 
round in sight.

Additionally there where to compiler errors, one file function with a 
parameter to less, and a printf with an argument to much. I can check, 
but I am currently installing Qt. Will test in a few minutes.

But again, great work!

Best regards, Ulrich

Thiago A. Corrêa schrieb:
> Rich,
> 
> On Tue, Jan 26, 2010 at 6:12 PM, gofootn <rpeters at micro-magic.com> wrote:
>> one feature that would life a lot easier when you are working with multiple
>> nut/os versions and build types:
>>
>> Save the edit | settings NutConf settings dialog parameters to a config
>> file, so that multiple versions can be used.  If I switch between 4.8.5 and
>> 4.9 I have to redo all of those settings.
>> QSettings can read/write an xml file instead of the registery which can then
>> be externally edited or distributed.
>> This would make life a lot easier, especially when configuring a new build
>>
> 
> I think it shouldn't lose it's config switching from one version to
> another in the registry, since there is no version specifics there.
> The problem should arise when using Nut/OS for different archs. For
> instance, I have a set of boards that use atmega and I'm now
> developing boards with AVR32. To switch from one to another I have to
> enter the settings dialog and change the compiler. I thought of having
> a project file, that could store the compiler settings as well as
> reference the board .conf file. Then I could have a project file for
> atmega and one for AVR32 and switch from one to another just opening
> the project file.
> 
> With that I could replace the current "Multiple configurations" that
> nutconf has (not implemented in qnutconf yet) using a xml file per
> project. This would take some effort to implement, I was thinking
> about having that a little later on, after a release, so it's not
> delayed too much.
> 
> Thanks,
>     Thiago A, Correa
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion