Ecosystems like JavaScript or Python use one of multiple different kinds of manifests to specify dependencies — package.json, deno.json, requirements.txt, pyproject.toml.
But some ecosystems don't use manifests, like C and C++. And even when there are quasi-manifests, like CMakeLists.txt, these are very difficult to parse.
How can we create tools to identify dependency graphs for manifest-less ecosystems?
Ecosystems like JavaScript or Python use one of multiple different kinds of manifests to specify dependencies —
package.json,deno.json,requirements.txt,pyproject.toml.But some ecosystems don't use manifests, like C and C++. And even when there are quasi-manifests, like
CMakeLists.txt, these are very difficult to parse.How can we create tools to identify dependency graphs for manifest-less ecosystems?