| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
It makes no sense for 'sis' to depend on 'first' or really any target
in symbian-abld and symbian-sbsv2 builds, as all builds are recursive
anyway.
Also do not generate real sis targets for projects that do not
actually deploy anything, making the check equivalent to one
in qmake for generating pkg files.
Task-number: QTBUG-5312
Reviewed-by: Janne Koskinen
|
| |
|
|
|
|
|
| |
Checking just for count can fail when default_deployment is replaced
with single custom deployment item.
Reviewed-by: Janne Koskinen
|
| |
|
|
| |
this makes windows-style path specs *ugly*. that's intentional. :-P
|
| |
|
|
|
|
|
|
| |
Convert paths in DEPLOYMENT to the rom drive (z:)
Filter out unwanted parts of the header (dependencies)
Task-number: QTBUG-10118
Reviewed-by: Alessandro Portale
|
| |
|
|
|
| |
After default_deployment was added as default option our test for
project type was not reached anymore. Fix that.
|
|
|
The sis target will depend on the main build target of each project,
which should make it possible to simply run "make sis" in the root of
a clean tree (after configure, of course), and have sis packages
generated for everything. It works at least for Qt.
This required some changes to the dependency generation in Qt, to
make sure that s60installs builds its package after all of Qt, and
that fluidlauncher has all the required files before building a
package.
In addition, all the sis target code was moved into its own qmake
feature file, called sis_targets. It is currently enabled by default
for Symbian.
|
