libX11 also ends up being linked into the eglfs platform plugin. Even when
configured with -no-xcb. I must be missing something, otherwise how could any
of the non-X11 embedded or Raspberry Pi stuff work… Of course you can build on
a machine that doesn't have the libs or headers available; I
On Friday, 29 August, 2014 7:09:55 Rutledge Shawn wrote:
libX11 also ends up being linked into the eglfs platform plugin. Even when
configured with -no-xcb.
There is a xcb backend (eglfshooks) for X11 .. maybe they have been selected
for some reason?
I must be missing something, otherwise
All,
I'm building the latest from dev branch using the following options
(on 64-bit Ubuntu 12.04):
-opensource -confirm-license -developer-build -release -no-gui
-no-widgets -no-cups -no-dbus -no-xcb
However the build fails with the following message:
The test for linking against libxcb and
Probably just an oversight; the configure script is supremely under
loved and makes several demented assumptions which go largely
unaddressed.
Ideally everyone would scratch their own itch apropos the configure
script, so if you remove this assumption and upstream it, maybe one
day it will be a
Yes, I feel the lack of love too! :)
I'll open a bug to track it (and possibly fix it if I get time).
-mandeep
On Thu, Aug 28, 2014 at 4:21 PM, Donald Carr sirsp...@gmail.com wrote:
Probably just an oversight; the configure script is supremely under
loved and makes several demented
On Thursday 28 August 2014 16:21:27 Donald Carr wrote:
Probably just an oversight; the configure script is supremely under
loved and makes several demented assumptions which go largely
unaddressed.
under loved is an understatement.
--
Thiago Macieira - thiago.macieira (AT) intel.com
