|
From: Stephen W. <st...@ic...> - 2015-05-06 15:57:24
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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? On 05/06/2015 07:39 AM, Stephen Williams wrote: > > It is absolutely NOT realistic to expect users to add the mingw > directory to the path on windows systems. Yes it would work and yes > that is kinda what the path is for, but that is not really the user > experience/expectation on Windows, even for command line tools. > > I'm also a little uneasy about changing the key from LOCAL_MACHINE > to CURRENT_USER. Doesn't the latter only apply to the currently > logged on user? > > Can we insist that install is done by an admin user that can set > HKEY_LOCAL_MACHINE? > > On 05/06/2015 12:46 AM, Martin Whitaker wrote: >> 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? > > >> ------------------------------------------------------------------------------ > >> > > One dashboard for servers and applications across > Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable >> Insights Deep dive visibility with transaction tracing using APM >> Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> _______________________________________________ Iverilog-devel >> mailing list Ive...@li... >> https://lists.sourceforge.net/lists/listinfo/iverilog-devel > > > > > ------------------------------------------------------------------------------ > > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable > Insights Deep dive visibility with transaction tracing using APM > Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ Iverilog-devel > mailing list Ive...@li... > https://lists.sourceforge.net/lists/listinfo/iverilog-devel > - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlVKOdkACgkQrPt1Sc2b3ikbhACfTSMPaMTxajM6tuzvCHYNhdHx 7EUAn0il8tuNGWhAivukxk96u+Gi5MBj =ZprX -----END PGP SIGNATURE----- |