Jump to page: 1 24  
Page
Thread overview
DVM - D Version Manager 0.4.3
Sep 02, 2014
Jacob Carlborg
Sep 02, 2014
eles
Sep 02, 2014
eles
Sep 03, 2014
Jacob Carlborg
Sep 04, 2014
Jordi Sayol
Sep 04, 2014
Nick Sabalausky
Sep 04, 2014
Jordi Sayol
Sep 04, 2014
Nick Sabalausky
Sep 04, 2014
Jordi Sayol
Sep 05, 2014
Jacob Carlborg
Sep 05, 2014
Jacob Carlborg
Sep 05, 2014
Jacob Carlborg
Sep 05, 2014
Jacob Carlborg
Sep 04, 2014
Jordi Sayol
Sep 05, 2014
Jacob Carlborg
Sep 05, 2014
Marc Schütz
Sep 05, 2014
Jacob Carlborg
Sep 02, 2014
Nick Sabalausky
Sep 03, 2014
Chris
Sep 03, 2014
Jacob Carlborg
Sep 03, 2014
Chris
Sep 03, 2014
Chris
Sep 03, 2014
Sean Kelly
Sep 03, 2014
Chris
Sep 03, 2014
Sean Kelly
Sep 04, 2014
Jacob Carlborg
Sep 04, 2014
Chris
Sep 04, 2014
Jacob Carlborg
Sep 05, 2014
Chris
Sep 05, 2014
Jacob Carlborg
Sep 04, 2014
Jacob Carlborg
September 02, 2014
I just released a new version of DVM, 0.4.3. The biggest news for this release is that both 32 and 64bit libraries are supported simultaneously. Now DVM will just copy the platform specific directory without messing with the directory structure.

This release fixes a critical bug that made it not possible to install new compilers.

Also building using Dub is supported. I'm going to wait a bit to add to code.dlang.org because Dub head is required.

For pre-compiled binaries and changelog (or below) see: https://github.com/jacob-carlborg/dvm/releases/tag/v0.4.3

For those not familiar with DVM:

DVM allows you to easily download and install D compilers and manage different versions of the compilers.

Changelog:

Version 0.4.3
  New/Changed Features
   * Add support for Dub
   * Since issue 23 has been fixed this means that now both 32 and 64bit libraries are supported simultaneously

  Bugs Fixed
   * Fix issue "unexpected redirect for method GET"
   * Issue 23: Leave DMD directory structure as-is

-- 
/Jacob Carlborg
September 02, 2014
On Tuesday, 2 September 2014 at 19:46:32 UTC, Jacob Carlborg wrote:
> I just released a new version of DVM, 0.4.3. The biggest news for this release is that both 32 and 64bit libraries are supported simultaneously. Now DVM will just copy the platform specific directory without messing with the directory structure.
>
> This release fixes a critical bug that made it not possible to install new compilers.
>
> Also building using Dub is supported. I'm going to wait a bit to add to code.dlang.org because Dub head is required.
>
> For pre-compiled binaries and changelog (or below) see: https://github.com/jacob-carlborg/dvm/releases/tag/v0.4.3
>
> For those not familiar with DVM:
>
> DVM allows you to easily download and install D compilers and manage different versions of the compilers.
>
> Changelog:
>
> Version 0.4.3
>   New/Changed Features
>    * Add support for Dub
>    * Since issue 23 has been fixed this means that now both 32 and 64bit libraries are supported simultaneously
>
>   Bugs Fixed
>    * Fix issue "unexpected redirect for method GET"
>    * Issue 23: Leave DMD directory structure as-is

Thank you. I see that you provide packages for Debian (albeit they are BIN files). Would it be a huge effort to add DVM to this repository of D?:

http://d-apt.sourceforge.net/

That would indeed make install even easier.
September 02, 2014
On Tuesday, 2 September 2014 at 20:05:21 UTC, eles wrote:
> On Tuesday, 2 September 2014 at 19:46:32 UTC, Jacob Carlborg wrote:


> That would indeed make install even easier.

And, especially, updates.

September 02, 2014
On 9/2/2014 3:46 PM, Jacob Carlborg wrote:
> I just released a new version of DVM, 0.4.3.
> [...]
> Version 0.4.3
>    New/Changed Features
>     * Add support for Dub
>     * Since issue 23 has been fixed this means that now both 32 and
> 64bit libraries are supported simultaneously
>
>    Bugs Fixed
>     * Fix issue "unexpected redirect for method GET"
>     * Issue 23: Leave DMD directory structure as-is
>

Sweet!!! Been looking forward to this.

September 03, 2014
On 02/09/14 22:05, eles wrote:

> Thank you. I see that you provide packages for Debian (albeit they are
> BIN files). Would it be a huge effort to add DVM to this repository of D?:

I have no idea. Linux is not my main platform. I only chose Debian because it's a stable/old system with a high chance of being binary compatible with other distributions.

Perhaps you would like to contact the maintainer of that repository?

-- 
/Jacob Carlborg
September 03, 2014
On Tuesday, 2 September 2014 at 19:46:32 UTC, Jacob Carlborg wrote:
> I just released a new version of DVM, 0.4.3. The biggest news for this release is that both 32 and 64bit libraries are supported simultaneously. Now DVM will just copy the platform specific directory without messing with the directory structure.
>
> This release fixes a critical bug that made it not possible to install new compilers.
>
> Also building using Dub is supported. I'm going to wait a bit to add to code.dlang.org because Dub head is required.
>
> For pre-compiled binaries and changelog (or below) see: https://github.com/jacob-carlborg/dvm/releases/tag/v0.4.3
>
> For those not familiar with DVM:
>
> DVM allows you to easily download and install D compilers and manage different versions of the compilers.
>
> Changelog:
>
> Version 0.4.3
>   New/Changed Features
>    * Add support for Dub
>    * Since issue 23 has been fixed this means that now both 32 and 64bit libraries are supported simultaneously
>
>   Bugs Fixed
>    * Fix issue "unexpected redirect for method GET"
>    * Issue 23: Leave DMD directory structure as-is

If I install dmd 2.066 with dvm, it won't overwrite or change anything? I'll soon be moving my code from 2.065 to 2.066, but I want to keep 2.065 around for a while to maintain existing code till the transition is complete. And how do I integrate it with dub?
September 03, 2014
On 03/09/14 11:08, Chris wrote:

> If I install dmd 2.066 with dvm, it won't overwrite or change anything?

No, the whole idea is to have multiple compilers installed simultaneous.

> I'll soon be moving my code from 2.065 to 2.066, but I want to keep
> 2.065 around for a while to maintain existing code till the transition
> is complete.

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".

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 version

* <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"

-- 
/Jacob Carlborg
September 03, 2014
On Wednesday, 3 September 2014 at 13:10:28 UTC, Jacob Carlborg wrote:
> On 03/09/14 11:08, Chris wrote:
>
>> If I install dmd 2.066 with dvm, it won't overwrite or change anything?
>
> No, the whole idea is to have multiple compilers installed simultaneous.
>
>> I'll soon be moving my code from 2.065 to 2.066, but I want to keep
>> 2.065 around for a while to maintain existing code till the transition
>> is complete.
>
> 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 compilers.

Thanks also for the great tool. This will make the transition a lot easier.

> 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 version
>
> * <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"
September 03, 2014
On Wednesday, 3 September 2014 at 13:18:50 UTC, Chris wrote:
> On Wednesday, 3 September 2014 at 13:10:28 UTC, Jacob Carlborg wrote:
>> On 03/09/14 11:08, Chris wrote:
>>
>>> If I install dmd 2.066 with dvm, it won't overwrite or change anything?
>>
>> No, the whole idea is to have multiple compilers installed simultaneous.
>>
>>> I'll soon be moving my code from 2.065 to 2.066, but I want to keep
>>> 2.065 around for a while to maintain existing code till the transition
>>> is complete.
>>
>> 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 compilers.
>
> Thanks also for the great tool. This will make the transition a lot easier.
>
>> 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 version
>>
>> * <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:

ftp://ftp.digitalmars.com/dmd.2.065.0.zip

(cf. http://forum.dlang.org/thread/ebvumaoniuukgjbowxbz@forum.dlang.org)

But DVM tries to access it via http:

Fetching: http://ftp.digitalmars.com/dmd.2.065.zip
An unknown error occurred:
tango.core.Exception.IOException@/home/doob/development/d/tango/tango/core/Exception.d(59): The resource with URL "http://ftp.digitalmars.com/dmd.2.065.zip" could not be found.
September 03, 2014
On Wednesday, 3 September 2014 at 15:55:47 UTC, Chris wrote:
>
> Methinks DVM doesn't get it right. 2.065.zip is available here:
>
> ftp://ftp.digitalmars.com/dmd.2.065.0.zip
>
> (cf. http://forum.dlang.org/thread/ebvumaoniuukgjbowxbz@forum.dlang.org)
>
> But DVM tries to access it via http:
>
> Fetching: http://ftp.digitalmars.com/dmd.2.065.zip
> An unknown error occurred:
> tango.core.Exception.IOException@/home/doob/development/d/tango/tango/core/Exception.d(59): The resource with URL "http://ftp.digitalmars.com/dmd.2.065.zip" could not be found.

The link for 2.065 on http://dlang.org/changelog.html is broken
as well.  I don't think this particular issue can be blamed on
DVM.
« First   ‹ Prev
1 2 3 4