On Wednesday, 3 September 2014 at 13:18:50 UTC, Chris wrote:
On Wednesday, 3 September 2014 at 13:10:28 UTC, Jacob Carlborg
On 03/09/14 11:08, Chris wrote:
If I install dmd 2.066 with dvm, it won't overwrite or change
No, the whole idea is to have multiple compilers installed
I'll soon be moving my code from 2.065 to 2.066, but I want
2.065 around for a while to maintain existing code till the
Yes, that's the whole idea.
And how do I integrate it with dub?
It doesn't have a direct integration with Dub. But that's the
other part of the idea. Just run "dvm use <compiler_version>"
to set the version you want to use. When Dub runs DMD it will
use the one you chose earlier. It works with any tool invoking
DMD in the same session as you run "dvm use".
Thanks. I thought so, I just wanted to be 100% sure it really
works this way, before doing anything. Hit-and-miss can cause
some serious headaches when dealing with different dmd
Thanks also for the great tool. This will make the transition a
This all works on the command line. If you have some form of
IDE chose the location where DVM installs the compilers. On
Posix this will be ~/.dvm and on Windows this will be
C:\Users\<username>\AppData\Roaming\dvm. Then either pick any
of the following:
* <path_to_dvm>/bin/dmd-<version> - for a specific compiler
* <path_to_dvm>/bin/dvm-current-dc - the compiler you chose
last time with "dvm use <version>"
* <path_to_dvm>/bin/dvm-default-dc - the default compiler, set
with "dvm use <version> -d"
Methinks DVM doesn't get it right. 2.065.zip is available here:
But DVM tries to access it via http:
An unknown error occurred:
The resource with URL "http://ftp.digitalmars.com/dmd.2.065.zip"
could not be found.