Saker.build can be used to build project of any languages. From Java through C++, it can be used to create applications of any type. The different types can be even mixed in a single project.
The rich Java API of the build system allows implementing support for any use-case.
Every build tool claims that it's fast. Saker.build won't be the odd one out. It focuses on fast clean and incremental builds, reducing the build feedback cycle significantly.
We also made some performance measurements you can check out with pretty graphs showing the advantage.
As a plugin to saker.build, we've implemented improved Java compilation capabilities. With deep code and dependency analysis, the incremental and clean Java builds complete in fraction of the time compared to other build tools.
Saker.build supports automatic dispatching of your build tasks to other machines in your network. Throwing more hardware at the build process can easily reduce your build times.
See the performance comparison for build clusters using the MSVC C/C++ toolchain.
Visualize and analyze your builds to remove performance bottlenecks and discover the cause of errors. Build trace is a recording of your build execution that you can examine to improve your build process.
Extensibility is the core of saker.build. You can develop your own build tasks and even build languages for the build system.
The saker.nest repository helps the distribution of community packages as the default build system repository.
Eclipse is the first IDE to receive plugin support for saker.build. Build language content assist, outline, and extension API support help integration.
Java project configurations can be automatically applied based on the build tasks.
See the Eclipse plugin guide for more information.
Using these options for cross-compilation may cause runtime errors.
Build traces can be used to debug builds and find performance bottlenecks.
A question for which the answer is always...
See the archive for older posts.