On 2017-06-17 08:06, Mike B Johnson wrote:
Thanks. At least D has something going on correctly here.
My feeling is, unless DVM works well with windows, that it probably
currently doesn't offer much help. If it does manage the versioning well
and can deal with the environmental issues well then it is close to what
I am asking. If that's the case, it should be polished off and used as
the main front end and hosted by D.
You didn't state if it works congruently with all the major compilers.
No, unfortunately it only allows to install DMD.
The issues in windows are:
1. coff/omf. Requires use of windows and visual studio/C stuff who's
locations and versions change over the years. This can be a major
headache finding the right version. Mainly because the error messages,
when using the wrong version, do not suggest that it is a versioning error.
dvm could have the option to search the entire system for the files it
needs(e.g., link.exe, various dlls that are generally used, etc) and
attempt get things to work.
No, DVM doesn't do anything to try to find the installation of Visual
Studio. Unless the compiler already can find it, it won't help. DVM was
created before the compiler supported Visual Studio and I haven't kept
the tool up to date to match that.
3. Re-installation can be problematic. sci.ini is overwritten. If you
hand coded the paths to get everything to work, guess what? Well, who
cares? You have plenty of time to waste, right?
That's a difficult problem. What if you messed up sc.ini and that's the
reason you want to reinstall?
--
/Jacob Carlborg
