How I used to do it in the past building for both Symbian and MeeGo was to
have .pro file hierarchy as you anyway need to have some .pro file
specifics. I know several ways you can go
**.pro level**
1. Just different .pro for the different platforms and that's it
They even might include different
On Thu, Nov 21, 2013 at 5:10 PM, Andrey Kozhevnikov
wrote:
> check __ARMEL__ or __ARM_ARCH_7__
Thank you, Andrey, but that is not what I was referring to.
Basically, I would like to have my package built for sailfish (and
install the sailfish qml files) when I select a sailfish target, and
say,
Is it possible to install files directly via .yaml/.spec (without using the
qmake installs)?
--
Marcin
2013/11/21 Andrey Kozhevnikov
> check __ARMEL__ or __ARM_ARCH_7__
>
>
> On 21.11.2013 21:37, Luciano Montanaro wrote:
>
>> For the record, I also have problems,. whenever I switch between
>>
Thanks.
Removing and adding kits seems to generate new .yaml file based on .pro
and .pri.
On 11/21/2013 11:11 AM, Andrey Kozhevnikov wrote:
create sailfish project, or dont use yaml, use spec.
On 21.11.2013 16:01, Wim de Vries wrote:
Hi Artem,
Thanks for the reply.
Best way would then to ch
i have src/client and src/server and everything is built correctly
automatically.
On 21.11.2013 21:05, Artem Marchenko wrote:
Yes, Qt Creator plugin trying to modify .yaml is a big annoyance to
anybody with non standard .yaml (I have src/test subprojects and
plugin is apparently able to work w
For the record, I also have problems,. whenever I switch between
ARM/486 builds or between sailfish and harmattan.
A slightly different topic...
Is there a way to detect the kit in use from the qmake file?
Currently, I add CONFIG+=sailfish on the build options when I want to
build for sailfish..
check __ARMEL__ or __ARM_ARCH_7__
On 21.11.2013 21:37, Luciano Montanaro wrote:
For the record, I also have problems,. whenever I switch between
ARM/486 builds or between sailfish and harmattan.
A slightly different topic...
Is there a way to detect the kit in use from the qmake file?
Current
Yes, Qt Creator plugin trying to modify .yaml is a big annoyance to anybody
with non standard .yaml (I have src/test subprojects and plugin is
apparently able to work with one package only). How I solved it, I just
keep resetting .yaml to version from version control whenever QtCreator
wants to be
create sailfish project, or dont use yaml, use spec.
On 21.11.2013 16:01, Wim de Vries wrote:
Hi Artem,
Thanks for the reply.
Best way would then to change .yaml, I guess.
But somehow there is no .yaml in the rpm dir.
Tried to add an empty one hoping that qmake or rebuild would fill it,
but rem
Hi Artem,
Thanks for the reply.
Best way would then to change .yaml, I guess.
But somehow there is no .yaml in the rpm dir.
Tried to add an empty one hoping that qmake or rebuild would fill it,
but remains emty.
Any idea how to get the yaml created?
Thanks.
On 11/20/2013 09:45 PM, Artem Marche
You need to mention these files in .yaml (or user editable part of .spec
that's generated from .yaml).
Basically here's what happens:
1. Your project files are mounted to the virtual build machine
2. make install copies data to the appropriate "final" folders on the build
machine (not visible fro
Hi,
I am able to deploy via RPM. Or better, QtCreator is able to do it ;-)
Still, I need to install some data files as well.
pro file:
data.files = checklistsdata/*
OTHER_FILES += \
checklistsdata/skyArrow-walkaround \
checklistsdata/skyArrowEMERGENCY \
.
In the .pri:
data.path = /ho
12 matches
Mail list logo
