Wayland McWayface tutorial project done, feedback on jextract

[Mark Hammons]

On 04/03/2019 11:14, Maurizio Cimadamore wrote:
> One question, I've seen in your great github landing page that you had 
> issues with gnome terminal - is that a Panama issue, or something else? 

I'm fairly certain it's an issue with wayland and wlroots. The tutorial 
I was basing this project off of was using wlroots version 0.2, while 
I'm using wlroots v0.3 (or maybe even 0.4.1, opensuse has them both 
installed and I'm not sure which jextract is linking against). The 
version difference comes with api incompatibilities. Some of the calls 
the tutorial told me I could use just don't exist anymore, or have been 
changed to use different arguments. I'm fairly certain the 
gnome-terminal issue is related to a newer version of a protocol being 
used (since the protocol used is literally labeled unstable) and that's 
why weston and its tools can connect while gnome-terminal doesn't.

Either that or I messed up somewhere. In any case, I'm fairly sure it's 
not a panama issue.

As for generating .deb files and stuff, I'd think that'd be a job for 
jpackager. Maybe jextract could leverage that if it needs to generate 
.exe/.rpm/.dmg/.deb files?

Also, I'm glad to hear you've already got plans to make dependent panama 
jars.

One last question. As I mention in my readme, I've written a binding for 
stdlib's setenv function in scala as opposed to getting jextract to 
generate it for me (because of the concerns I voiced before). It's in 
the package usr.include in the scala source code. Is it necessary that I 
define the header file at all in these bindings? I'd imagine I'd 
normally have to include the library to link against (but it's not 
necessary since it's part of libc), but if I can leave out the header 
annotation it's easier to make semi-platform independent bindings like 
what I could do with jnr.

Thanks,

Mark