Thomas Perl wrote:
> Why do you want to use Qt Resources instead of deploying the files to
> the filesystem?
To hide SOME code from those who like to just copy&paste rather than ask for
permission or credit the source. Not from everyone, just from those
"copy&pasters". Some time ago I had m
Thomas Perl wrote:
> Why do you want to use Qt Resources instead of deploying the files to
> the filesystem?
To "hide" some of QML code away from prying eyes. Of course, I know that it's
a very poor protection as it is just compression so everything can be easily
extracted, but that's actua
On 2014-04-24 00:36, Kim Foder wrote:
On Wed, 2014-04-23 at 22:53 +0200, tw_bolek wrote:
- manually edit Makefile and remove qml_install and qml_uninstall
- in .specs file remove /usr/share/myappand %{_datadir}/%{name}/qml
lines
I usually do this by renaming the qml folder, create a n
> I usually do this by renaming the qml folder, create a new qml folder,
> and create en empty qml file in the folder (otherwise the deploy fails).
>
> This changes the path to files included in the resource, so they have to
> be added again.
Good idea...
Anyway, let's hope that this gets corre
On Wed, 2014-04-23 at 22:53 +0200, tw_bolek wrote:
> - manually edit Makefile and remove qml_install and qml_uninstall
> - in .specs file remove /usr/share/myappand %{_datadir}/%{name}/qml
> lines
I usually do this by renaming the qml folder, create a new qml folder,
and create en empty
I've just managed to build rpm without the freakin' qml folder, but in order
to do that I additionally needed:
- manually edit Makefile and remove qml_install and qml_uninstall
- in .specs file remove /usr/share/myappand %{_datadir}/%{name}/qml
lines
Don't mean to be rude or something
Yes, I did "clean", deleted the whole build folder, then did "clean" again.
That FREAKING folder still gets added
> did you made "clean" and removed build folder content?
>
> 24.04.2014 01:16, tw_bolek пишет:
> >
> > Doesn't work, either :(( The qml folder is still added to rpm.
> > And
did you made "clean" and removed build folder content?
24.04.2014 01:16, tw_bolek пишет:
Doesn't work, either :(( The qml folder is still added to rpm.
And while building the rpm I get messages about "overriding commands for target
'install_desktop'", "ignoring old commands for target 'insta
Doesn't work, either :(( The qml folder is still added to rpm.
And while building the rpm I get messages about "overriding commands for
target 'install_desktop'", "ignoring old commands for target 'install_icon'",
etc.
> okay, then try this:
> desktop.files = $${TARGET}.desktop
> deskt
okay, then try this:
desktop.files = $${TARGET}.desktop
desktop.path = /usr/share/applications
icon.files = $${TARGET}.png
icon.path = /usr/share/icons/hicolor/86x86/apps
INSTALLS = desktop icon
24.04.2014 00:56, tw_bolek пишет:
show your full pro file
Hey Andrey, here you are. Nothing speci
> show your full pro file
Hey Andrey, here you are. Nothing special in there.
# The name of your app.
# NOTICE: name defined in TARGET has a corresponding QML filename.
# If name defined in TARGET is changed, following needs to be
# done to match new name:
# - corre
show your full pro file
24.04.2014 00:39, tw_bolek пишет:
Doesn't work :(
INSTALLS -= qml doesn't seem to do anything, and renaming the qml folder
results in an RPM build error - files not found
Anything else, please?
Gosh, it was so easy and obvious in Qt4.8
Thank you,
Bolek
you ca
Doesn't work :(
INSTALLS -= qml doesn't seem to do anything, and renaming the qml folder
results in an RPM build error - files not found
Anything else, please?
Gosh, it was so easy and obvious in Qt4.8
Thank you,
Bolek
> you can try to add INSTALLS -= qml somewhere after
> sailfishapp
you can try to add INSTALLS -= qml somewhere after sailfishapp config
line, or just rename folder name
23.04.2014 14:19, tw_bolek пишет:
Thank you!!! Yes, QUrl("qrc:/myapp/main.qml") does the job!!
Now, *PLEASE*, one more help request:
what is the best way to EXCLUDE the qml folder from bein
Thank you!!! Yes, QUrl("qrc:/myapp/main.qml") does the job!!
Now, *PLEASE*, one more help request:
what is the best way to EXCLUDE the qml folder from being added to the rpm file?
Thank you,
B.
> I don't think you should use SailfishApp::pathTo since it points
>to a file in data director
> PROBLEM: what path should I use in the main.cpp file to point to the main qml
> file in the resource?
> SailfishApp::pathTo("qrc:/qml/main.qml") returns
> /usr/share/myapp/qrc/qml/main.qml - not found
To load the QML file from resource, you should not use SailfishApp::pathTo,
instead use QU
On Wednesday 23 of April 2014 09:23:29 tw_bolek wrote:
> Hi guys,
>
> I've put all my qml files into a resource file and I did NOT include the qml
> folder in the rpm.
>
> PROBLEM: what path should I use in the main.cpp file to point to the main qml
> file in the resource?
>
> SailfishApp::pat
Hi guys,
I've put all my qml files into a resource file and I did NOT include the qml
folder in the rpm.
PROBLEM: what path should I use in the main.cpp file to point to the main qml
file in the resource?
SailfishApp::pathTo("qml/main.qml") returns /usr/share/myapp/qml/main.qml -
not found
18 matches
Mail list logo
