Include ini.h in build.zig.zon - #20
Open
thearchivalone wants to merge 2 commits into
Open
Conversation
This small change allows pulling in the c api header when using zig's build system as the main build system when building mixed language code. As it currently stands, to use the c api in that instance, you can use zig fetch to pull in the library but still need to have the header available, making changes upstream a possible breaking point if the api changes and the header is no longer up to date
Even though adding the ini was fine, not including all of the new files have lead to build failure when including in other projects
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This small change allows pulling in the c api header when using zig's build system for mixed language code. As it currently stands, to use the api in that instance, you can use zig fetch to pull in the library but still need to have the header available leading to the possibility of breakage if the developer has to manually update the header locally