This is a fork of jqlang/jq to package the libjq C API for Zig
The intention under this fork is to package jqlang/jq for Zig. So:
- Unnecessary files have been deleted,
- The build system has been replaced with
build.zig, - A cron runs every day to check jqlang/jq. Then it updates this repository if a new release is available.
The goal of this repository is not to provide a Zig binding for jqlang/jq. There are at least as many legit ways as possible to make a binding as there are active accounts on Github. So you are not going to find an answer for this question here. The point of this repository is to abstract the jqlang/jq compilation process with Zig (which is not new comers friendly and not easy to maintain) to let you focus on your application. So you can use libjq.zig:
- as raw (see the examples directory),
- as a daily updated interface for your Zig binding of jqlang/jq (an available exemple is coming soon).
The Zig part of this package is relying on the latest Zig release (0.13.0) and will only be updated for the next one (so for the 0.14.0).
Here the repositories' version used by this fork:
These repositories are automatically updated when a new release is available:
- (coming soon)
This repository is automatically updated when a new release is available from these repositories:
- jqlang/jq
- tiawl/toolbox
- tiawl/oniguruma.zig
- tiawl/spaceporn-action-env
- tiawl/spaceporn-action-bot
- tiawl/spaceporn-action-ci (TODO)
- tiawl/spaceporn-action-cd-ping (TODO)
- tiawl/spaceporn-action-cd-pong
These additional options have been implemented for maintainability tasks:
-Dfetch Update .references folder and build.zig.zon then stop execution
-Dupdate Update binding
This repository is not subject to a unique License:
The parts of this repository originated from this repository are dedicated to the public domain. See the LICENSE file for more details.
For other parts, it is subject to the License restrictions their respective owners choosed. By design, the public domain code is incompatible with the License notion. In this case, the License prevails. So if you have any doubt about a file property, open an issue.