summaryrefslogtreecommitdiffstats
path: root/tools/designer
diff options
context:
space:
mode:
authorJaakko Helanti <ext-jaakko.helanti@nokia.com>2012-01-16 10:48:39 (GMT)
committerQt by Nokia <qt-info@nokia.com>2012-01-17 01:54:10 (GMT)
commitbb5cba5dcc3f3453ccbfea2667adc3a12c4ba92b (patch)
tree402c5582d2c3077562aa7ba2307cb001b70d5e88 /tools/designer
parent68f2155cd27f669559dd0f877156d81deda8bf73 (diff)
downloadQt-bb5cba5dcc3f3453ccbfea2667adc3a12c4ba92b.zip
Qt-bb5cba5dcc3f3453ccbfea2667adc3a12c4ba92b.tar.gz
Qt-bb5cba5dcc3f3453ccbfea2667adc3a12c4ba92b.tar.bz2
Symbian: qmake: Fix emulator deployment destinations
This fix affects how qmake generates "bld.inf" file. Earlier, all emulator deployments went to epoc32/winscw/c, which is the C-drive of the emulator. However, emulator implementation expects often to find deployments from epoc32/release/winscw/udeb/z, which is the ROM drive of the emulator. For this reason many things, including QML deployments, did not work in the emulator. Now the fixed deployment is as follows: - If pro-file deployment has no path value, it goes to emulator ROM drive. - If pro-file deployment has path variable with no drive letter, it goes to emulator ROM drive. - If pro-file deployment has path variable with drive letter, it goes to the given emulator drive. - If pro-file deployment has path variable with '!' as drive letter, it goes to emulator C drive. When making emulator ROM-drive deployment, two deployments are made, one to udeb and one to urel emulator. Task-number: ou1cimx1#954237 Change-Id: I62d3f5b479ee0c0c547e824bb45ae8c0a6484d87 Reviewed-by: Jaakko Helanti <ext-jaakko.helanti@nokia.com> Reviewed-by: Pasi Pentikäinen <ext-pasi.a.pentikainen@nokia.com>
Diffstat (limited to 'tools/designer')
0 files changed, 0 insertions, 0 deletions