<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tazel, branch feature/tazel-test</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>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>
<entry>
<title>Merge pull request #6 from Progmasoft/feature/action-level-incremental</title>
<updated>2026-11-13T04:01:38+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-13T04:01:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=6bb2736f505c647d27f8d42bcb1f4b542c910e34'/>
<id>6bb2736f505c647d27f8d42bcb1f4b542c910e34</id>
<content type='text'>
Make builds incremental per action, by content</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Make builds incremental per action, by content</pre>
</div>
</content>
</entry>
<entry>
<title>Make Windows objects reproducible so early cutoff holds there</title>
<updated>2026-11-12T22:54:38+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-12T22:54:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=34acd40e7c520dda4addfc63ed3e26175fb399c5'/>
<id>34acd40e7c520dda4addfc63ed3e26175fb399c5</id>
<content type='text'>
The Windows runner showed that a comment in a header recompiled both
units and then archived and relinked, where Linux and macOS stopped
after the compiles. Clang stamps objects for Windows targets with the
time by default, and debug information there records the content of
every header, so the objects always differed.

- Clang gets -mno-incremental-linker-compatible for Windows targets:
  the same source gives the same object.
- The early-cutoff part of BuildCommandTest builds in release mode,
  without debug information, on every system.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The Windows runner showed that a comment in a header recompiled both
units and then archived and relinked, where Linux and macOS stopped
after the compiles. Clang stamps objects for Windows targets with the
time by default, and debug information there records the content of
every header, so the objects always differed.

- Clang gets -mno-incremental-linker-compatible for Windows targets:
  the same source gives the same object.
- The early-cutoff part of BuildCommandTest builds in release mode,
  without debug information, on every system.
</pre>
</div>
</content>
</entry>
<entry>
<title>Make builds incremental per action, by content</title>
<updated>2026-11-12T19:40:35+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-12T19:40:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=d73260a011d463f492448bc2e29aa46fba657326'/>
<id>d73260a011d463f492448bc2e29aa46fba657326</id>
<content type='text'>
Every compile, archive, link and Zig build is now an action: a command
line with its directory and environment, the files it reads and the
files it writes. ActionCache keeps a record beside the first output of
each action, with the digest of the action and the SHA-256 of every
input and output. An action runs again only when:

- its command line, directory or environment changed,
- a file it read has other content: the declared inputs, and what the
  compiler included, from the depfile it wrote,
- or an output is gone or no longer what the action wrote.

Files are compared by content, not by time. Touching a file reruns
nothing; a translation unit recompiled to the same object (a comment in
a header, say) reruns neither the archive nor the program that use it.
Digests are kept per build by size and modification time, so each file
is read once.

- Zig writes no depfile, so every .zig file beside and below the root
  file, and the libraries it links, are the inputs of a Zig build. It
  no longer runs on every build.
- Staged headers and data files are copied only when their bytes
  differ.
- The .cmd records and the time comparisons of UpToDate are gone.

Tests: the action cache (command, environment, touched, changed and
restored inputs, altered outputs, forgotten records) and, with the C
compiler of the machine, a touch that runs nothing, a comment in a
header that recompiles two units but does not archive or link, and a
change of code that recompiles, archives and relinks.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Every compile, archive, link and Zig build is now an action: a command
line with its directory and environment, the files it reads and the
files it writes. ActionCache keeps a record beside the first output of
each action, with the digest of the action and the SHA-256 of every
input and output. An action runs again only when:

- its command line, directory or environment changed,
- a file it read has other content: the declared inputs, and what the
  compiler included, from the depfile it wrote,
- or an output is gone or no longer what the action wrote.

Files are compared by content, not by time. Touching a file reruns
nothing; a translation unit recompiled to the same object (a comment in
a header, say) reruns neither the archive nor the program that use it.
Digests are kept per build by size and modification time, so each file
is read once.

- Zig writes no depfile, so every .zig file beside and below the root
  file, and the libraries it links, are the inputs of a Zig build. It
  no longer runs on every build.
- Staged headers and data files are copied only when their bytes
  differ.
- The .cmd records and the time comparisons of UpToDate are gone.

Tests: the action cache (command, environment, touched, changed and
restored inputs, altered outputs, forgotten records) and, with the C
compiler of the machine, a touch that runs nothing, a comment in a
header that recompiles two units but does not archive or link, and a
change of code that recompiles, archives and relinks.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #5 from Progmasoft/feature/build-c-family</title>
<updated>2026-11-12T19:36:11+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-12T19:36:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=86214c96285f73d352f934b0da33d231150898f0'/>
<id>86214c96285f73d352f934b0da33d231150898f0</id>
<content type='text'>
Build and run C, C++, Objective-C, Objective-C++ and Zig targets</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Build and run C, C++, Objective-C, Objective-C++ and Zig targets</pre>
</div>
</content>
</entry>
<entry>
<title>Build and run C, C++, Objective-C, Objective-C++ and Zig targets</title>
<updated>2026-11-12T19:19:46+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-12T19:19:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=7cb809c6560fc4ed29f41e4e4199cd91af6cbed1'/>
<id>7cb809c6560fc4ed29f41e4e4199cd91af6cbed1</id>
<content type='text'>
Tazel gets its first build commands:

  tazel build [--release] [--triple &lt;LLVM triple&gt;] [labels...]
  tazel run   [--release] [--triple &lt;LLVM triple&gt;] [label] [-- program arguments]

Without a label they take the package of the current directory. A
pattern skips targets not built for the triple; a label names one, or
it is an error. tazel run builds and runs one bin target with its args
and env from BUILD.kts, then the arguments after --.

- Plan (driver.BuildPlan): the selected targets and every library they
  depend on, configured once each for one triple and build mode, with
  link order (dependents before dependencies) and cycle detection.
  Dependencies from ViGet and local .vipkg files are refused with a
  message, since they are not built yet.
- Compilers (driver.CcToolchain): Clang, then GCC, then zig cc on PATH
  unless the target chooses one. Clang builds for other triples with
  --target, zig cc with its own triple spelling; GCC only for the host.
  MSVC and clang-cl are refused with a message for now.
- Commands (driver.CcCommands): standard, gnuExtensions, optimize and
  debugInfo with their mode defaults, warnings, warningsAsErrors,
  position-independent code (sharedlibs, and staticlibs a sharedlib
  links unless pic says otherwise), arc, sanitizers, LTO, public and
  private defines and headers with those of the libraries, headers
  staged under includePrefix/stripIncludePrefix, precompiledHeader as a
  forced include, flags; archives with llvm-ar or ar; links with
  alwaysLink as whole-archive, links, frameworks on macOS, rpath (and
  the directories of shared libraries), linkerScript, exports (version
  script or exported symbols), soVersion (soname and the unversioned
  name), defFile and subsystem on Windows, strip and linkFlags.
  Windows resource scripts are refused with a message for now.
- Zig targets run zig build-exe, build-lib (-dynamic) or test
  --test-no-exec on their root file, with the libraries they depend on.
- Incremental (driver.UpToDate): every compile writes a depfile (-MD
  -MF); an object is current while its command line is the same and no
  input in its depfile is newer. Archives and programs are remade when
  their command or an input changed. A failed command is redone.
- Jobs: the job pool and build graph of the legacy Tazel run the
  translation units in parallel (execution.jobs, keepGoing).
- data files are copied beside the output.

Tests: depfile reading, up-to-date decisions, globs and excludes, Zig
triples and output names, and a real build with the C compiler of the
machine: a first build, a build with nothing to do, a header change
that recompiles both units, tazel run with args, env and extra
arguments, and a compiler error.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Tazel gets its first build commands:

  tazel build [--release] [--triple &lt;LLVM triple&gt;] [labels...]
  tazel run   [--release] [--triple &lt;LLVM triple&gt;] [label] [-- program arguments]

Without a label they take the package of the current directory. A
pattern skips targets not built for the triple; a label names one, or
it is an error. tazel run builds and runs one bin target with its args
and env from BUILD.kts, then the arguments after --.

- Plan (driver.BuildPlan): the selected targets and every library they
  depend on, configured once each for one triple and build mode, with
  link order (dependents before dependencies) and cycle detection.
  Dependencies from ViGet and local .vipkg files are refused with a
  message, since they are not built yet.
- Compilers (driver.CcToolchain): Clang, then GCC, then zig cc on PATH
  unless the target chooses one. Clang builds for other triples with
  --target, zig cc with its own triple spelling; GCC only for the host.
  MSVC and clang-cl are refused with a message for now.
- Commands (driver.CcCommands): standard, gnuExtensions, optimize and
  debugInfo with their mode defaults, warnings, warningsAsErrors,
  position-independent code (sharedlibs, and staticlibs a sharedlib
  links unless pic says otherwise), arc, sanitizers, LTO, public and
  private defines and headers with those of the libraries, headers
  staged under includePrefix/stripIncludePrefix, precompiledHeader as a
  forced include, flags; archives with llvm-ar or ar; links with
  alwaysLink as whole-archive, links, frameworks on macOS, rpath (and
  the directories of shared libraries), linkerScript, exports (version
  script or exported symbols), soVersion (soname and the unversioned
  name), defFile and subsystem on Windows, strip and linkFlags.
  Windows resource scripts are refused with a message for now.
- Zig targets run zig build-exe, build-lib (-dynamic) or test
  --test-no-exec on their root file, with the libraries they depend on.
- Incremental (driver.UpToDate): every compile writes a depfile (-MD
  -MF); an object is current while its command line is the same and no
  input in its depfile is newer. Archives and programs are remade when
  their command or an input changed. A failed command is redone.
- Jobs: the job pool and build graph of the legacy Tazel run the
  translation units in parallel (execution.jobs, keepGoing).
- data files are copied beside the output.

Tests: depfile reading, up-to-date decisions, globs and excludes, Zig
triples and output names, and a real build with the C compiler of the
machine: a first build, a build with nothing to do, a header change
that recompiles both units, tazel run with args, env and extra
arguments, and a compiler error.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #4 from Progmasoft/feature/plugin-api-and-gradle-plugin</title>
<updated>2026-11-12T19:06:58+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-12T19:06:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=95cdafcf1aa01b5d32171c56e6a94137402643b9'/>
<id>95cdafcf1aa01b5d32171c56e6a94137402643b9</id>
<content type='text'>
Bring the plugin API and the Gradle plugin from the legacy Tazel</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Bring the plugin API and the Gradle plugin from the legacy Tazel</pre>
</div>
</content>
</entry>
<entry>
<title>Merge main into feature/plugin-api-and-gradle-plugin</title>
<updated>2026-11-12T15:54:01+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-12T15:54:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=9cff1e2b6a37959abc8a8b66946df61850a0aa47'/>
<id>9cff1e2b6a37959abc8a8b66946df61850a0aa47</id>
<content type='text'>
Keeps both changelog entries: Tazel Custom Commands and Options from
main, then the plugin API and the Gradle plugin.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Keeps both changelog entries: Tazel Custom Commands and Options from
main, then the plugin API and the Gradle plugin.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge pull request #3 from Progmasoft/feature/custom-commands-and-options</title>
<updated>2026-11-12T15:53:10+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-12T15:53:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=01036658064b95c24c1136d2bba9403c81c3337d'/>
<id>01036658064b95c24c1136d2bba9403c81c3337d</id>
<content type='text'>
Bring Tazel Custom Commands and Tazel Options from the legacy Tazel</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Bring Tazel Custom Commands and Tazel Options from the legacy Tazel</pre>
</div>
</content>
</entry>
<entry>
<title>Bring the plugin API and the Gradle plugin from the legacy Tazel</title>
<updated>2026-11-12T15:52:50+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-12T15:52:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/tazel/commit/?id=6c7e9ad4e59c46da58a121d70caa17c01006273b'/>
<id>6c7e9ad4e59c46da58a121d70caa17c01006273b</id>
<content type='text'>
Tazel Plugins stay, built with Gradle and published to Tazel Portal.
The api/ (com.progmasoft.tazel:tazel-api) and gradle-plugin/
(com.progmasoft.tazel.plugin) projects come from Progmasoft/tazel-legacy
with their tests, with these changes:

- tazelPlugin { } holds group, name and version. The descriptor
  META-INF/tazel-plugin.properties records them first, so the JAR says
  who the plugin is; before, ViGet recorded the publisher, name and
  version at push time. The group must be a reversed domain of at least
  two parts (Tazel Portal checks the namespace by the Sonatype rules),
  the name letters, digits and _ . -, and the version a Semantic
  Version. The version of the Gradle project is not the plugin's.
- The API version starts again at 1, so plugins built for the legacy
  Tazel (API 3) are not loaded.
- Documentation no longer speaks of ViGet, Tala targets or
  tazel.tala.run; the site is tazel.net.
- Dependency locking of the legacy build is not carried over, like in
  the rest of this build.

The root build includes both projects, so ./gradlew check runs the
Gradle TestKit tests of the plugin as well.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Tazel Plugins stay, built with Gradle and published to Tazel Portal.
The api/ (com.progmasoft.tazel:tazel-api) and gradle-plugin/
(com.progmasoft.tazel.plugin) projects come from Progmasoft/tazel-legacy
with their tests, with these changes:

- tazelPlugin { } holds group, name and version. The descriptor
  META-INF/tazel-plugin.properties records them first, so the JAR says
  who the plugin is; before, ViGet recorded the publisher, name and
  version at push time. The group must be a reversed domain of at least
  two parts (Tazel Portal checks the namespace by the Sonatype rules),
  the name letters, digits and _ . -, and the version a Semantic
  Version. The version of the Gradle project is not the plugin's.
- The API version starts again at 1, so plugins built for the legacy
  Tazel (API 3) are not loaded.
- Documentation no longer speaks of ViGet, Tala targets or
  tazel.tala.run; the site is tazel.net.
- Dependency locking of the legacy build is not carried over, like in
  the rest of this build.

The root build includes both projects, so ./gradlew check runs the
Gradle TestKit tests of the plugin as well.
</pre>
</div>
</content>
</entry>
</feed>
