Настройка производительности Qt
|
Creating a Static Build To compile Qt as a static library, use the -static option when running configure: ./configure -static To build the application suite as an all-in-one application, design each application as a stand-alone widget (or set of widgets) with only minimal code in the main() function. Then, write an application that provides a means of switching between the applications. The Qt Extended platform is an example using this approach: It can be built either as a set of dynamically linked executables, or as a single static application. Note that the application still should link dynamically against the standard C library and any other libraries which might be used by other applications on the target device. |
When installing end-user applications, this approach may not be an option, but when building a single application suite for a device with limited CPU power and memory, this option could be very beneficial.
The libraries shipped with some C++ compilers on some platforms have poor performance in the built-in "new" and "delete" operators. Improved memory allocation and performance may be gained by re-implementing these functions:
void *operator new[](size_t size) { return malloc(size); } void *operator new(size_t size) { return malloc(size); } void operator delete[](void *ptr) { free(ptr); } void operator delete[](void *ptr, size_t) { free(ptr); } void operator delete(void *ptr) { free(ptr); } void operator delete(void *ptr, size_t) { free(ptr); }
The example above shows the necessary code to switch to the plain C memory allocators.
When rendering, Qt uses the concept of a backing store; i.e., a paint buffer, to reduce flicker and to support graphics operations such as blending.
The default behavior is for each client to render its widgets into memory while the server is responsible for putting the contents of the memory onto the screen. But when the hardware is known and well defined, as is often the case with software for embedded devices, it might be useful to bypass the backing store, allowing the clients to manipulate the underlying hardware directly. There are two approaches to direct painting: The first approach is to set the Qt::WA_PaintOnScreen window attribute for each widget, the other is to use the QDirectPainter class to reserve a region of the framebuffer. For more information, see the direct painting section of the architecture documentation.
Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies) | Торговые марки | Qt 4.5.3 |
Попытка перевода Qt документации. Если есть желание присоединиться, или если есть замечания или пожелания, то заходите на форум: Перевод Qt документации на русский язык... Люди внесшие вклад в перевод: Команда переводчиков |