From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] vte: new package
Date: Wed, 17 Jan 2018 00:55:15 +0200 [thread overview]
Message-ID: <d911f8a2-a35d-e0a2-b19e-9eb907135812@petroprogram.com> (raw)
In-Reply-To: <20180116234700.545dad71@windsurf>
Hi
Thomas Petazzoni kirjoitti 17.01.2018 klo 00:47:
> Hello,
>
> On Wed, 17 Jan 2018 00:29:13 +0200, Stefan Fr?berg wrote:
>
>>>> depends on BR2_USE_WCHAR # glib2
>>>> depends on BR2_TOOLCHAIN_HAS_THREADS # glib2
>>>> depends on BR2_USE_MMU # glib2
>>>> depends on BR2_INSTALL_LIBSTDCPP # pango
>>>> depends on BR2_TOOLCHAIN_HAS_SYNC_4 # pango -> harfbuzz
>>>> *depends on BR2_PACKAGE_HAS_LIBEGL_WAYLAND || \ BR2_PACKAGE_HAS_LIBGL *
>> Is OpenGL *really* needed for libgtk3 ?
> I remember having a lengthy discussion back then with Gustavo, who said
> OpenGL was really needed. However, things might have evolved since then.
>
>> Im asking because I have a chrooted musl environment where I
>> intentionally tried to avoid any package that tries to pull OpenGL stuff
>> (like mesa, wayland etc...) and I managed to build
>> gtk3 just fine (version 3.22.26)
>>
>> Here's it's built conf (uses static libs, introspection disabled and
>> uses X11 backend):
>>
>> ./configure --prefix=/usr --sysconfdir=/etc --disable-nls
>> --disable-rpath --disable-shared --disable-modules --enable-static
>> --enable-x11-backend --enable-broadway-backend --disable-glibtest
>> --disable-cloudprint --disable-introspection --disable-gtk-doc
>> --disable-man --disable-gtk-doc-html --disable-gtk-doc-pdf --with-pic
> Does the result actually runs on some target platform ?
I really hope so.
I am currently, at this very moment, building my app against webkitgtk
in that chrooted environment
and if all goes well, I get a nice big static binary blob that I could
try with any Linux, no matter
what C-libc is being used. And should not need OpenGL.
As long as the CPU is x86_64 it should run.
>
> If so, it would definitely be nice to support gtk3 without OpenGL.
>
>
Great! I keep fingers crossed :-)
Regards
-S-
prev parent reply other threads:[~2018-01-16 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 15:23 [Buildroot] [PATCH 1/1] vte: new package Stefan Fröberg
2018-01-16 16:07 ` Thomas Petazzoni
2018-01-16 17:58 ` Stefan Fröberg
2018-01-16 22:29 ` Stefan Fröberg
2018-01-16 22:47 ` Thomas Petazzoni
2018-01-16 22:55 ` Stefan Fröberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d911f8a2-a35d-e0a2-b19e-9eb907135812@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox