开发学院手机开发 Symbian 开发 Qt for Symbian 入门之环境搭建阅读

Qt for Symbian 入门之环境搭建

　2010-05-31 20:18:00　来源：WEB开发网　闂傚倷绶氬ḿ褍螞閹绢喖绠柨鐕傛嫹

闂傚倷绀侀幉锟犲垂閻㈠灚宕查柟鎵閸庡秵銇勯幒鎴濃偓鐢稿磻閹炬枼妲堟繛鍡楃С濞岊亞绱撻崒姘扁枌闁瑰嚖鎷�

婵犵數濮幏鍐川椤撴繄鎹曢梻渚€娼уú銈吤洪妸鈺佺劦妞ゆ帊鑳堕埊鏇㈡煏閸モ晛浠х紒杈╁仱閺佹捇鏁撻敓锟�闂傚倷绶氬ḿ褍螞閹绢喖绠柨鐕傛嫹　　闂傚倷鑳舵灙缂佺粯顨呴埢宥夊即閵忕姵鐎梺缁樺姇閻忔氨鈧凹鍓熷娲垂椤曞懎鍓伴梺閫炲苯澧紒澶婄秺瀵濡歌閸嬫捇妫冨☉娆忔殘闂佷紮缍€娴滎剟鍩€椤掑倹鏆柛瀣躬瀹曚即寮借閺嗭箓鏌ㄩ悤鍌涘

核心提示：QLibraryInfo::location(QLibraryInfo::PluginsPath, if needed at compile time, or via the $$QT_PLUGINS_BASE_DIR variable defined in the data_caging_paths.prf feat

QLibraryInfo::location(QLibraryInfo::PluginsPath, if needed at compile time, or via the $$QT_PLUGINS_BASE_DIR variable defined in the data_caging_paths.prf feature file, if needed in the .pro file). If either the stub or the actual plugin.dll are missing, the plugin loading will fail. The stub contents are mostly irrelevant. Only the file name and timestamp matter (the stub timestamp is checked in plugin caching). If the DEPLOYMENT variable is used properly, the stub gets generated and deployed automatically and you don’t need to worry about it. See http://doc.trolltech.com/4.6-snapshot/qmake-variable-reference.html#deployment for details.

When loading plugins with QPluginLoader, do not give the plugin dll itself as a target, use the stub file instead, although for convenience you can use either “.dll” or “.qtplugin” as the suffix. E.g. if you have the plugin stub named as “c:/foo/bar.qtplugin”, and the actual plugin as is located at “c:/sys/bin/bar.dll”, you can use either QPluginLoader(“c:/foo/bar.dll”) or QPluginLoader(“c:/foo/bar.qtplugin”) to load the plugin. So basically you can treat the stub as you would the actual plugin on other platforms.

Q: Qt applications get an additional white window with a black cursor. How can I fix this?

A: This is a result of having the ‘stdioserver’ package installed. This application is a server process that redirects STDIN and STDOUT to a console window by default. This behavior can be be changed by modifying the configure file located at “C:systemdataconfig.ini”. The relevant change involves editing the [STDIO] section and changing STDIN and STDOUT to be:

STDIN = MEDIA1

STDOUT = MEDIA4

MEDIA1 and MEDIA4 should be of the type ‘file’ and should have a path pointing to “in.txt” or “out.txt” respectively and located in the same directory as “config.ini”. You must also ensure that the “in.txt” file actually exists