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 course, but kind of just pushes the problem a bit further away, and does not make it disappear.
On Fri, Dec 5, 2014 at 4:03 PM, Mohammed Hassan < mohammed.has...@jollamobile.com> wrote: > On Thu, Dec 04, 2014 at 10:12:37PM +0200, Tone Kastlunger wrote: > > Anything that makes a developer's life easier is absolutely welcomed > > I'd say. > > I must admit to have cursed many times over such a feature not being > > present (either as macro OR as selectior that win32:unix:mac: are..) > > best, > > tortoisedoc > > I have an application which I build for Harmattan, SailfishOS and Android. > > I have a common C++ codebase (95% common maybe), A QML abstraction and > platform specific QML ui bits. > I also have a separate .pro file per platform. > Each .pro file adds an OS specific macro. > harmattan.pro adds -DHARMATTAN=1 > sailfish.pro adds -DSAILFISH=1 > android.pro adds -DANDROID=1 > > Here is an example: > https://gitorious.org/quran/quran/source/sailfish/sailfish.pro > https://gitorious.org/quran/quran/source/n9/n9.pro > > Works fine for me. > > Cheers, > _______________________________________________ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org >
_______________________________________________ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
