Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow modules to have private and public include directories #18439

Open
Tracked by #8
ikskuh opened this issue Jan 3, 2024 · 0 comments
Open
Tracked by #8

Allow modules to have private and public include directories #18439

ikskuh opened this issue Jan 3, 2024 · 0 comments
Labels
proposal This issue suggests modifications. If it also has the "accepted" label then it is planned. zig build system std.Build, the build runner, `zig build` subcommand, package management
Milestone

Comments

@ikskuh
Copy link
Contributor

ikskuh commented Jan 3, 2024

Follow-up from #18160:

After reading the source i've seen that modules now have a include_dirs property which is neat. But what i've figured is that some modules will require private and public include directories.

The private ones are required to build the C source code of the modules, but the public ones are required for using the module, so it would be useful to be able to either make them available to all other modules, or just to the ones depending on it

@Vexu Vexu added proposal This issue suggests modifications. If it also has the "accepted" label then it is planned. zig build system std.Build, the build runner, `zig build` subcommand, package management labels Jan 3, 2024
@Vexu Vexu added this to the 0.13.0 milestone Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal This issue suggests modifications. If it also has the "accepted" label then it is planned. zig build system std.Build, the build runner, `zig build` subcommand, package management
Projects
None yet
Development

No branches or pull requests

2 participants