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

Fixed broken build.zig files. #3045

Merged
merged 1 commit into from
May 6, 2023
Merged

Fixed broken build.zig files. #3045

merged 1 commit into from
May 6, 2023

Conversation

Gamer-Kold
Copy link
Contributor

I noticed the build.zig file wasn't working with the latest zig compiler. So I went ahead and fixed it. It went ahead and built fine on my linux machine, and I used the resulting library to compile the basic example, so I don't think there were any hidden errors.

(Small side note, is the zig build script community maintained? I'd want to add a notice to the build file itself if that was the case.)

@raysan5 raysan5 merged commit de748df into raysan5:master May 6, 2023
@raysan5
Copy link
Owner

raysan5 commented May 6, 2023

@Gamer-Kold Thanks for the review, actually it was reviewed last week I think...

Yes, the zig build script is community maintained, feel free to add a note if you think it will be helpful for other users.

@star-tek-mb
Copy link
Contributor

star-tek-mb commented May 12, 2023

latest raylib should be built with latest zig master branch. if you are using zig 0.10.0 use older raylib tagged version please.

@raysan5 can we revert this please? examples build.zig wasn't touched (it's still master). and overall zig is moving forward to package manager, i'm using raylib in my project as is with zig package manager.

@Gamer-Kold look at previous zig related PRs. zig 0.10.0 does have some bugs with C ABI, this was the cause i've updated raylib to zig latest master (0.11.0-dev).

@Gamer-Kold
Copy link
Contributor Author

Makes sense. It didn't work on my machine with master; but if it's working on most other people's machines then I have no reason to hold back the revert. Not when I can keep a custom build file anyway.

As an aside, I thought it was using a deprecated version of the system; a note in the build script stating which version it has been tested with (as said previously) would really be nice.

@star-tek-mb
Copy link
Contributor

@Gamer-Kold yeah. i think we should leave a note with specific zig version build.zig file was tested with. can you do that? i would appreciate your work.

@Gamer-Kold
Copy link
Contributor Author

I'll try, I'll also revert the pull request since it seems thay hasn't happened yet.

Gamer-Kold added a commit to Gamer-Kold/raylib that referenced this pull request May 14, 2023
…mpiler (as of commit, latest is 0.10.1) (raysan5#3045)"

This reverts commit de748df so that zig
build script works with master branch of zig.
raysan5 pushed a commit that referenced this pull request May 15, 2023
…e to all of them stating version of zig they were using (#3060)

* Revert "Fixed broken build.zig files. Now works with latest stable compiler (as of commit, latest is 0.10.1) (#3045)"

This reverts commit de748df so that zig
build script works with master branch of zig.

* Added a note to build.zig files that denotes what version of zig they have been tested with.

* Standardised the note in the build.zig files
futureapricot pushed a commit to futureapricot/raylib that referenced this pull request Oct 4, 2023
…as of commit, latest is 0.10.1) (raysan5#3045)

Co-authored-by: Talha Qamar <qamartalha@proton.me>
futureapricot pushed a commit to futureapricot/raylib that referenced this pull request Oct 4, 2023
…e to all of them stating version of zig they were using (raysan5#3060)

* Revert "Fixed broken build.zig files. Now works with latest stable compiler (as of commit, latest is 0.10.1) (raysan5#3045)"

This reverts commit de748df so that zig
build script works with master branch of zig.

* Added a note to build.zig files that denotes what version of zig they have been tested with.

* Standardised the note in the build.zig files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants