Dub and compilation

[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 .a file, no .so file.

Cargo downloads source to the cache but compiles to the project area,
separating debug and release builds. Each project has it's own
compilation of the shared source.

I believe Cargo has this right and Dub has this wrong. So wrong that
SCons, CMake, and Meson have a strong role in the D world. As it
stands, Dub is fine for fetching dependencies and then has no more role
to play in the build of a project. Actually then the Dub command has no
useful role since it may well be better for the build tools to just use
the Dub repository API directly.

Unless I have misunderstood Dub, or someone is fixing it.

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder at ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel at winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.puremagic.com/pipermail/digitalmars-d-learn/attachments/20170411/6410f50b/attachment.sig>