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

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

Michael Strelnikov wrote:
> I'm not sure about storing in .ini file is a good idea either.
> Sometimes this path can be changed and user will have a hard time wondering
> why simulations stopped working.
>
iverilog-vpi does check whether the C compiler can be found on the currently 
stored path, and outputs an informative message if not.

The logic I've implemented is:

   - If -mingw=path is supplied alone on the command line, the
     path is stored in the registry as before. If access is
     denied, a message is output that suggests running as
     administrator.

   - If -mingw=path is supplied with a list of source files, it
     is used as the path for that run only and not stored in the
     registry.

   - If -mingw=path is not supplied, iverilog-vpi first looks in
     the registry, and if a path is stored there, uses that. If
     there is no entry in the registry, it seaches the system path.
     If the C compiler is not found on the system path, it outputs
     an informative message and quits.

Hopefully this will satisfy all parties.

I've removed the -ivl option, and made iverilog-vpi automatically extract the 
IVL root directory from the location of the .exe file, exactly as vvp does.

Martin