3
21
Fork
You've already forked zigbrains
2

Broken with Zig 0.17.0 master branch #11

Open
opened 2026年05月26日 11:00:17 +02:00 by FalsePattern · 2 comments

ZigBrains is currently not compatible with the latest Zig 0.17.0 master branch releases due to the build system rewrite.
We can only make it compatible once all the TODOs inside the print() function in this struct are resolved: https://codeberg.org/ziglang/zig/src/branch/master/lib/compiler/Maker/ScannedConfig.zig
Once that's done, we can update the project scan logic to work via the info returned from zig build --print-configuration, but currently it still lacks critical info about stuff like dependency source paths.

The latest compatible zig version is 0.17.0-dev.387+31f157d80

See:
ziglang/zig#35428
https://ziggit.dev/t/devlog-build-system-reworked/15742/5
https://github.com/zigtools/zls/issues/3208

ZigBrains is currently not compatible with the latest Zig 0.17.0 master branch releases due to the build system rewrite. We can only make it compatible once all the TODOs inside the print() function in this struct are resolved: https://codeberg.org/ziglang/zig/src/branch/master/lib/compiler/Maker/ScannedConfig.zig Once that's done, we can update the project scan logic to work via the info returned from `zig build --print-configuration`, but currently it still lacks critical info about stuff like dependency source paths. The latest compatible zig version is `0.17.0-dev.387+31f157d80` See: https://codeberg.org/ziglang/zig/pulls/35428 https://ziggit.dev/t/devlog-build-system-reworked/15742/5 https://github.com/zigtools/zls/issues/3208
FalsePattern changed title from (削除) Zig 0.17.0 build system rewrite compatibility (削除ここまで) to Broken with Zig 0.17.0 master branch 2026年05月27日 12:17:27 +02:00
Author
Owner
Copy link

update:
The intended way to read the configuration is by processing the binary format via std.Build.Configuration.
Blocker: ziglang/zig#35498
See: https://ziggit.dev/t/devlog-build-system-reworked/15742/9

We'll need to bundle a helper zig script we compile to an exe and run to get json output on its stdout piped back into java like what we're doing with the build runner right now

(削除) As a temporary solution until 35498 is resolved, we can do the workaround i mentioned in https://ziggit.dev/t/devlog-build-system-reworked/15742/3: "clearing the .zig-cache/c/ directory, running zig build --help, and then parsing the file that appears in there." and then stop doing it when zig build gets the command line flag (削除ここまで) ziglang/zig#35511

cc @ENDERZOMBI102

update: The intended way to read the configuration is by processing the binary format via `std.Build.Configuration`. Blocker: https://codeberg.org/ziglang/zig/issues/35498 See: https://ziggit.dev/t/devlog-build-system-reworked/15742/9 We'll need to bundle a helper zig script we compile to an exe and run to get json output on its stdout piped back into java like what we're doing with the build runner right now ~~As a temporary solution until 35498 is resolved, we can do the workaround i mentioned in https://ziggit.dev/t/devlog-build-system-reworked/15742/3: "clearing the `.zig-cache/c/` directory, running `zig build --help`, and then parsing the file that appears in there." and then stop doing it when zig build gets the command line flag~~ https://codeberg.org/ziglang/zig/pulls/35511 cc @ENDERZOMBI102
Author
Owner
Copy link

Working branch: https://codeberg.org/FalsePattern/zigbrains/src/branch/0.17-compat

Working branch: https://codeberg.org/FalsePattern/zigbrains/src/branch/0.17-compat
Sign in to join this conversation.
No Branch/Tag specified
master
rewrite-3
0.17-compat
251
252
253
dev
241
242
243
feat/use-var-intent
feat/parser-reimpl
experimental
30.0.1
30.0.0
29.1.0
29.0.1
29.0.0
28.3.0
28.2.2
28.2.1
28.2.0
28.1.0
28.0.0
27.3.1
27.3.0
27.2.1
27.2.0
27.1.1
27.1.0
27.0.0
26.3.2
26.3.1
26.3.0
26.2.1
26.2.0
26.1.0
26.0.2
26.0.1
26.0.0
25.5.1
25.5.0
25.4.2
25.4.1
25.4.0
25.3.0
25.2.0
25.1.0
25.0.2
25.0.1
24.0.1
24.0.0
23.1.2
23.1.1
23.1.0
23.0.2
23.0.1
23.0.0
22.0.1
22.0.0
21.1.0
21.0.0
20.3.0
20.2.2
20.2.1
20.2.0
20.1.3
20.1.2
20.1.1
20.1.0
20.0.4
20.0.3
20.0.2
20.0.1
20.0.0
19.3.0-232
19.3.0-233
19.3.0-241
19.3.0-242
19.3.0
19.2.0
19.1.0
19.0.0
18.1.0
18.0.0
17.3.1-dev001
17.3.0
17.2.0
17.1.0
17.0.0
16.1.3
16.1.2
16.1.1
16.1.0
16.0.0
16.0.0-pre2
16.0.0-pre1
15.2.0-241
15.2.0-233
15.2.0-232
15.2.0
15.1.1-241
15.1.1-233
15.1.1-232
15.1.1
15.1.0-241
15.1.0-233
15.1.0-232
15.1.0
15.0.3-241
15.0.3-233
15.0.3-232
15.0.3
15.0.2-241
15.0.2-233
15.0.2-232
15.0.2
15.0.1-241
15.0.1-233
15.0.1-232
15.0.1
15.0.0-241
15.0.0-233
15.0.0-232
15.0.0
14.5.0-241
14.5.0-233
14.5.0-232
14.5.0-231
14.5.0
14.4.0-241
14.4.0-233
14.4.0-232
14.4.0-231
14.4.0
14.3.0-233
14.3.0-232
14.3.0-231
14.3.0
14.2.0-233
14.2.0-232
14.2.0-231
14.2.0
14.1.0-233
14.1.0-232
14.1.0-231
14.1.0
14.0.1-233
14.0.1-232
14.0.1-231
14.0.1
14.0.0-233
14.0.0-232
14.0.0-231
14.0.0
13.2.0-233
13.2.0-232
13.2.0-231
13.2.0
13.1.1-233
13.1.1-232
13.1.1-231
13.1.1
13.1.0-233
13.1.0-232
13.1.0-231
13.1.0
13.0.1-233
13.0.1-232
13.0.1-231
13.0.1
13.0.0-233
13.0.0-232
13.0.0-231
13.0.0
12.1.0-pre01
12.0.0
11.1.0
11.0.0
0.9.0
0.8.1
0.8.0
0.7.0
0.6.0
0.5.2
0.5.1
0.5.0
0.4.0
0.3.1
0.3.0
0.2.0
0.10.0
0.1.0
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
 The priority is critical
Priority
High
 The priority is high
Priority
Low
 The priority is low
Priority
Medium
 The priority is medium
Reviewed
Confirmed
 Issue has been confirmed
Reviewed
Duplicate
 This issue or pull request already exists
Reviewed
Fixed
 The bug has been fixed.
Reviewed
Invalid
 Invalid issue
Reviewed
Won't Fix
 This issue won't be fixed
Status
Abandoned
 Somebody has started to work on this but abandoned work
Status
Blocked
 Something is blocking this issue or pull request
Status
Need More Info
 Feedback is required to reproduce issue or to continue work
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
FalsePattern/zigbrains#11
Reference in a new issue
FalsePattern/zigbrains
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?