diff options
| author | Michele Calgaro <michele.calgaro@yahoo.it> | 2018-09-27 14:18:50 +0900 |
|---|---|---|
| committer | Michele Calgaro <michele.calgaro@yahoo.it> | 2018-09-27 14:18:50 +0900 |
| commit | 9f5d59f33644aaadd7af43db86734a3294250a02 (patch) | |
| tree | 4a15ec2d023078bbee1a5b00dfb02e72972d0cd3 /doc/qws.doc | |
| parent | ff63338d189a49a16b29a503ba23727cfa7e2e66 (diff) | |
| download | tqt3-9f5d59f33644aaadd7af43db86734a3294250a02.tar.gz tqt3-9f5d59f33644aaadd7af43db86734a3294250a02.zip | |
qt -> tqt conversion:
qtlib -> tqtlib
libqt -> libtqt
QTLIB -> TQTLIB
LIBQT -> LIBTQT
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/qws.doc')
| -rw-r--r-- | doc/qws.doc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/qws.doc b/doc/qws.doc index c6e366267..b294ec7c5 100644 --- a/doc/qws.doc +++ b/doc/qws.doc @@ -567,9 +567,9 @@ The following guidelines will improve CPU performance: A lot of CPU and memory is used by the ELF linking process. You can make significant savings by using a static build of your application suite. This means that rather than having a dynamic library (\c -libqte.so) and a collection of executables which link dynamically to +libtqte.so) and a collection of executables which link dynamically to that library, you build all the applications into a single executable -and statically link that with a static library (\c libqt.a). This +and statically link that with a static library (\c libtqt.a). This improves start-up time, and reduces memory usage, at the expense of flexibility (to add a new application, you must recompile the single executable) and robustness (if one application has a bug, it might |