On Thu, Nov 21, 2013 at 5:10 PM, Andrey Kozhevnikov
coderusin...@gmail.com 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
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
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
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
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
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?
Is it possible to install files directly via .yaml/.spec (without using the
qmake installs)?
--
Marcin
2013/11/21 Andrey Kozhevnikov coderusin...@gmail.com
check __ARMEL__ or __ARM_ARCH_7__
On 21.11.2013 21:37, Luciano Montanaro wrote:
For the record, I also have problems,. whenever I
