michaeltryby
commented
5 years ago Build steps: 1) clone epanet library dev branch 2) apply patches 3) generate build system 4) build libraries 5) copy dll, lib, and header files to epanet/toolkit and epanet/output 6) run python setup and build packages 7) upload build artifacts
The package build is currently performed manually. It requires the epanet-toolkit and epanet-output libraries to be built a priori. The required .dll, .lib, and .h files are then manually copied to the source directory for the module being built. Then the python packaging system is used to build the swig wrapper and create the package. This process need to be automated for easy packaging and distribution of the python modules.