tinygltf | Header only C++11 tiny glTF 2.0 library

This is currently not supported, as you could see from the table of core options, only 3 options are settable per subproject as of now: werror and default_library (since 0.54.0) and warning_level (since 0.56.0). And below in Specifying options per subproject you can find more details e.g. about order of applying.

Also I found from discussion in issue Subproject default_options are ignored one of the main contributor says:

Right now only a couple of options are allowed on a per-project basis: default_library, werror (and one more I can't remember off the top of my head). We keep adding more over time, but other ones are ignored, yes.

Removing all meson files through rm -rf meson* inside the build directory and recompiling seems to have fixed the problem.

From the glTF specification, skin.skeleton is "the closest common root of the joints hierarchy or a direct or indirect parent node of the closest common root."

Not all engines or authoring tools have a concept of a "root" in the joint hierarchy, so it isn't required, but if your loader needs one you can simply choose any node that is a common ancestor of the other joints, use the scene root itself, or insert a new root at loading time.

Since you're linking SFML statically, you're integrating all the symbols of SFML in your application including the STB symbols.

I see two different solutions here, maybe there are more:

• Update the STB header in the SFML extlibs/ directory and rebuild SFML
• Link SFML dynamically, so your application doesn't see the SFML STB symbols

It's possible the two cubes share the same mesh. In the screenshot below, there are two Blender "objects", Left-Cube and Right-Cube. Both objects use the same Blender mesh, called Shared-Cube-Mesh.

The glTF exporter recognizes this pattern and mirrors it in the glTF file. There will be two glTF nodes, corresponding to the two Blender objects that use the mesh. But there will only be a single glTF mesh, with a single cube.

You can click the "number of users" button, shown below with a white arrow pointing to it, to make the second object use its own unique mesh. But be warned, this doubles the amount of mesh data being exported to glTF in this simple example. A complete copy of the mesh would be made in both Blender and the glTF binary payload.