[Development] Why is libxcb needed if GUI is disabled in build?

[Mandeep Sandhu]

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 <sirspudd at gmail.com> wrote:
> 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 little less poxy.
>
> Cheerio,
> Donald
>
> On Thu, Aug 28, 2014 at 4:11 PM, Mandeep Sandhu
> <mandeepsandhu.chd at gmail.com> wrote:
>> 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 support libraries failed!
>>  You might need to install dependency packages, or pass -qt-xcb.
>>
>> As I understand libxcb provided C language bindings for the X
>> protocol. However if GUI is disabled, why do we still need xcb? Is it
>> because X also handles mouse/keyboard input?
>>
>> Also, it would be nice if the configure 'help' output would show which
>> options are selected by default, eg is "-gui" or "-no-gui" the default
>> option?
>>
>> Thanks,
>> -mandeep
>> _______________________________________________
>> Development mailing list
>> Development at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>
>
>
> --
> -------------------------------
>  °v°  Donald Carr
> /(_)\ Vaguely Professional Penguin lover
>  ^ ^
>
> Cave canem, te necet lingendo