Getting Started¶
If you haven't installed KISSB yet, visit the Installatino page and select your preferred method.
We are recommending to use the Wrapper script which will use a single file runtime of Kissb, which is the easiest way to use KISSB.
To test a simple build, create a folder, then install KISSB:
1 |
|
Build File¶
As with any build system, your build script is written in a text file, which is named after a convention. You can select between the following names:
- Recommended: kiss.build.tcl
- Alternatives: build.tcl, kissb.tcl or build.kissb.tcl
Create a file called kiss.build.tcl, with a line printing a message:
1 |
|
Now run kissb in your terminal:
1 2 3 4 |
|
You can see your script was run, and a warning was produced because no specific build target was passed
Build Targets¶
The standard usage of Kissb is to pass a build target, which is similar to make targets, or lifecycle targets in Gradle or Maven.
Build targets have no special lifecycle meaning in Kissb, users and/or package providers can define their own convention.
To add a target to your build file, use the "@" command:
1 2 3 4 5 |
|
Now run kissb again, passing the foo target:
1 2 3 4 5 6 |
|
Targets are very similar to simple build functions, but they offer a more evolved syntax to allow usages similar to make scenarios.
Add a new target bar which should run before foo:
1 2 3 4 5 6 7 8 9 |
|
Now run kissb again, passing the foo target:
1 2 3 4 5 6 7 8 9 10 |
|
Build Packages¶
At this point your build doesn't do anything special, and the KISSB core API doesn't provide any specific build mechanism for any languages.
However, a certain number of packages are available, which provide build commands and extensions for specific languages.
Local Script Libraries¶
Adding Local scripts and packages is one good way to create your own set of build commands and share them between projects.
There are multiple ways to load utility scripts, described on the Packages page