chore: consume the bindings toolbox and declare the upstream manifest

.github/workflows/CD.yml

@@ -17,7 +17,7 @@ on:
 jobs:
   cd:
     if: github.event_name != 'schedule' || github.ref == 'refs/heads/main'
-    uses: EvergineTeam/evergine-standards/.github/workflows/binding-simple-cd.yml@v2
+    uses: EvergineTeam/Evergine.Bindings/.github/workflows/binding-simple-cd.yml@v1
     with:
       generator-project: "MeshOptimizerGen/MeshOptimizerGen/MeshOptimizerGen.csproj"  # Path to your generator .csproj
       generator-name: "MeshOptimizer"                # Name of your generator executable

.github/workflows/CI.yml

@@ -20,7 +20,7 @@ on:
 
 jobs:
   ci:
-    uses: EvergineTeam/evergine-standards/.github/workflows/binding-common-ci.yml@v2
+    uses: EvergineTeam/Evergine.Bindings/.github/workflows/binding-common-ci.yml@v1
     with:
       generator-project: "MeshOptimizerGen/MeshOptimizerGen/MeshOptimizerGen.csproj"  # Path to your generator .csproj
       generator-name: "MeshOptimizer"                # Name of your generator executable

binding.yml

@@ -0,0 +1,33 @@
+# Binding manifest — see https://github.com/EvergineTeam/Evergine.Bindings
+# Schema: https://github.com/EvergineTeam/Evergine.Bindings/blob/main/binding.schema.json
+toolbox: 1.0.0
+
+package:
+  id: Evergine.Bindings.MeshOptimizer
+  project: MeshOptimizerGen/Evergine.Bindings.MeshOptimizer/Evergine.Bindings.MeshOptimizer.csproj
+  target-framework: net10.0
+  runtime-identifier: linux-x64
+
+upstream:
+  kind: git-tree
+  language: cpp
+  project: https://github.com/zeux/meshoptimizer
+  version-from: git-release
+  sources:
+    - repo: zeux/meshoptimizer
+      ref: master
+      remote-path: src/meshoptimizer.h
+      path: MeshOptimizerGen/MeshOptimizerGen/Headers/meshoptimizer.h
+      format: c-header
+
+generator:
+  project: MeshOptimizerGen/MeshOptimizerGen/MeshOptimizerGen.csproj
+  name: MeshOptimizer
+  output:
+    - MeshOptimizerGen/Evergine.Bindings.MeshOptimizer/Generated
+
+# NOTE — this package ships native binaries under Evergine.Bindings.MeshOptimizer/runtimes.
+# The header and those binaries must come from the same upstream revision. `ref: master`
+# is a moving target, so a header bump is only valid together with a native rebuild;
+# binding-updater must label any such pull request `needs-human-review`. Pinning `ref`
+# to a release tag would remove this hazard and is worth considering.