Why do this?
We should enable consumers of this SDK to get those paths themselves if they need them.
What to add
Not sure if there is a more conventional Zig name for the following functions but I imagine it returning []LazyPath for each. Would likely need the compile target passed in as a bare minimum.
- Add getLibraryPaths()
- Add getIncludePaths()
- Add getSystemIncludePaths()
What prompted this?
Translate-C as an external dependency didn't work until I added it recently in this PR: #92, We should enable consumers of this SDK to get those paths themselves if they need them.
it might be preferable to add a public API to get the include paths for a given target.
From: #91
Why do this?
We should enable consumers of this SDK to get those paths themselves if they need them.
What to add
Not sure if there is a more conventional Zig name for the following functions but I imagine it returning
[]LazyPathfor each. Would likely need the compile target passed in as a bare minimum.What prompted this?
Translate-C as an external dependency didn't work until I added it recently in this PR: #92, We should enable consumers of this SDK to get those paths themselves if they need them.