| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
qmake has been lately expanded with pkg_prerules / pkg_postrules support
which make it possible to customize .pkg file content via pro file.
In addition we have got template package file support which takes care
of expanding TARGET and PLATFORM variables from .pkg files before
creating .sis file.
With help of these features and since .pkg format supports conditional
install statements, we can now install only the S60 version specific
plugin to each HW. This saves disk usage a bit.
Task-number: 248061
Reviewed-by: Miikka Heikkinen
|
|
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this change Qt did not install to device which had sqlite3
already in ROM. Since we now install the sqlite3 only if it is not on
any drive, the installation works also with preinstalled sqlite.
Even better appraoch would be to use embedded SIS file for sqlite,
since that would allow sqlite3 upgrade without upgrading the whole Qt.
However we yet don't have such SIS, but once we get one from Symbian
this needs to be further changed.
Task-number: 258858
Reviewed-by: Miikka Heikkinen
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The included fixes / cleanups:
- QtLibs PKG filename changed
- Component name in Qt libs pkg changed to "Qt for S60"
* Done in order to make SISX upgrade possible after pre-release.
- Removed passing of 'fixedTarget' member variable as an argument
- Removed whitespaces from generated file names
- Fixed 'make sisx' calling syntax when custom makefile name used
- Fixed MAKEFILE variable content in generated makefiles
- Changed names of environment variables used by 'make sisx'
* Nee variables have 'QT_SISX_' prefix
Reviewed-By: Miikka Heikkinen
|
|
|
|
| |
Reviewed-by: Jason Barron
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
It is not currently supported anymore after QtScript switched to the
JavaScriptCore backend.
RevBy: Trust me
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Removed exports are marked ABSENT, as we're experimenting with how
hard it will be to maintain BC once these DEF files are final. There
were probably too many exports anyway, as I think I might have originally
frozen them with a version of RVCT that had the symbol visibility
issues.
Reviewed-by: TrustMe
|
|\ \
| |/ |
|
| |
| |
| |
| | |
RevBy: Trust me
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Note: these *will* change between now and the release of 4.6, they
should not be relied upon for anything - they are purely for
experimental purposes
Task-number: 259810 (partial)
Reviewed-by: TrustMe
|
|/
|
|
|
|
|
|
| |
Note: these *will* change between now and the release of 4.6, they
should not be relied upon for anything - they are purely for
experimental purposes
Webkit DEF files to follow in later commit...
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Task: 242139
This commit replaces Symbian specific 'depends' keyword in qmake
DEPLOYMENT variable with two more generic ones. The new keywords
are 'pkg_prerules' and 'pkg_postrules', and they allow developer to
pass raw data to PKG file. The strings in 'pkg_prerules' are added
before PKG file package-body headers and 'pkg_postrules' after them.
Correspondingly as old 'depends' keyword, the new keywords are not
parsed by qmake, so they must be in a format understood by Symbian
package generation tools.
Note that 'pkg_prerules' can also replace default language,
package-header and vendor statements in pkg file. If you decide to
override any of these statements, you need to pay attention that
also other statements stay valid.
|
|
|
|
| |
These need to be added to the DEPLOYMENT variable as well.
|
|
|
|
|
|
|
| |
Ensure that we build the plugins we need and also clean up the file
a bit to remove the symbian specific blocks that aren't needed. Also
we no longer need a separate .iby file for deploying the VG graphics
system since it is now nicely integrated into Qt.
|
|
|
|
| |
has been merged
|
|
|
|
| |
The STL config is stored in CONFIG qmake variable, not in QT_CONFIG.
|
| |
|
|
|
|
| |
RevBy: jbarron
|
| |
|
| |
|
|
|
|
| |
components when working on Tube HW.
|
|
|