Re: DUB 0.9.13 released

2013-04-26 Thread alex

On Tuesday, 16 April 2013 at 21:50:10 UTC, Sönke Ludwig wrote:

Changes:

 - Support for a new "buildRequirements" field to be able to 
specify

   things like "Don't treat warnings as errors" or "Allow use of
   deprecated features"

 - A lot of improvements to the VisualD project generator

 - Some important bug fixes


Change log:
  
https://github.com/rejectedsoftware/dub/blob/master/CHANGELOG.md


Download:
  http://registry.vibed.org/download


I want to inform you that Mono-D v0.5.2.4 can open Dub projects 
natively now - no need for creating .dproj files explicitly 
anymore, just opening package.json is required in order to have 
the project there.

It also handles include paths in the most common cases.

Btw, what about nested dependencies? How are they handled in dub? 
Are all sub-packages in the .dub folder read for further 
dependency information?


Great work though!


Re: DUB 0.9.13 released

2013-04-26 Thread Sönke Ludwig
Am 26.04.2013 21:37, schrieb alex:
> 
> I want to inform you that Mono-D v0.5.2.4 can open Dub projects natively
> now - no need for creating .dproj files explicitly anymore, just opening
> package.json is required in order to have the project there.
> It also handles include paths in the most common cases.

Cool! I'll try that out tomorrow. Do you execute the "dub" binary to
generate a project file or do you parse the "package.json" directly? If
it helps, it would be relatively easy to add a mode where all build
settings for the project, including all of its dependencies, are output
to stdout as JSON.

> Btw, what about nested dependencies? How are they handled in dub? Are
> all sub-packages in the .dub folder read for further dependency
> information?

Yes, the ones in ".dub", in the system- and user-wide package folders,
as well as any package added with "dub add-local" are scanned for
matches recursively and their build settings are merged-in accordingly.

> Great work though!

Thanks, the same must be said about Mono-D! (which is a lot more
complex, of course)


Re: DUB 0.9.13 released

2013-04-26 Thread alex

On Friday, 26 April 2013 at 20:16:15 UTC, Sönke Ludwig wrote:

Am 26.04.2013 21:37, schrieb alex:


I want to inform you that Mono-D v0.5.2.4 can open Dub 
projects natively
now - no need for creating .dproj files explicitly anymore, 
just opening

package.json is required in order to have the project there.
It also handles include paths in the most common cases.


Cool! I'll try that out tomorrow. Do you execute the "dub" 
binary to
generate a project file or do you parse the "package.json" 
directly? If
it helps, it would be relatively easy to add a mode where all 
build
settings for the project, including all of its dependencies, 
are output

to stdout as JSON.


It parses the package.json directly, no .sln or .dproj is 
generated. It runs dub build for building and dub for executing 
the program -- where do I specify run arguments btw?




Btw, what about nested dependencies? How are they handled in 
dub? Are

all sub-packages in the .dub folder read for further dependency
information?


Yes, the ones in ".dub", in the system- and user-wide package 
folders,
as well as any package added with "dub add-local" are scanned 
for


where is the list of packages added with 'add-local' stored at?

matches recursively and their build settings are merged-in 
accordingly.


I think I might open up all the dependency projects as well when 
opening the 'root' package.json - do you think that it's a good 
idea or just distracting the user from the main project?





Great work though!


Thanks, the same must be said about Mono-D! (which is a lot more
complex, of course)


:-)


Re: DUB 0.9.13 released

2013-04-26 Thread Rory McGuire
I'd say opening all dependencies is distracting. But being able to open
them quickly is really useful.

On Fri, Apr 26, 2013 at 10:26 PM, alex  wrote:

> On Friday, 26 April 2013 at 20:16:15 UTC, Sönke Ludwig wrote:
>
>> Am 26.04.2013 21:37, schrieb alex:
>>
>>>
>>> I want to inform you that Mono-D v0.5.2.4 can open Dub projects natively
>>> now - no need for creating .dproj files explicitly anymore, just opening
>>> package.json is required in order to have the project there.
>>> It also handles include paths in the most common cases.
>>>
>>
>> Cool! I'll try that out tomorrow. Do you execute the "dub" binary to
>> generate a project file or do you parse the "package.json" directly? If
>> it helps, it would be relatively easy to add a mode where all build
>> settings for the project, including all of its dependencies, are output
>> to stdout as JSON.
>>
>
> It parses the package.json directly, no .sln or .dproj is generated. It
> runs dub build for building and dub for executing the program -- where do I
> specify run arguments btw?
>
>
>
>>  Btw, what about nested dependencies? How are they handled in dub? Are
>>> all sub-packages in the .dub folder read for further dependency
>>> information?
>>>
>>
>> Yes, the ones in ".dub", in the system- and user-wide package folders,
>> as well as any package added with "dub add-local" are scanned for
>>
>
> where is the list of packages added with 'add-local' stored at?
>
>
>  matches recursively and their build settings are merged-in accordingly.
>>
>
> I think I might open up all the dependency projects as well when opening
> the 'root' package.json - do you think that it's a good idea or just
> distracting the user from the main project?
>
>
>
>>  Great work though!
>>>
>>
>> Thanks, the same must be said about Mono-D! (which is a lot more
>> complex, of course)
>>
>
> :-)
>


Re: DUB 0.9.13 released

2013-04-26 Thread alex

On Friday, 26 April 2013 at 20:47:42 UTC, Rory McGuire wrote:
I'd say opening all dependencies is distracting. But being able 
to open

them quickly is really useful.


I think I should create greyed-out references in the 
pseudo-solution which can be enabled and loaded afterwards if 
wanted. Or so..


Re: DUB 0.9.13 released

2013-04-29 Thread Tyro[17]

On 4/16/13 5:49 PM, Sönke Ludwig wrote:

Changes:

  - Support for a new "buildRequirements" field to be able to specify
things like "Don't treat warnings as errors" or "Allow use of
deprecated features"

  - A lot of improvements to the VisualD project generator

  - Some important bug fixes


Change log:
   https://github.com/rejectedsoftware/dub/blob/master/CHANGELOG.md

Download:
   http://registry.vibed.org/download



Probably a stupid question but can DUB be used to install DMD? 
Instructions please.


Thanks


Re: DUB 0.9.13 released

2013-04-29 Thread Jonathan M Davis
On Monday, April 29, 2013 21:27:48 Tyro[17] wrote:
> On 4/16/13 5:49 PM, Sönke Ludwig wrote:
> > Changes:
> >   - Support for a new "buildRequirements" field to be able to specify
> >   
> > things like "Don't treat warnings as errors" or "Allow use of
> > deprecated features"
> >   
> >   - A lot of improvements to the VisualD project generator
> >   
> >   - Some important bug fixes
> > 
> > Change log:
> >https://github.com/rejectedsoftware/dub/blob/master/CHANGELOG.md
> > 
> > Download:
> >http://registry.vibed.org/download
> 
> Probably a stupid question but can DUB be used to install DMD?
> Instructions please.

There is no dub build for dmd. dmd is built using makefiles, and it really 
needs the druntime, Phobos, and tools projects as well (all of which build 
with makefiles) - especially if you're going to install it - and dub does not 
currently support building with makefiles or including other projects like 
that. It also doesn't support installing anything AFAIK. It just builds stuff 
with the bonus that it'll download and build the dependencies for you first. It 
may be possible for dub to do all of that in the future, but not now.

- Jonathan M Davis