Welcome to Bud
This is a tool to assist developers in building applications written in the D Language. It's main purpose is to reduce the need for developers to keep track of which files are needed to be compiled and/or linked to form either an execuable file or library file.
The discussion forum is a valuable source of information and feedback too.
The latest downloads (Version 3.04 - October 16th, 2006) are
- Windows Executable (without debug code)
- Windows Executable (with debug code)
- Source files
NOTE: Needs D v0.163 or higher to compile
UPDATE on 01 March 2011: here is a port of the 3.04 files to D2, tested only on Linux and Mac OSX x86_64, but might work on Windows too.
Compilation on Unix
If you have no existing binary, the executable must be built with the makefile first:
make -f Makefile.unix
It is still imperative to build a final binary with the utility itself:
./build build -full -op ln -s build bud
Most developers coming from C/C++ are familiar with the need for makefiles when building applications that have more than a couple of files involved. The usual process would be that whenever a new source file was created for the application, the developer would also update the makefile file to add then new file's name to the list of files needed to build the application. This is extra housekeeping for the developer, and as such is a chore and is occasionally overlooked.
Bud eases this chore by examining the source files on its command line and determines all specific files are actually needed by the application, and whether or not they need recompiling. After doing this, it then launches the compiler, linker, and librarian as required to build the intended target file. No makefiles are required.
Bud is very flexible and its behaviour can be controlled by various command line switches and configuration files.
The utility's main documentation describes the functions and options in much greater detail, so I'll just give a brief outline here of typical usages.
The common usage for Bud is just to name the top most file in the application's hierarchy of source files on its command line.
This will cause the utility to inspect the file myapp.d for references to other source files, such as import and pragma statements. It does this recursively to find all the files needed for the application. It then checks each of these files to see if their compiled version is up-to-date with respect to the target file. In most cases, the target is the executable file you are trying to build, but this may also be a library you are building. For each file that is not up-to-date, it adds it to the list of files to compile. After all needed files are checked it launches the compiler (if required) to create object files, and then, in the case of an executable target, launches the linker. If building a library it launches the librarian instead of the linker.
Commonly Used Switches
-cleanup Ensures that all working files created during the run are removed. -full Causes all source files, except ignored modules, to be compiled. -info Displays the version and path of the Bud application -names Displays the names of the files used in building the target. -noautoimport Prevents source file paths from being added to the list of Import Roots -obj Just creates object files. No linker or librarian is launched. -od Nominates the temporary file directory. -run Runs the application after successful linking. -silent Prevents unnecessary messages being displayed. -T<name> Identifies the target name to Bud. -test Does a test run only. No compiling, linking or library work is done. -V Set verbose mode on for just Bud and not for the compiler -X<name> Identifies a module or package to ignore
- bud-3-1.04-ported-to-D2.tar.gz (98.0 kB) -
This is the bud-3-1.04 files but now ported to D2, 01march2011. Tested on Mac and Linux x86_64., added by jaye on 03/01/11 18:19:24.