On Tue, 2017-04-11 at 13:24 +, Mike Parker via Digitalmars-d-learn
wrote:
> On Tuesday, 11 April 2017 at 11:13:30 UTC, Russel Winder wrote:
>
> > This is not what seems to happen with unit-threaded. for the
> > directory ~/.dub/packages/unit-threaded-0.7.11/unit-threaded,
> > the tree is:
>
On Tuesday, 11 April 2017 at 11:13:30 UTC, Russel Winder wrote:
This is not what seems to happen with unit-threaded. for the
directory ~/.dub/packages/unit-threaded-0.7.11/unit-threaded,
the tree is:
Just to be clear -- is this what you see after compiling a
project that depends on unit-thre
On Tue, 2017-04-11 at 09:57 +0300, drug via Digitalmars-d-learn wrote:
>
[…]
> There is possibility to place binaries to specified directory using
> `targetPath` (see `Build settings` in Dub documentation)
That is fine for the project code, but doesn't help with the
dependencies.
--
Russel.
==
On Tue, 2017-04-11 at 06:45 +, Mike Parker via Digitalmars-d-learn
wrote:
>
[…]
> DUB downloads the source of dependencies from github and stores
> it all in the system cache. Each package has its own versioned
> folder in the cache and, when compiled, is given a .dub
> subdirectory in the
11.04.2017 08:15, Russel Winder via Digitalmars-d-learn пишет:
As I understand it, Dub compiles a downloaded dependency into the local
Dub cache. This means you cannot store a debug build and a release
build for multiple architectures and different compilers, at the same
time, and you only get a
On Tuesday, 11 April 2017 at 05:15:37 UTC, Russel Winder wrote:
As I understand it, Dub compiles a downloaded dependency into
the local Dub cache. This means you cannot store a debug build
and a release build for multiple architectures and different
compilers, at the same time, and you only get
