@Sönke Ludwig Sönke Ludwig authored on 19 Jan 2013
source Using the same path schema for temp exe files on Posix as on Windows. 12 years ago
LICENSE.txt Added license files. 12 years ago
LICENSE_DE.txt Added license files. 12 years ago
README.md Update README.md 12 years ago
package.json Fixed dependency. 12 years ago
README.md

dub package manager

Package and build manager for D applications and libraries.

Introduction

DUB emerged as a more general replacement for vibe.d's package manager. It does not imply a dependecy to vibe.d for packages and was extended to not only directly build projects, but also to generate project files (currently VisualD).

The project's pilosophy is to keep things as simple as possible. All that is needed to make a project a dub package is to write a short package.json file and put the source code into a source subfolder. It can then be registered on the public package registry to be made available for everyone. Any dependencies specified in package.json are automatically downloaded and made available to the project during the build process.

Future direction

To make things as flexible as they need to for certain projects, it is planned to gradually add more options to the package file format and eventually to add the possibility to specify an external build tool along with the path of it's output files. The idea is that DUB provides a convenient build management that suffices for 99% of projects, but is also usable as a bare package manager that doesn't get in your way if needed.

Installation

DUB comes precompiled for Windows, Mac OS, Linux and FreeBSD. It needs to have the following dependencies installed:

  • libevent 2.0.x
  • OpenSSL

The dub executable then just needs to be accessible from PATH and can be invoked from the root folder of any DUB enabled project to build and run it.