Upgrade Mesa, how feasible?

Development
43

Have you got past the splash screen?

44

ā€¦would be great news if you could confirm Godot 3.1-alpha5 is working!

45

Yes. Although, I havenā€™t run your mentioned test demo or the demos on the Godot website under Haiku (see: https://youtu.be/R6HD1L4dqMg).

Does any of those demos work for you at all?

46

Iā€™ve only tested the one I wrote by calling it through Godot from the command line. I didnā€™t get any graphics output in the window. I only saw the results of button presses as indicated by print statements that display in the terminal. As such, I can see it possible to write an old school text adventure in Godot. Thatā€™s as far as Iā€™ve got. What overrides are you using? I assume Haiku x86_64?

47

Looks like GLES 2 support has returned for Godot 3.1. this sounds like a good thing for near term usability in Haiku.

49

Any recipe for 18.1? This seems to be a breaking point for Godot.

50

Yes. I currently maintain a Haikuports recipe for Mesa 18.3.1 (current). Builds on Haiku R1B1 x86 and x86_64. Mesa library seems fine. Some reworking on the mesa_swpipe driver patching still needed.

3 Likes
51

I must have missed it.

52

@cocobean

I looked at the ports tree again and couldnā€™t find it. I found the 17.1.10 and 7.9.2 recipes.

53

For referencing:

Haikuports - Legacy Mesa 18.x work:

NOTE: Mesa 18.x needs further patch work for full mesa_swpipe driver functionality. Mesa 18.3.1 was the last stable release I tested to compile on Haiku.

Godot:

54

I can see the conversation. I see file names with paths in the conversation hinting that 18.x recipes are in the tree. But I still donā€™t see any 18.x files in the tree when looking at a freshly pulled repo, or directly querying through GitHub.

55

The recipes and patchsets are within those conversation links. You can view and copy/download from there to update Mesa from the tree.

Wait till the core developers have time to fix a few things. They are already aware of the issues (as mentioned in those links). :grin:

56

So until there is some form of official release, anyone wanting to try the code and work with it has to manually copy and paste code and apply diffs by hand? That kinda defeats the purpose of git, at least in my view.

57

Disclaimer: Use only what is submitted in the Haikuports tree initially.

If you are working on bumping Mesa and using git, follow the first conversation link to kallisti5ā€™s Mesa git work and pull from there. His main instructions for testing his Mesa work are there (unless they changed). You can fork from there at your leisure. That is the official core dev Mesa work to follow (unless said otherwise).

.

1 Like
58

Applause to Dragon, Bullfrog, and Cocobean for taking the initiative on Mesa and related 3D updates. Having some updates on the 3D infrastructure is a nice step forward.

1 Like
59

Thanks. I have been using the main install of 17.1.10. Sorry I missed the link to kallistis git in the tl;dr. Iā€™m just wanting to test Godot against what we have to see whatā€™s working. I realize known issues are being worked on. 17.1.10 isnā€™t working for this. Iā€™m just trying not to duplicate work by piecing it together from scratch. Nor am I trying to say work faster. I appreciate everyoneā€™s efforts and how well everything is working so far. I have over a dozen installs of Haiku on various machines. Breaking things and data loss donā€™t scare me. I have my important stuff isolated from development/testing platforms.

60

Godot 3.1 Beta released!

2 Likes
61

Yes, because cocbean submitted the pull requests, but then deleted the branch he submitted it from. So now there isnā€™t an easy way to checkout the code using git, and his work will probably be lost because itā€™s too annoying to recover. We told him it is annoying to do that, butā€¦

1 Like
62

This why I backup the changes I make by making copies of the files I change. This makes it a simple matter of copying the files back in place and doing a commit/rebase to restore my changes back to a local branch in case I lose it for one reason or another. My progress with the terminal argv Iā€™ve been working on has been in limbo due to volatility in my working setup. Iā€™ve been doing a lot of hardware changes that have disrupted my work flows.

63

This topic is now a few month old. I think itā€™s okay to throw into the room the shy question if something happened in the mean time? The last I know is that somebody experimented with a 18.x receipt but Iā€™m right now not sure in what stage this came to a rest. Iā€™d love to do a proper cross-compile of my projects in the future.