I just released a new version of DVM, 0.4.0. The only thing new in this release in the "compile" command. This allows to compile DMD, druntime and Phobos from github. Create a folder, clone DMD, druntime and Phobos in the newly create folder, run "dvm compile folder" to compile everything. The compiler is placed in the DMD directory.

For installation instructions see: https://bitbucket.org/doob/dvm

Changelog:

Version 0.4.0
  New/Change Features
    * Added a "compile" command for compiling DMD, druntime and Phobos from github

-- 
/Jacob Carlborg

On 06/01/2012 21:29, Jacob Carlborg wrote:
> I just released a new version of DVM, 0.4.0. The only thing new in this
> release in the "compile" command. This allows to compile DMD, druntime
> and Phobos from github. Create a folder, clone DMD, druntime and Phobos
> in the newly create folder, run "dvm compile folder" to compile
> everything. The compiler is placed in the DMD directory.
>
> For installation instructions see: https://bitbucket.org/doob/dvm
>
> Changelog:
>
> Version 0.4.0
> New/Change Features
> * Added a "compile" command for compiling DMD, druntime and Phobos from
> github
>

This is excellent, can't wait to try it out!

Would it be possible to get something like this working?

$ dvm install git-master # install everything from git master
$ dvm update git-master  # update to the latest dmd/druntime/phobos
                         # revision
$ dvm use git-master     # switch to git master

-- 
Robert
http://octarineparrot.com/

"Jacob Carlborg" <doob@me.com> wrote in message news:je7p3p$1pl1$1@digitalmars.com...
>I just released a new version of DVM, 0.4.0. The only thing new in this release in the "compile" command. This allows to compile DMD, druntime and Phobos from github. Create a folder, clone DMD, druntime and Phobos in the newly create folder, run "dvm compile folder" to compile everything. The compiler is placed in the DMD directory.
>

In other words:

$ git clone https://github.com/D-Programming-Language/dmd.git
$ git clone https://github.com/D-Programming-Language/druntime.git
$ git clone https://github.com/D-Programming-Language/phobos.git
$ git clone https://github.com/D-Programming-Language/tools.git  # for RDMD,
but this is optional
$ dvm compile
$ ./dmd/bin32/dmd  # or ./dmd/bin64/dmd
DMD32 D Compiler v2.0...
...etc...

If you notice it downloading the latest DMD release before compiling, there's a reason for that: There are some files (from the bin and lib directories) that aren't in github, so it grabs them from the latest DMD release.

BTW, This isn't just for Git DMD, it can also recompile release versions of DMD:

$ wget https://github.com/downloads/D-Programming-Language/dmd/dmd.2.057.zip
$ unzip dmd.2.057.zip
$ dvm compile ./dmd2  # the directory is optional, DVM's default is "."
$ ./dmd2/linux/bin32/dmd   # or ./dmd2/osx/bin64/dmd, etc...

DVM will automatically detect whether you have a git-style or release-style project structure and act accordingly. Use DVM's -v (verbose) flag to see which it detects. It also detects D1 vs D2, so it can be used to compile D1/Phobos as well.

Be aware, it might have some trouble will really old releases of DMD 1 and 2 due to changes in the project structure and/or makefiles. But anything remotely recent should work fine (if not, please file a bug).

If you're on Windows, it will automatically download and install DMC if DMC isn't detected on the PATH (you can also do it with "dvm install dmc"). But you may run into some "paths with spaces" trouble with the DMC toolchain that I wasn't able to fully track down, so if that happens, you should download DMC to a directory with no spaces:

$ dvm fetch dmc

and extract/install it manually.

"Robert Clipsham" <robert@octarineparrot.com> wrote in message news:je7qkg$1s8f$1@digitalmars.com...
>
> Would it be possible to get something like this working?
>
> $ dvm install git-master # install everything from git master
> $ dvm update git-master  # update to the latest dmd/druntime/phobos
>                          # revision
> $ dvm use git-master     # switch to git master
>

Yea, both Jacob and I wanted to get that sort of thing in, and it shouldn't be too hard. But neither of us have quite gotten around to it yet.

On 2012-01-06 23:38, Nick Sabalausky wrote:
> "Jacob Carlborg"<doob@me.com>  wrote in message
> news:je7p3p$1pl1$1@digitalmars.com...
>> I just released a new version of DVM, 0.4.0. The only thing new in this
>> release in the "compile" command. This allows to compile DMD, druntime and
>> Phobos from github. Create a folder, clone DMD, druntime and Phobos in the
>> newly create folder, run "dvm compile folder" to compile everything. The
>> compiler is placed in the DMD directory.
>>
>
> In other words:
>
> $ git clone https://github.com/D-Programming-Language/dmd.git
> $ git clone https://github.com/D-Programming-Language/druntime.git
> $ git clone https://github.com/D-Programming-Language/phobos.git
> $ git clone https://github.com/D-Programming-Language/tools.git  # for RDMD,
> but this is optional
> $ dvm compile
> $ ./dmd/bin32/dmd  # or ./dmd/bin64/dmd
> DMD32 D Compiler v2.0...
> ...etc...
>
> If you notice it downloading the latest DMD release before compiling,
> there's a reason for that: There are some files (from the bin and lib
> directories) that aren't in github, so it grabs them from the latest DMD
> release.
>
> BTW, This isn't just for Git DMD, it can also recompile release versions of
> DMD:
>
> $ wget https://github.com/downloads/D-Programming-Language/dmd/dmd.2.057.zip
> $ unzip dmd.2.057.zip
> $ dvm compile ./dmd2  # the directory is optional, DVM's default is "."
> $ ./dmd2/linux/bin32/dmd   # or ./dmd2/osx/bin64/dmd, etc...
>
> DVM will automatically detect whether you have a git-style or release-style
> project structure and act accordingly. Use DVM's -v (verbose) flag to see
> which it detects. It also detects D1 vs D2, so it can be used to compile
> D1/Phobos as well.
>
> Be aware, it might have some trouble will really old releases of DMD 1 and 2
> due to changes in the project structure and/or makefiles. But anything
> remotely recent should work fine (if not, please file a bug).
>
> If you're on Windows, it will automatically download and install DMC if DMC
> isn't detected on the PATH (you can also do it with "dvm install dmc"). But
> you may run into some "paths with spaces" trouble with the DMC toolchain
> that I wasn't able to fully track down, so if that happens, you should
> download DMC to a directory with no spaces:
>
> $ dvm fetch dmc
>
> and extract/install it manually.
>
>

Thanks for the elaborated explanation.

-- 
/Jacob Carlborg

On 2012-01-07 00:58, Nick Sabalausky wrote:
> "Robert Clipsham"<robert@octarineparrot.com>  wrote in message
> news:je7qkg$1s8f$1@digitalmars.com...
>>
>> Would it be possible to get something like this working?
>>
>> $ dvm install git-master # install everything from git master
>> $ dvm update git-master  # update to the latest dmd/druntime/phobos
>>                           # revision
>> $ dvm use git-master     # switch to git master
>>
>
> Yea, both Jacob and I wanted to get that sort of thing in, and it shouldn't
> be too hard. But neither of us have quite gotten around to it yet.

I would really like to do a complete rewrite of the tool, the internals. Well actually more of a complete refactoring so DVM can be built as a library and the tool uses the library. This would make things like the above much easier to integrate.

-- 
/Jacob Carlborg

"Jacob Carlborg" <doob@me.com> wrote in message news:je9fbv$1heb$2@digitalmars.com...
> On 2012-01-07 00:58, Nick Sabalausky wrote:
>> "Robert Clipsham"<robert@octarineparrot.com>  wrote in message news:je7qkg$1s8f$1@digitalmars.com...
>>>
>>> Would it be possible to get something like this working?
>>>
>>> $ dvm install git-master # install everything from git master
>>> $ dvm update git-master  # update to the latest dmd/druntime/phobos
>>>                           # revision
>>> $ dvm use git-master     # switch to git master
>>>
>>
>> Yea, both Jacob and I wanted to get that sort of thing in, and it
>> shouldn't
>> be too hard. But neither of us have quite gotten around to it yet.
>
> I would really like to do a complete rewrite of the tool, the internals. Well actually more of a complete refactoring so DVM can be built as a library and the tool uses the library. This would make things like the above much easier to integrate.
>

Interesting. Do you have any sort of idea on when, or a rough roadmap? Or is it one of those "One of things days if I get around to it" sort of thing (that I'm all too familiar with myself!)?

"Nick Sabalausky" <a@a.a> wrote in message news:jeaaae$304r$1@digitalmars.com...
> "Jacob Carlborg" <doob@me.com> wrote in message news:je9fbv$1heb$2@digitalmars.com...
>>
>> I would really like to do a complete rewrite of the tool, the internals. Well actually more of a complete refactoring so DVM can be built as a library and the tool uses the library. This would make things like the above much easier to integrate.
>>
>
> Interesting. Do you have any sort of idea on when, or a rough roadmap? Or is it one of those "One of things days if I get around to it" sort of thing (that I'm all too familiar with myself!)?
>

I guess what I'm really getting at is: Is the refactoring you have in mind something that should ideally come before other new features? Or would that not really matter?

On 2012-01-07 21:39, Nick Sabalausky wrote:
> "Nick Sabalausky"<a@a.a>  wrote in message
> news:jeaaae$304r$1@digitalmars.com...
>> "Jacob Carlborg"<doob@me.com>  wrote in message
>> news:je9fbv$1heb$2@digitalmars.com...
>>>
>>> I would really like to do a complete rewrite of the tool, the internals.
>>> Well actually more of a complete refactoring so DVM can be built as a
>>> library and the tool uses the library. This would make things like the
>>> above much easier to integrate.
>>>
>>
>> Interesting. Do you have any sort of idea on when, or a rough roadmap? Or
>> is it one of those "One of things days if I get around to it" sort of
>> thing (that I'm all too familiar with myself!)?
>>
>
> I guess what I'm really getting at is: Is the refactoring you have in mind
> something that should ideally come before other new features? Or would that
> not really matter?

Ideally it should come before other new features. I mean, the more stuff we put in there the more mess it will be. The point of the refactoring is of course to make it easier to add new features and to understand the code.

I'm not really sure about the road map. I'm currently focusing on Orbit, the package manager I'm developing. Also the main goal of DVM is already done. Hopefully I can squeeze in some time to work on DVM before the first release of Orbit.

About the refactoring, what to you think about these:

* Move to git
* Move to github
* Port to D2, still using Tango

-- 
/Jacob Carlborg

"Jacob Carlborg" <doob@me.com> wrote in message news:jec1j6$2rbu$1@digitalmars.com...
>
> Ideally it should come before other new features. I mean, the more stuff we put in there the more mess it will be. The point of the refactoring is of course to make it easier to add new features and to understand the code.

Yea, that makes sense. I guess I just wasn't sure how "deep" the refactoring you were envisioning was going to be.

Something possibly releated I've been meaning to bring up: I've been thinking that DVM's commands and options should work more like, say, git or svn. By that I mean: Right now DVM has a set of commands, and a set of "global" DVM options. Problem is, some of the options only apply to some of the commands. This sugegsts a few changes:

1. "dvm --help" should only show globally-applicable options. (--verbose and --help are probably only ones right now.)

2. "dvm [command] --help" (and maybe "dvm --help [command]", too) should show a command-specific help screen.

This isn't a *huge* need right now, but I think it'll only become more and more important as DVM progresses. I don't know if this is something that should be taken into account in the refactoring, or just left until after.

Another thing that might need to be considered in the refactoring: On Linux, DVM doesn't currently work inside a shell script. It's just not recognized. I'm sure it probably has something to do with the "dvm" shell-function. Maybe it's because it's set to only be defined on interactive prompts? I don't really know for certain what the problem or the solution is, so depending on whatever the "right" solution is, this might be a "take into account in the refactoring" matter.


> About the refactoring, what to you think about these:
>
> * Move to git

I don't have a really strong opinion on that. While I kind of like Hg a little better, I normally use the Tortoise tools, and I like TortoiseGit much better than TortoiseHg. Also branching is built into Git rather than being a grafted-on extra, which is nice. (And of course, DVM goes hand-in-hand with DMD and DMD is Git). So I guess I would lean more towards Git, but either way works.


> * Move to github

It's ultimately up to you, but personally I can't stand Github. My vote would be to stick with Bitbucket.

Granted, I haven't actually tried Bitbucket's Git support yet. But just yesterday I started the process of converting a couple of my projects from SVN/Dsource to Git/Bitbucket, so we'll see how it goes, and I'll let you know.


> * Port to D2, still using Tango
>

I'm definitely in favor of switching to D2. In fact, I took the leap from D1/Tango straight to D2/Phobos on my own projects about a year or so ago, so I have some experience in that (and D2's only gotten better since), and I'd be happy to take the lead converting it to D2. I found that the vast majority of changes I needed to make were Tango->Phobos because, while there are some breaking changes from D1->D2, most of the changes are additive, and D1-style code works fine in D2 with only very little change.

As far as Tango: I have no idea what the state of D2's Tango is, and personally I'd prefer Phobos. But if you have reason to believe D2's Tango is ready to use and you'd prefer that, then I'm perfectly fine with it. Actually, heck, if we're going to switch to D2, we may as well at least give D2's Tango a try along the way. If it works, it works, if it doesn't we can help out D2's Tango or just do Phobos (especially since 2.058 will have that new curl module).