-
Notifications
You must be signed in to change notification settings - Fork 9
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
Project status? #3
Comments
Hi! Thanks for your interest. I believe the "27 days ago" refers to the currently opened pull request. That being said, I'd still think this is an interesting endeavor, that I hope I'll be able to pick up again at some point. There are several interesting problems to be solved here: for instance, it is not obvious at all what a nice and safe high-level API for wlroots should be (the current repo contains an attempt, but I think it needs to be reworked). See also for instance the difficulties that other people had when writing rust wrappers (http://way-cooler.org/blog/2019/04/29/rewriting-way-cooler-in-c.html). And all of this only makes sense to in the end use the bindings to write a compositor (even a minimal one to start with), and coming up with something interesting is a project on its own. So yeah, I guess the status is "experimental" and "hibernating" :-). |
The reason I'm asking is because I'm interested in writing a compositor, but I can't promise I can deliver a good one because that would stress me out, and I also have to worry about work for now. Would it be possible to generate part of the bindings and write a nice ocaml'y interface on top of that? Edit: You could try outsourcing some of this to a capable student via GSoC, perhaps. |
I've seen some recent activity and became curious.
Any ideas? |
Yeah, you should pin my (at the moment unreleased) xkbcommon bindings:
But yeah, I've been doing some cleanup. Now everything should compile, and the API now corresponds to "thin bindings": it sticks to the wlroots API as much as possible while being type safe. Still, there is a lot of mechanical work to be done to be able to implement nontrivial examples on top of the bindings. In particular, I started porting |
Hmmm... that doesn't work
Thin bindings sound good. Building more ocaml-y bindings on top of that can always be done later. I'll take a more in-depth look and I'm aware that there's always mechanical work to be done for bindings. Thanks for your effort :) |
Ah, try:
|
Thanks, that did the trick |
Got a build failure now:
|
Do you have the latest version of wlroots (from their git)? |
Nope, but I didn't know you're targeting their git master instead of release. I have 0.10.1. I can check with master later. (Maybe all this should go into README.md?) |
Yeah, all of this should definitely go in the readme. I think at targeted the release branch at some point, and ended up installing the git version for other purposes, and didn't checked whether it broke. For now let's just say I target the git master yeah :/. |
No worries, it's not like I'm expecting a finished product ;) |
I'm messing around with it a little bit (I've never really used OCaml, only SML) and I'm stuck at writing a .merlin file for the tinywl subdir. Sorry to bum so much support off you, but I looked at the other .merlin files and there's numbers and underscores that I don't understand. Do you generate them somehow? |
Yeah you shouldn't have to write .merlin files by hand, dune generates them automatically. So if you build tinywl ( |
Ah, I see. I assume it isn't being built because of the build failure with |
Hi, not an actual issue but I have no idea where else to ask questions about this project.
Just wondering, is this still alive? The organization overview says it was modified 27 days ago but I didn't see any recent commits...
The text was updated successfully, but these errors were encountered: