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

Framebuffer and static support? #383

Open
piranna opened this issue May 17, 2017 · 3 comments
Open

Framebuffer and static support? #383

piranna opened this issue May 17, 2017 · 3 comments

Comments

@piranna
Copy link

piranna commented May 17, 2017

Is it possible to use uzbl-core with a framebuffer graphic device? And is it possible to compile it in a single statically linked binary? I think its minimalist design is perfect to use it as local graphic environment for NodeOS... :-)

@mathstuf
Copy link
Member

I don't think webkit itself supports being build statically. If you can get it to be static, I see no reason Uzbl itself couldn't. As for a framebuffer, Uzbl currently does some raw X calls, but if that could be predicated on the backend GTK is actually using, I don't see why it wouldn't work either (@keis is running on Wayland IIRC).

@piranna
Copy link
Author

piranna commented May 17, 2017

I was able to compile it statically for framebuffer using Qt on noGUI, don't know if it would be possible to do it with GTK...

@mathstuf
Copy link
Member

Just an FYI, but Qt uses an old version of WebKit. WebKit2 is the Future™ and uses separate binaries for network and rendering logic, so you'll basically have at least 3 copies of WebKitGTK laying around…

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

No branches or pull requests

2 participants