On Monday 27 April 2015 22:21:49 Uli Schlachter wrote:
> Hi,
>
> sorry, but which plugins in plugins are being used? I can't find anything
> like that.
>
> Also, as you mention it is a small library:
>
> $ size libxcb-errors.so
>text data bss dec hex filename
> 30900
Hi,
sorry, but which plugins in plugins are being used? I can't find anything like
that.
Also, as you mention it is a small library:
$ size libxcb-errors.so
textdata bss dec hex filename
309002632 8 335408304 libxcb-errors.so
$ size libQt5XcbQpa.so
text
On Monday 27 April 2015 12:58:23 Edward Sutton wrote:
> Are the configure settings used to build Qt releases version controlled or
> accessible by the public? I think knowing what the configure settings are
> would be useful?
They are. See
http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-too
Are the configure settings used to build Qt releases version controlled or
accessible by the public? I think knowing what the configure settings are
would be useful?
This is the configure that Qt tech support told me is used to build Android ( I
am not sure if that meant release builds? ):
Its a small library, so I think it is sensible to compile it in the plugin
(even with the error data). I don't think it makes much sense at current time
to check if there is a system version available and then use that. However,
what is bothering me is that this is code that we don't want to be
On 27 Apr 2015, at 00:53, Thiago Macieira wrote:
> On Sunday 26 April 2015 21:39:23 Uli Schlachter wrote:
>> The actual question that I want to ask with this mail: This is a new
>> external dependency. Is it ok to add this dependency to Qt?
>
> How common is that library? What distros often hav
Hi list(s),
I'm in the early development stage of a mobile app and I'm currently trying
to figure out which native API are mapped to Qt and which are not. Writing
native code is not a problem but I would avoid wasting time for reinventing
the wheel. :)
Among the other things I'm concerned with th
