|
From: Michael S. <mic...@gm...> - 2015-05-06 23:49:42
|
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. Best regards, Michael Strelnikov On 7 May 2015 at 09:46, Martin Whitaker <mai...@ma...> wrote: > 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 > > > > > ------------------------------------------------------------------------------ > 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 > |