Qt first impression - QTE and QT

QTE is QT / Embedded, it is a version of Qt, you know that it is not a subset of other versions (QT / X11, QT / Mac), just reversible, QTE is more than they include a larger class library, can be said to be Their extension. Just started, I was very vague to QTE, I didn't know its development model, and the status of the QT family, and I finally saw a little color.

QT and QTE have different documents: First, QTE is in the help document of Qt / X11, is not the home link, but hidden in Overviews - All overviews and howtos; see it, I think QTE hides Inside the QT, do you have any QTE's document as part of the Qt document? In fact, QTE and QT are different from: source code pack, installation package, configuration, compilation, and program operations, almost "parallel railroad tracks" can be described.

<1> Source package (reflected after decompression: QT-VER, you can't divide QT or QTE, huh, huh): QT: QT-X11-Commercial-Ver.Tar.gz QTE: Qt-Embedded-Ver-Commercial .tar.gz

<2> Configuration parameters (every time the application will change it, it is a bit annoying): export qtdir = ... export ld_library_path = ...

<3> Configuration, Compilation: First, you need to make a clear concept: QTE is not like VxWorks, with Tornado, later selection target (Target) platform to compile, you can choose to cross-compile. QTE is not, at least not used for compilation, debugging IDE, only one Designer, only to drag some controls, quickly generate UI files, then UI-> CPP file conversion. QTE Many things must be done during the Configure period, that is, each compile option (target platform, publish / debug version, which module support ...) change, there is a job that recompiles the entire QTE, and these in VxWorks Needless (I mean, you don't need to reinstall VxWorks and Tornado), only in Tornado can use the mouse point to use the mouse point. OK! Tour: QT and QTE can: ./configure make But know if QTE needs to configure parameters, QTE's Configure parameter has a lot, typical: -release / -debug-shared / -static-no- : Module includes: OpenGL, Table, Network, Canvas; -NO-XFT / -XFT: Does the anti-aliased font need XFT expansion libraries; -plateform : Specifies a host (Host) platform (here Target Just the platform name, not the target platform in the host-target);-xplateform : Specifies the target (Target) platform; Target includes: Linux-generic-g / linux-x86-g / linux-ARM-G / Linux- MIPS-G - QVFB: QTE unique parameters, is supported by default. <4> Compile Tools: Clear a concept: Qt can write your own Hello World at this time, but there is still a thing for QTE: qvfb - qt AVFB. QVFB: It is one of the qt Tools and one of QTE's Tools. Compile QT version qvfb: Enter $ qtdir / tools / qvfb / ;./configure; make if there is an error related to "-lqt-MT" library, indicating that other QTs have been installed before, affecting, enters Makefile, modify "-lqt -mt "to" -lqt "compile QTE version QVFB: Enter $ qtdir / tools / qvfb / ;./configure; make if there is an error related to" -lqt-MT "library, indicating that other QTs have been installed before, affecting Enter Makefile, modify "-lqt-mt" is "-lqte", of course, for the Application of QT / Embedded, you don't have to compile QVFB in Qt / Embedded.

<5> Run Application: Do not mention QT, only QTE; first start QT (notice QTE) QVFB: QTDIR / TOOLS / QVFB / QVFB then run QTE program: Qtedir / Examples / *** / *** -qws What is your favorite, you can start QTE's QVFB in QVFB in QT.