you can set INSTALLS = without appending to existing contents and
manually point to desktop (if present) and binary files
On 17.02.2014 19:51, Thomas Perl wrote:
On 2014-02-17 14:43, J-P Nurmi wrote:
Not a bug but an (annoying) feature. :) You probably have "CONFIG +=
sailfishapp" in your .pro
On 2014-02-17 14:43, J-P Nurmi wrote:
Not a bug but an (annoying) feature. :) You probably have "CONFIG +=
sailfishapp" in your .pro. That will automatically add the qml
subfolder to install rules
(https://github.com/sailfish-sdk/libsailfishapp/blob/master/data/sailfishapp.prf#L40).
A trivial
On Mon, Feb 17, 2014 at 2:24 PM, itviewer wrote:
> Hi all，
>
> In my application I don't want the qml file to be deployed.
> I know I should use the Qt resource system.
>
> After added all qml files to the .qrc file and rebuild the application，
>
> It seems that all qml files are still build in
Hi all，
In my application I don't want the qml file to be deployed.
I know I should use the Qt resource system.
After added all qml files to the .qrc file and rebuild the application，
It seems that all qml files are still build in to the rpm file.
Is it a sdk's bug?
How can I deploy rpm applicatio
