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

Remove HW_buffer_counter after irrlichmt fix to remove HWBufferMap #12232

Merged
merged 2 commits into from Apr 28, 2022

Conversation

paradust7
Copy link
Contributor

Fixes issue #12231, in conjunction with minetest/irrlicht#99 (comment)

@sfan5 sfan5 added the Bugfix 🐛 PRs that fix a bug label Apr 26, 2022
@sfan5
Copy link
Member

sfan5 commented Apr 26, 2022

This is exactly the kind of fix I had in mind, thanks for looking at this.

For now the old code should not be removed but put inside #if IRRLICHT_VERSION_MT_REVISION < 5 so people can still build with older IrrlichtMt temporarily.

@lhofhansl
Copy link
Contributor

Cool... Happy to see my old hack removed!

@lhofhansl
Copy link
Contributor

Wait. We merged this before the Irrlicht change. Let's either revert this or merge the Irrlicht change quickly.
(I didn't have a chance to test it, yet).

@lhofhansl
Copy link
Contributor

@SmallJoker @sfan5

@sfan5
Copy link
Member

sfan5 commented Apr 29, 2022

I assume that was an oversight, I'll merge the Irrlicht PR since it's fine anyway.
Though I wonder whether most people remember to pull irrlichtmt updates too or whether they'll accidentally end up running a Minetest with this change and Irrlicht without the other one.

@SmallJoker
Copy link
Member

I do not update IrrlichtMt often so that recent Minetest builds continue to work (and do not need LD_PRELOAD with an old IrrlichtMt build). That makes bisecting and compatibility testing much easier. So yes indeed, people might indeed not update IrrlichtMt in sync with Minetest.

@sfan5
Copy link
Member

sfan5 commented Apr 29, 2022

It's okay if people use irrlichtmt tagged at a revision, the compatibility #if's can deal with this. What might cause problems is random git commits.

sfan5 pushed a commit that referenced this pull request Apr 30, 2022
…12232)

 Keep code and use version check instead, for backwards compatibility
sfan5 pushed a commit that referenced this pull request Apr 30, 2022
…12232)

 Keep code and use version check instead, for backwards compatibility
@paradust7 paradust7 deleted the issue_12231 branch May 6, 2022 20:27
sfan5 pushed a commit that referenced this pull request May 12, 2022
…12232)

 Keep code and use version check instead, for backwards compatibility
sfan5 pushed a commit that referenced this pull request May 12, 2022
…12232)

 Keep code and use version check instead, for backwards compatibility
sfan5 pushed a commit that referenced this pull request May 14, 2022
…12232)

 Keep code and use version check instead, for backwards compatibility
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants