zig/mach
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
mach/libs/model3d
History
Stephen Gutekanst 29964c99bb update to latest Zig (zig fmt) 
Signed-off-by: Stephen Gutekanst <stephen@hexops.com>
2023-06-25 00:01:55 -07:00
..
.github {dev,model3d}: ensure model3d has standard project files 2022-10-22 07:45:50 -07:00
assets model3d: add m3d implementation / bindings (#589) 2022-10-21 07:42:01 -07:00
src update to latest Zig (zig fmt) 2023-06-25 00:01:55 -07:00
.gitattributes {dev,model3d}: ensure model3d has standard project files 2022-10-22 07:45:50 -07:00
.gitignore {dev,model3d}: ensure model3d has standard project files 2022-10-22 07:45:50 -07:00
build.zig all: use std.Build.installArtifact 2023-04-25 15:06:11 -07:00
LICENSE {dev,model3d}: ensure model3d has standard project files 2022-10-22 07:45:50 -07:00
LICENSE-APACHE {dev,model3d}: ensure model3d has standard project files 2022-10-22 07:45:50 -07:00
LICENSE-MIT {dev,model3d}: ensure model3d has standard project files 2022-10-22 07:45:50 -07:00
README.md model3d: README title change 2023-04-05 03:26:52 -07:00

README.md

mach/model3d - compact, featureful model format & alternative to glTF

Model3D is an up-and-coming compact, featureful, universal model format that tries to address the shortcomings of existing formats (yes, including glTF - see their rationale.)

This repository provides Zig bindings, with the aim of a pure-Zig implementation eventually.

This repository is a separate copy of the same library in the main Mach repository, and is automatically kept in sync, so that anyone can use this library in their own project if they like!

Experimental

This is an experimental Mach library, according to our stability guarantees:

Experimental libraries may have their APIs change without much notice, and you may have to look at recent changes in order to update your code.

Why this library is not declared stable yet

Join the community

Join the Mach community on Discord to discuss this project, ask questions, get help, etc.

Issues

Issues are tracked in the main Mach repository.

Contributing

Contributions are very welcome. Pull requests must be sent to the main repository to avoid some complex merge conflicts we'd get by accepting contributions in both repositories. Once the changes are merged there, they'll get sync'd to this repository automatically.