The d code was ported from the original C++ implementation which is WIP too.
- Why dlang? Because to better achieve the goals defined as "the code to be more modular, extensible, and easier to maintain", I think dlang is superior to C++ in many ways.
- I would happily transfer the ownership of the repo to OpenWaterAnalytics on request.
- The example inp files were successfully tested
- The output binary file generation must be tested (The Link and Node results seem fine in terms of both reading and writing).
- only the d standard library phobos.
You need any d compiler and dub (the D language's official package manager) which is usually shipped with the compilers.
cd into the project root, and type:
for command line executable:
dub build --config=cli
for dynamic library:
dub build --config=dynamicLibrary
for static library:
dub build
To compile release versions, append -b release to the end of the dub command.
The D runtime and Phobos must be explicitly linked. For instance in a Windows machine below C code must be compiled with:
cl phobos2-ldc.lib druntime-ldc.lib epanet3.lib main.c
// main.c
#include <stdio.h>
#include "epanet3.h"
int main() {
EN_runEpanet("net1.inp", "out1", "out2");
printf("done!");
return 0;
}The dynamic library can also be loaded instead of static linking. Take a look at the python folder.