Open andy5995 opened 2 days ago
Looking briefly at the tree-sitter wrap, the problem may be with using the subproject dir as the patch directory. Paradox?
My understanding is that writing patch_directory = tree-sitter
uses ./subprojects/packagefiles/tree-sitter
as folder from which meson.build
is copied. That is what I understood by reading the docs at least. Is that wrong?
For ref: https://mesonbuild.com/External-Project-module.html#using-wrap-file
I would have assumed meson patches file back after updating its git deps. If not, I think it is an upstream issue.
I believe you are correct. I just looked through the structure of the wrapdb project and it matches what you state.
I opened an issue upstream
See https://github.com/mesonbuild/meson/issues/13970#issuecomment-2507492812 for the fix.
I'll re-title this issue to suggest documenting it here.
Note I didn't read through the meson docs or the dupe issue to see if there are cases when the reset arg should not be appended.
tree-sitter wasn't shown in the output but is on L79 of meson.build.
Removing subprojects/tree-sitter and re-running
bun run meson-setup.clang-release
fixed the issue.Looking briefly at the tree-sitter wrap, the problem may be with using the subproject dir as the patch directory. Paradox?