Skip to content

tiawl/shaderc.zig

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

shaderc.zig

This is a fork of google/shaderc packaged for Zig

Why this fork ?

The intention under this fork is to package google/shaderc for Zig. So:

  • Unnecessary files have been deleted,
  • The build system has been replaced with build.zig,
  • A cron runs every day to check google/shaderc. Then it updates this repository if a new release is available.

How to use it

The goal of this repository is not to provide a Zig binding for google/shaderc. 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 google/shaderc 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 shaderc.zig:

  • as raw (no available example, open an issue if you are interested in, we will be happy to help you),
  • as a daily updated interface for your Zig binding of google/shaderc (see here for a private usage).

Dependencies

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:

CICD reminder

These repositories are automatically updated when a new release is available:

This repository is automatically updated when a new release is available from these repositories:

zig build options

These additional options have been implemented for maintainability tasks:

  -Dfetch   Update .references folder and build.zig.zon then stop execution
  -Dupdate  Update binding

License

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.