<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tazel, branch ci/dokka</title>
<subtitle>A build system and package manager for C, C++, Objective-C, Objective-C++ and Zig, with Kotlin project files.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/'/>
<entry>
<title>Merge branch 'main' into ci/dokka</title>
<updated>2026-11-15T16:33:02+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-15T16:33:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=8e3629745e8a57cb5290d2951a93cdfcd500f8a9'/>
<id>8e3629745e8a57cb5290d2951a93cdfcd500f8a9</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #11 from Progmasoft/legal/mit</title>
<updated>2026-11-15T16:32:00+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-15T16:32:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=584c52693097e039291321f787079145d76a3cdd'/>
<id>584c52693097e039291321f787079145d76a3cdd</id>
<content type='text'>
License tazel under MIT</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
License tazel under MIT</pre>
</div>
</content>
</entry>
<entry>
<title>Build the Dokka reference in CI</title>
<updated>2026-11-15T14:31:05+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T14:31:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=d7773dce6f8557698c72ca1e1f1daffbe4806d68'/>
<id>d7773dce6f8557698c72ca1e1f1daffbe4806d68</id>
<content type='text'>
Dokka 2.3.0 builds one HTML reference of the plugin API and the Gradle
plugin (build/dokka/html), and the CLI module on its own. Every Dokka
warning fails.

- tazel-api and tazel-gradle-plugin also fail on an undocumented public
  declaration. Their remaining 41 declarations are documented: the members
  of BuildStep, BuildContext, CapturedRun, Host, ExtensionScope,
  ExtensionHost, ProjectPlugin, ProjectPluginContext and ProjectSummary,
  OperatingSystem and Architecture, and the task inputs, constants and
  settings of the Gradle plugin.
- The CLI does not report undocumented declarations yet: 300, most of
  them members of the project-file DSL, which get their own change.
- Two KDoc links that pointed at parameters of another function are
  rewritten.
- CI runs Dokka on Linux and keeps the HTML.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Dokka 2.3.0 builds one HTML reference of the plugin API and the Gradle
plugin (build/dokka/html), and the CLI module on its own. Every Dokka
warning fails.

- tazel-api and tazel-gradle-plugin also fail on an undocumented public
  declaration. Their remaining 41 declarations are documented: the members
  of BuildStep, BuildContext, CapturedRun, Host, ExtensionScope,
  ExtensionHost, ProjectPlugin, ProjectPluginContext and ProjectSummary,
  OperatingSystem and Architecture, and the task inputs, constants and
  settings of the Gradle plugin.
- The CLI does not report undocumented declarations yet: 300, most of
  them members of the project-file DSL, which get their own change.
- Two KDoc links that pointed at parameters of another function are
  rewritten.
- CI runs Dokka on Linux and keeps the HTML.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>License tazel under MIT</title>
<updated>2026-11-15T10:57:38+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T10:57:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=a8e418e8b8ce40e71b91fd3d5cbf6dd44379dd65'/>
<id>a8e418e8b8ce40e71b91fd3d5cbf6dd44379dd65</id>
<content type='text'>
Every Progmasoft file of the repository moves from MPL-2.0 WITH
AdditionRef-Progmasoft-Exception-2.0 to MIT: LICENSE.txt is the MIT
text, every SPDX-License-Identifier and the POM license of every
publication say MIT, the README and the changelog say so, and LICENSES/
with the exception text goes.
The core, the Plugin API and the Gradle plugin are all MIT; the API's
POM already named its license and the Gradle plugin's publications now
name it too. Third-party files, such as the Gradle
wrapper, keep their licenses. Every commit to Progmasoft's files is the
maintainer's own.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Every Progmasoft file of the repository moves from MPL-2.0 WITH
AdditionRef-Progmasoft-Exception-2.0 to MIT: LICENSE.txt is the MIT
text, every SPDX-License-Identifier and the POM license of every
publication say MIT, the README and the changelog say so, and LICENSES/
with the exception text goes.
The core, the Plugin API and the Gradle plugin are all MIT; the API's
POM already named its license and the Gradle plugin's publications now
name it too. Third-party files, such as the Gradle
wrapper, keep their licenses. Every commit to Progmasoft's files is the
maintainer's own.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #9 from Progmasoft/docs/no-former-language</title>
<updated>2026-11-15T09:15:46+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-15T09:15:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=dd97353d89e50dff1ec6431699acf7e8a5d327b7'/>
<id>dd97353d89e50dff1ec6431699acf7e8a5d327b7</id>
<content type='text'>
Describe tazel-legacy without the language it served</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Describe tazel-legacy without the language it served</pre>
</div>
</content>
</entry>
<entry>
<title>Describe tazel-legacy without the language it served</title>
<updated>2026-11-15T09:07:25+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T09:07:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=61ed79e4d62b91093882261184b30c5f516f40fe'/>
<id>61ed79e4d62b91093882261184b30c5f516f40fe</id>
<content type='text'>
The README names the earlier Tazel by its versions only (0.1.0 to 0.4.0.3) and points to Progmasoft/tazel-legacy.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The README names the earlier Tazel by its versions only (0.1.0 to 0.4.0.3) and points to Progmasoft/tazel-legacy.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #8 from Progmasoft/feature/fmt-lint-compile-commands</title>
<updated>2026-11-13T18:38:00+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-13T18:38:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=11af82b954a1e35db371dc049a2c8bc153a1bf21'/>
<id>11af82b954a1e35db371dc049a2c8bc153a1bf21</id>
<content type='text'>
Add tazel fmt, tazel lint and the compilation database</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add tazel fmt, tazel lint and the compilation database</pre>
</div>
</content>
</entry>
<entry>
<title>Add tazel fmt, tazel lint and the compilation database</title>
<updated>2026-11-13T17:34:58+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-13T17:34:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=3f1a5ace6dc7bfea240f07e3c6fb84de25e6c582'/>
<id>3f1a5ace6dc7bfea240f07e3c6fb84de25e6c582</id>
<content type='text'>
tazel fmt formats the files the selected targets own (sources less
excludes, the headers below their header directories, textual headers)
on every triple they are built for: clang-format for the four C-family
languages, zig fmt for Zig. --check reports and changes nothing.

tazel lint plans the selected targets for one triple and mode, stages
their headers, and writes compile_commands.json with the compile command
tazel build runs (less -MD -MF) to the output root and to
.tazel/compile_commands.json. It then runs clang-tidy on each C-family
translation unit of the selected targets in the job pool; --fix runs one
unit at a time so fixes to a shared header do not race. Zig targets are
skipped with a note.

--check belongs to fmt and --fix to lint; what follows -- goes to the
tool. The tests use the clang-format and clang-tidy of the machine and
return early without them.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
tazel fmt formats the files the selected targets own (sources less
excludes, the headers below their header directories, textual headers)
on every triple they are built for: clang-format for the four C-family
languages, zig fmt for Zig. --check reports and changes nothing.

tazel lint plans the selected targets for one triple and mode, stages
their headers, and writes compile_commands.json with the compile command
tazel build runs (less -MD -MF) to the output root and to
.tazel/compile_commands.json. It then runs clang-tidy on each C-family
translation unit of the selected targets in the job pool; --fix runs one
unit at a time so fixes to a shared header do not race. Zig targets are
skipped with a note.

--check belongs to fmt and --fix to lint; what follows -- goes to the
tool. The tests use the clang-format and clang-tidy of the machine and
return early without them.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #7 from Progmasoft/feature/tazel-test</title>
<updated>2026-11-13T16:19:35+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-13T16:19:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=3875d3db9770344da6dd668a8de6ec898e9cdb4d'/>
<id>3875d3db9770344da6dd668a8de6ec898e9cdb4d</id>
<content type='text'>
Run test targets with tazel test</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Run test targets with tazel test</pre>
</div>
</content>
</entry>
<entry>
<title>Run test targets with tazel test</title>
<updated>2026-11-13T04:10:08+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-13T04:10:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=8003318ad262d37f8c3fe29dd4f13937e7b2d309'/>
<id>8003318ad262d37f8c3fe29dd4f13937e7b2d309</id>
<content type='text'>
  tazel test [--release] [labels...] [-- arguments for every test]

The test targets are built like any other, then run as the accepted
DSL describes, close to Bazel's cc_test:

- Each test runs in its output directory, beside the data files copied
  there, with its args, then the arguments after --, and its env, plus
  TEST_TARGET and a clean TEST_TMPDIR.
- shards = N runs it N times with TEST_TOTAL_SHARDS and TEST_SHARD_INDEX;
  each shard has its own log (test.shard-K-of-N.log, else test.log).
- The timeout is its own or the one of its size (1, 5, 15, 60 minutes);
  a test still running then is stopped with its children: TIMEOUT.
- flaky = true runs a failing test up to three times; passing after a
  failure is FLAKY, which counts as passed.
- EXCLUSIVE tests run alone, after the others run in parallel; MANUAL
  tests run only when their label is named, never through a pattern.
- A test that passed is not run again while the digest of its program,
  its data files, its arguments, its env, its shards and its timeout are
  the same (CACHED), unless it is tagged NO_CACHE.
- A failed test shows the end of its log and where the log is; the
  command exits with 1 when any test failed. Only this machine's triple
  is tested.

Processes gets runLogged, which writes output to a file and enforces a
time limit. Durations are printed without the locale.

TestCommandTest builds C tests with the compiler of the machine and
checks a passing test with data, args and env, a failing one, a flaky
one, a sharded one, a test that hangs, MANUAL tests left out of
patterns, cached results, and that other arguments are another run.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  tazel test [--release] [labels...] [-- arguments for every test]

The test targets are built like any other, then run as the accepted
DSL describes, close to Bazel's cc_test:

- Each test runs in its output directory, beside the data files copied
  there, with its args, then the arguments after --, and its env, plus
  TEST_TARGET and a clean TEST_TMPDIR.
- shards = N runs it N times with TEST_TOTAL_SHARDS and TEST_SHARD_INDEX;
  each shard has its own log (test.shard-K-of-N.log, else test.log).
- The timeout is its own or the one of its size (1, 5, 15, 60 minutes);
  a test still running then is stopped with its children: TIMEOUT.
- flaky = true runs a failing test up to three times; passing after a
  failure is FLAKY, which counts as passed.
- EXCLUSIVE tests run alone, after the others run in parallel; MANUAL
  tests run only when their label is named, never through a pattern.
- A test that passed is not run again while the digest of its program,
  its data files, its arguments, its env, its shards and its timeout are
  the same (CACHED), unless it is tagged NO_CACHE.
- A failed test shows the end of its log and where the log is; the
  command exits with 1 when any test failed. Only this machine's triple
  is tested.

Processes gets runLogged, which writes output to a file and enforces a
time limit. Durations are printed without the locale.

TestCommandTest builds C tests with the compiler of the machine and
checks a passing test with data, args and env, a failing one, a flaky
one, a sharded one, a test that hangs, MANUAL tests left out of
patterns, cached results, and that other arguments are another run.
</pre>
</div>
</content>
</entry>
</feed>
