On 2017-03-20 10:07, Russel Winder via Digitalmars-d-learn wrote:
And different behaviour with different build options, at least when
using dmd, but I think the same is true for ldc2:
|> dub test
No source files found in configuration 'library'. Falling back to "dub -b
unittest".
Performing
On Mon, 2017-03-20 at 08:39 +, Russel Winder wrote:
> […]
> Actually it seems worse than that. Even with "dub -b unittest" it
> appears that Dub compiles main.d without the -unittest flag to ldc2
> and so the normal application runs.
And different behaviour with different build options, at
On Mon, 2017-03-20 at 00:58 -0700, Jonathan M Davis via Digitalmars-d-
learn wrote:
>
[…]
> I haven't spent the time to dig in and report it properly, but based
> on some
> of what I saw recently on a project I have, the module with main in
> it
> didn't have its tests run, as if dub's didn't
On Monday, March 20, 2017 07:51:09 Russel Winder via Digitalmars-d-learn
wrote:
> I have a Meson build for a D program project with a single main.d file
> that has some unit tests. Both executable and test executable are
> created and work as expected.
>
> I created a minimal Dub file for this
I have a Meson build for a D program project with a single main.d file
that has some unit tests. Both executable and test executable are
created and work as expected.
I created a minimal Dub file for this project. Using Dub the program
runs as expected. However when I run "dub test" it claims to
