On Dec 6, 2014 8:30 PM, "Lorn Potter" wrote:
>
>
> On 5 Dec 2014, at 2:38 am, Alejandro Exojo wrote:
>
> >
> > Then I searched a bit in the branch of the mer-qt/qtbase repo. I see
you don't
> > use any mkspec for SailfishOS or Jolla, right? That's where I thought
you
> > might have it, and where
Andrey, Michael,
Thank you for your responses.
I am sorry, my mails about this questions got lost and I just found your
responses on google again :^). Unfortunately, there doesn't exist any official
documentation about that on https://sailfishos.org/ or a similar site.
I found a very helpful blo
On 5 Dec 2014, at 2:38 am, Alejandro Exojo wrote:
>
> Then I searched a bit in the branch of the mer-qt/qtbase repo. I see you
> don't
> use any mkspec for SailfishOS or Jolla, right? That's where I thought you
> might have it, and where I think it could be. Blackberry sets there the
> QMAK
At least my C++ includes have the same names.
The difference is the implementation but all implementations adhere to the same
interface.
Cheers,
On Dec 6, 2014 2:46 PM, Tone Kastlunger wrote:
I think the idea to include different project files for defining which platform
to compile on is a co
Also, you can raise awareness to contact you via email.
That has worked quite fine at least for my app (Quickbar).
On Fri, Dec 5, 2014 at 5:45 PM, wrote:
> Just asked this from dev-care and they are working on it. Not soon I think
> but it's on the roadmap at least.
>
> Andrey Kozhevnikov kirjoi
I think the idea to include different project files for defining which
platform to compile on is a correct workaround;
however, this forces you to include files with different names depending on
which system you want to compile on,
which means you need to have specific .pro files; which is ok, of c
