On Saturday, 22 February 2014 at 09:44:48 UTC, Sönke Ludwig wrote:
A new final release is ready. This one took a bit longer and
has more changes than usual:
After updating, to 0.9.21 dub generate visuald no longer
generates release and unittestconfigurations for VisualD -
only debug is
Am 22.02.2014 13:07, schrieb Sönke Ludwig:
Am 22.02.2014 12:24, schrieb Paulo Pinto:
Am 22.02.2014 10:44, schrieb Sönke Ludwig:
The Windows installer seems not to like being installed via UAC as the
Administrator gets the PATH configured, not the user that started the
installer.
--
Paulo
On 02/22/2014 10:44 AM, Sönke Ludwig wrote:
A new final release is ready. This one took a bit longer and has more
changes than usual:
(...)
Thanks for what looks like a great release!
The second feature planned is first class support for Dustmite -
(...)
Mostly welcomed. Dustmite is really
On 2/22/2014 6:44 PM, Sönke Ludwig wrote:
A new final release is ready. This one took a bit longer and has more
changes than usual:
Great job! Thanks for all the work you're putting into this.
Thanks for the great work!
On Saturday, 22 February 2014 at 09:44:48 UTC, Sönke Ludwig wrote:
A new final release is ready. This one took a bit longer and
has more changes than usual
https://www.archlinux.org/packages/community/x86_64/dub/
Am 22.02.2014 10:44, schrieb Sönke Ludwig:
A new final release is ready. This one took a bit longer and has more
changes than usual:
- Finally properly obeys the difference between target types
library, staticLibrary, dynamicLibrary and sourceLibrary.
By default, each library type
Am 22.02.2014 10:44, schrieb Sönke Ludwig:
A new final release is ready. This one took a bit longer and has more
changes than usual:
- Finally properly obeys the difference between target types
library, staticLibrary, dynamicLibrary and sourceLibrary.
By default, each library type
Congratulations for this new dub release.
Already uploaded new dub deb packages for this release at
http://d-apt.sourceforge.net/
--
Jordi Sayol
Am 22.02.2014 12:24, schrieb Paulo Pinto:
Am 22.02.2014 10:44, schrieb Sönke Ludwig:
The Windows installer seems not to like being installed via UAC as the
Administrator gets the PATH configured, not the user that started the
installer.
--
Paulo
Going by the installer script, it should
On Saturday, 22 February 2014 at 12:07:39 UTC, Sönke Ludwig wrote:
Am 22.02.2014 12:24, schrieb Paulo Pinto:
Am 22.02.2014 10:44, schrieb Sönke Ludwig:
The Windows installer seems not to like being installed via
UAC as the
Administrator gets the PATH configured, not the user that
started the
Am 27.01.2014 04:33, schrieb Jakob Ovrum:
On Wednesday, 15 January 2014 at 14:12:47 UTC, Sönke Ludwig wrote:
A new and hopefully last beta version of DUB 0.9.21 has been released:
http://forum.rejectedsoftware.com/groups/rejectedsoftware.dub/thread/826/
It contains some major new features, so
Am 27.01.2014 13:14, schrieb Sönke Ludwig:
- Use the closest matching import folder to infer the module name
instead of the first match (i.e. ./libev instead of . in this
case).
Implemented:
https://github.com/rejectedsoftware/dub/commit/5d0867fef7c6415e300c6ce214aa5790d0a2ca93
On Monday, 27 January 2014 at 12:38:06 UTC, Sönke Ludwig wrote:
Am 27.01.2014 13:14, schrieb Sönke Ludwig:
- Use the closest matching import folder to infer the module
name
instead of the first match (i.e. ./libev instead of .
in this
case).
Implemented:
On Monday, 27 January 2014 at 12:14:37 UTC, Sönke Ludwig wrote:
I understand that it is popular because a separate source or
src folder can be avoided*. But it really is quite unclean
considering how importing modules works in D.
* and it makes it harder for people to find the actual source
On Wednesday, 15 January 2014 at 14:12:47 UTC, Sönke Ludwig wrote:
A new and hopefully last beta version of DUB 0.9.21 has been
released:
http://forum.rejectedsoftware.com/groups/rejectedsoftware.dub/thread/826/
It contains some major new features, so extensive testing is
needed to get a
The bug turned out to be me not using importPaths correctly,
so my bad.
On Friday, 10 January 2014 at 18:48:11 UTC, Atila Neves wrote:
I finally got around to cloning the git repo and trying the
latest dub and how dub test would work.
1st of all there is a bug, should I also add it to the
Am 09.12.2013 18:29, schrieb Kapps:
On Monday, 9 December 2013 at 12:46:00 UTC, Kapps wrote:
I was looking for something similar to dub test and am glad to see it
added, but I can't seem to figure out how to get it to do anything at
all.
Okay, it seems that this was just an issue with the
On Wednesday, 11 December 2013 at 09:51:37 UTC, Sönke Ludwig
wrote:
The latest GIT master version now works without requiring a
main file.
Regarding integration with tested, what should work now is to
import
the automatically generated module test_main and use that as
the
testing root:
On Wednesday, 11 December 2013 at 22:13:59 UTC, Kapps wrote:
I noticed that the main file generated seems to already support
tested integration automatically which I find quite nice.
Unfortunately it seems that tested is not actually following
imports so both the above sample and the
I was looking for something similar to dub test and am glad to
see it added, but I can't seem to figure out how to get it to do
anything at all.
In particular, I'm trying to give tested a try as it seems
quite nice and I was looking for an automated way to generate
computer-readable test
On Monday, 9 December 2013 at 12:46:00 UTC, Kapps wrote:
I was looking for something similar to dub test and am glad to
see it added, but I can't seem to figure out how to get it to
do anything at all.
Okay, it seems that this was just an issue with the beta.
Building from git master allows
Am 03.12.2013 19:52, schrieb Jacob Carlborg:
On 2013-12-02 10:10, Sönke Ludwig wrote:
Using dub test --main-file= See also dub test --help.
* Can this be specified in the package.json file so invoking dub test
will always use a custom main file?
Not in a nice way, but I'd suggest we
On 2013-12-04 10:57, Sönke Ludwig wrote:
Not in a nice way, but I'd suggest we do something like making dub
test look for a configuration named unittest before trying to
generate its own custom main.
That would be nice to have.
It does already: dub test -- args...
Cool.
--
/Jacob
It also supports setting a custom file containing main(), so
that for
example custom unit test runners can be specified and similar
Awesome!
things. In
this case, the generated file looks like this:
---
module test_main;
import library_name.main_module;
import custom_main_module;
---
For
Am 03.12.2013 10:34, schrieb Atila Neves:
It also supports setting a custom file containing main(), so that for
example custom unit test runners can be specified and similar
Awesome!
things. In
this case, the generated file looks like this:
---
module test_main;
import
On 2013-12-02 10:10, Sönke Ludwig wrote:
Using dub test --main-file= See also dub test --help.
* Can this be specified in the package.json file so invoking dub test
will always use a custom main file?
* Don't know how it works now but it would be nice if dub could pass all
remaining
Am 02.12.2013 08:32, schrieb Jacob Carlborg:
On 2013-11-30 21:48, Sönke Ludwig wrote:
Based on the bug reports so far, I've prepared a new beta release of
0.9.21 for testing. Apart from fixes for the reported issues, it
contains a revamped command line interface with detailed help for each
On 2013-12-02 09:10, Sönke Ludwig wrote:
It's similar. By default, for library projects, it generates a maim
module of the form
---
module test_main;
import library_name.main_module;
import std.stdio;
import core.runtime;
void main() { writeln(All unit tests were successful.); }
---
and runs
Am 02.12.2013 09:19, schrieb Jacob Carlborg:
On 2013-12-02 09:10, Sönke Ludwig wrote:
It's similar. By default, for library projects, it generates a maim
module of the form
---
module test_main;
import library_name.main_module;
import std.stdio;
import core.runtime;
void main() {
On 2013-12-02 10:10, Sönke Ludwig wrote:
It errors out. An alternative would be to put _all_ source files as
static imports into the generated module, but the main file will also be
required for dependency based builds (--rdmd and possibly for DUB's own
build system, once partial rebuilds
Am 02.12.2013 17:01, schrieb Jacob Carlborg:
On 2013-12-02 10:10, Sönke Ludwig wrote:
It errors out. An alternative would be to put _all_ source files as
static imports into the generated module, but the main file will also be
required for dependency based builds (--rdmd and possibly for
On 2013-12-02 21:51, Sönke Ludwig wrote:
I need to dig up the old discussions about this topic, I just seemed to
remember that we reached a conclusion to require a root file also for
libraries, but you are right that technically it's not required in this
case (as in the the suggested
On 2013-11-30 21:48, Sönke Ludwig wrote:
Based on the bug reports so far, I've prepared a new beta release of
0.9.21 for testing. Apart from fixes for the reported issues, it
contains a revamped command line interface with detailed help for each
command and also the new dub test command.
Based on the bug reports so far, I've prepared a new beta release of
0.9.21 for testing. Apart from fixes for the reported issues, it
contains a revamped command line interface with detailed help for each
command and also the new dub test command.
http://code.dlang.org/download
On Saturday, 30 November 2013 at 20:49:14 UTC, Sönke Ludwig wrote:
Based on the bug reports so far, I've prepared a new beta
release of
0.9.21 for testing. Apart from fixes for the reported issues, it
contains a revamped command line interface with detailed help
for each
command and also the
36 matches
Mail list logo
