|
From: Martin W. <mai...@ma...> - 2015-05-06 23:46:15
|
Stephen Williams wrote: > Ironically, after re-reading this post, I realized that setting the > path is exactly what we expect of users in order to get access to > the iverilog-vpi tool in the first place. So, logic fail on my part. > > Still, it was my choice in the first place to locate the mingw tools > via the registry (not that I ever really use Windows) and my thinking > was to simplify the experience as much as possible, and also to not > pollute the users path any more then necessary. So if not a registry > entry, perhaps a .ini file in the iverilog install directory? > Users who have installed the MinGW compiler will most likely have added it to their path already - otherwise they won't be able to use it to compile C programs. In this case the current procedure complicates the user experience, because they have to run iverilog-vpi to set a path that is already known to the system. So I suggest a better solution is to first search the current path for the MinGW compiler, and if it is not found, prompt the user to enter a path and store it in a .ini file for future use. Martin |