[Development] Porting QT to new OS
drwho
drwho at infidigm.net
Thu Nov 7 16:50:31 CET 2019
On 2019-11-07 10:31 a.m., Konstantin Tokarev wrote:
> 07.11.2019, 18:08, "drwho" <drwho at infidigm.net>:
>> On 2019-11-07 12:42 a.m., Thiago Macieira wrote:
>>> On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
>>>
>>>> 4) What about the memory footprint?
>>> A couple of megabytes.
>> I'd love to see a build how too that results in a couple of megabytes.
>> The smallest I've ever got Qt with a "cut everything out" configure is...
>>
>> text data bss hex filename
>>
>> 5199292 129564 11596 517d24 libQt5Core.so.5.6.2
>>
>> 3904283 81384 10616 3cfa7b libQt5Gui.so.5.6.2
>>
>> 4893838 212704 840 4deeb6 libQt5Widgets.so.5.6.2
> This is ELF section sizes, not a memory footprint. Actual memory footprint (RSS/PSS values) can be obtained from smaps file
A simple console only application (only using QtCore) I built using a
static Qt build without -ltcg is about 4MB memory foot print on arm...
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1129 root 20 0 14244 4004 3848 S 0.0 1.6 0:00.01 simple_app
Using -ltgc saves about 31%, so aprox 3MB memory footprint.
Using a dynamically linked Qt version, I've seen memory footprints as
low as 200K for console only applications.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20191107/4c42d964/attachment.html>
More information about the Development
mailing list