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.
Extensibility is the core of saker.build. You can develop your own build tasks or even build languages for the build system.
The saker.nest repository helps the distribution of community packages as the default build system repository.
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.
|Incremental Java builds||40||100|
|Distributed C++ build||70||100|
We'd spend our time writing code rather than watching it compile and believe you would too. Saker.build excels in running fast for clean and incremental builds alike!
It achieves this by parallelizing every build task that it can, and may also distribute the workload to other build machines.
Check out the performance measurements that we've made to get a clearer picture.
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.
Automatic syntax higlighting helps you read and write your build scripts more efficiently.
The script assistance features are available in the IDE with the saker.build plugins.
Hint: hover over this script with your mouse!
Content assistance is available in the build script editor of your favorite IDE.
Context driven completion proposals help you write build scripts faster while quick documentation helps you choose the appropriate build configuration.
Keep targetting older releases while keeping up with the new features.
IntelliJ support for the saker.build system has just been released.
Using these options for cross-compilation may cause runtime errors.
Build traces can be used to debug builds and find performance bottlenecks.
See the archive for older posts.