[EMAIL PROTECTED] writes: > Selon Stephen Leake <[EMAIL PROTECTED]>: > >> Tristan Gingold <[EMAIL PROTECTED]> writes: >> >> I often need to keep several versions (well, at least two) of each >> tool installed; one for a working production system, another for the >> latest upgrade being tested. Possibly another for the previous working >> production system. >> >> This is very difficult if the Windows registry is used; it is painful >> to change the registry entries between the two versions. Especially >> when I don't know what keys need to be changed (I have not checked the >> latest ghdl documentation; perhaps it does say what keys are used). > > Using different versions is not incompatible with the use of registries.
In another posting, you said the registry key is HKLM\Software\Ghdl\Install_Dir I have not looked in the code, but I assume this identifies a directory where ghdl should look for libraries and such. I have version 0.24 installed in c:/Gnu/ghdl-0.24, and 0.25 installed in c:/Gnu/ghdl-0.25. Which one does Install_Dir point to? It has to be one or the other. If it points to 0.25, then 0.24 won't work properly. So I have to edit the registry when I want to switch ghdl versions. > Maybe ghdl should put version in registry keys ? If the key was qualified by the version, that would work: HKLM\Software\Ghdl\0.24\Install_Dir HKLM\Software\Ghdl\0.25\Install_Dir But putting the right bin directory in PATH is simpler, and necessary anyway. In my applications, I compute things like Install_Dir from the path to the executable, which is available from the command line information. >> I understand that unsophisticated Windows users like the registry, >> because "it just works", and setting environment variables in plain >> Windows is itself somewhat painful. > > Yes, and program install/desinstall works trough registry. Agreed; having ghdl show up in the "add/remove programs" list is a Good Thing. But that doesn't mean registry variables should be required for proper running of ghdl from the command line. Actually, this is another place where versioning is important; "add/remove programs" should show all installed versions of ghdl, not just the most recent one. >> Perhaps there could be a way to opt out of using the registry, and use >> environment variables instead. > > Maybe an environment variable may override the registry? That would be good. I suspect that in the case of Install_Dir, computing it from the path to the executable would be even better. -- -- Stephe _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
