It's only counterintuitive because your used to Unix. On Unix, environment
variables are the norm. In the old DOS days they were the norm on DOS. In
moving to Windows, and especially now, like it or not, MS moved to this
"registry" idea as a way to centrally locate all these .ini files they
used
to have. There are still enviornment variables on Windows, it's just
they're
so far buried down it's hard to get to. MS "encapsulated" the environment
variables in the registry. Note that it doesn't mean that I like the
system.
The only simple solution I could think of Eric might implement is to
ask the user/administrator at installation time, whether the registry
keys should be brought into place, or whether the user would rather
like to handle that on their own, using environment variables.
I agree though, system-wide environment variables are completely
unsuited as the name of the variable being looked up is always one of
GCC_ROOT, BINUTILS_ROOT, etc -- independent of whether this is a
cross-compiler or not.
Right.
At least with the registry there can be keys that are specific
distro+version. Up until now I haven't put the version on there.
Eric
_______________________________________________
AVR-GCC-list mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
!DSPAM:45c385ef278801393315152!