Re: [Iverilog-devel] Icarus keys in the Windows registry

[Martin W. <mai...@ma...>]

Having slept on this, I'm questioning why iverilog-vpi needs to store anything 
in the registry. The two things it stores there are

   - the path to the iverilog root directory
   - the path to the installed MinGW compiler

The first of these it could work out for itself, in the same way vvp does. The 
second is just added to the PATH environment variable - surely it is easier to 
ask the user to add this to PATH themselves. After all, any user capable of 
writing VPI modules is surely capable of setting up their PATH variable.

Martin Whitaker wrote:
> When running natively in Windows, iverilog-vpi stores a couple of keys in the
> registry. Currently it stores these in
>
>     HKEY_LOCAL_MACHINE\Software\Icarus Verilog
>
> With typical Microsoft consistency, a 32-bit application running with normal
> user privileges can add these keys to the registry, but, on the same Windows
> machine, a 64-bit application must be running with administrator privileges.
>
> Currently iverilog-vpi silently fails to store the keys when built as a 64-bit
> application. I could fix this in two ways:
>
>     - output a warning message to inform the user they need to run with
>       administrator privileges
>
>     - change the key location to HKEY_CURRENT_USER
>
> I'm inclined to go for the second option. Does anyone wish to argue otherwise?