Re: [SailfishDevel] Mer PIM build questions
Hi Lukáš, First of all it may be worth noting that there is a "slight" difference between Ubuntu and Mer/Sailfish OS operating systems :) This has at least two implications: 1) not all Mer packages can be build against Ubuntu without modifications and 2) packages built against Ubuntu are not likely to work when deployed to a device running Mer/Sailfish OS. If you are on Linux, get Sailfish OS Platform SDK [1]. If you are on Windows or Mac or if you want to use a Qt Creator based IDE on whichever platform, get Sailfish OS Application SDK [2]. There may be some hiccups while building these lower level packages with the application SDK but the workaround [3] pointed out by Chris shouldn't be needed unless I miss something. I tried to build buteo-sync-plugin-caldav with application SDK on Linux and Windows and the file permissions listed with `rpm -qlvp RPMS/*` seemed correct. The Qt Creator based IDE only works with qmake driven projects. A frequent issue with these lower level packages is that they do not use the magic qtc_* macros in their RPM .spec files. See this example project to learn how to use these macros [4] (referred by [5]). Without these macros the build tool `mb2` (used directly or indirectly via Qt Creator) cannot separate qmake and make execution and more. You can start your contribution by adding these macros to buteo-sync-plugin-* packages for your own convenience :) You don't need to bother with dependencies. All dependencies will be installed automatically upon the first build. BR, Martin [1] https://sailfishos.org/wiki/Platform_Development [2] https://sailfishos.org/wiki/Application_Development [3] You don't need this https://sailfishos.org/wiki/CalDAV_and_CardDAV_Community_Contributions#Development_With_The_Sailfish_OS_Application_Developer_SDK [4] https://github.com/sailfishos/cppqml-sample/blob/master/rpm/cppqml.spec [5] https://sailfishos.org/wiki/Tutorial_-_Combining_C%2B%2B_with_QML From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Lukáš Karas [lukas.ka...@centrum.cz] Sent: Thursday, January 18, 2018 4:35 PM To: devel@lists.sailfishos.org Subject: Re: [SailfishDevel] Mer PIM build questions Dne čtvrtek 18. ledna 2018 15:05:19 CET Pekka Vuorela napsal(a): > On Thu, 2018-01-18 at 12:57 +0100, Lukáš Karas wrote: > > Now the main question - when I try to build mer-core/timed, there are > > few > > `*.type` files that should be compiled by `iodata-qt5-type-to-c++` > > tool. > > But how this should be done in the build? In > > src/server/server.pro:17 > > is defined IODATA_TYPES with list of these files, but there is > > nothing about > > it in generated Makefile. There is some qmake plugin or preparison > > step > > that I overlook? > > server.pro: CONFIG += iodata-qt5 > Suppose that picks up above. libiodata there: > https://git.merproject.org/mer-core/libiodata > > Do wonder a bit where's the need for timed compilation, though. Timed is required by mKCal, see: https://git.merproject.org/mer-core/mkcal/blob/master/src/src.pro#L44 I do something wrong probably, I already have iodata in image: https://github.com/Karry/mer-devel/blob/master/pim-docker/Dockerfile > > ___ > 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
Re: [SailfishDevel] Mer PIM build questions
On 18/01/18 17:35, Lukáš Karas wrote: Timed is required by mKCal, see: https://git.merproject.org/mer-core/mkcal/blob/master/src/src.pro#L44 I do something wrong probably, I already have iodata in image: https://github.com/Karry/mer-devel/blob/master/pim-docker/Dockerfile I'm not quite sure what this docker thing is, but most likely you wouldn't have any problem if you used Mer OBS [1] to build rpms. Cheers, -Slava [1] https://build.merproject.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Mer PIM build questions
Hi Lukáš, Thanks very much for offering to help out with improving the Google sync plugins! The instructions for building the buteo-sync-plugins-social plugins should be very similar to those for building the caldav and carddav plugins - for those, see: https://sailfishos.org/wiki/CalDAV_and_CardDAV_Community_Contributions#Development_With_The_Sailfish_OS_Application_Developer_SDK Please see also https://sailfishos.org/wiki/Platform_Development for instructions on how to create a platform SDK target and build packages within in. Note that once you have an SDK target, you can install dependencies (like timed-devel) within it, without needing to build those dependencies yourself. If you have any issues, don't hesitate to get in touch! Thanks, Chris. From: Devel [devel-boun...@lists.sailfishos.org] on behalf of Karas [lukas.ka...@centrum.cz] Sent: Thursday, January 18, 2018 9:57 PM To: devel@lists.sailfishos.org Subject: [SailfishDevel] Mer PIM build questions Hi all. I am little bit frustrated from the state of PIM on SFOS. It is painful to use Sailfish on primary phone when you are using google services for managing contacts and calendars. From rare activity in buteo-sync-plugins-social repository [1] seems to me that noone is activelly developing it right now. Fot that reason, I want to resolve some bugs [2] myself and create merge request. Before any programming I need environment for build and testing. I want to create docker environment (x86_64) for testing [3]. I am really the first one who is trying it? I don't find any existing docker image with Mer components... It is possibly that I am going to wrong direction, but I have good experince with developign inside docker and it was my first choice... Now the main question - when I try to build mer-core/timed, there are few `*.type` files that should be compiled by `iodata-qt5-type-to-c++` tool. But how this should be done in the build? In src/server/server.pro:17 is defined IODATA_TYPES with list of these files, but there is nothing about it in generated Makefile. There is some qmake plugin or preparison step that I overlook? Regards, Lukas 1) https://git.merproject.org/mer-core/buteo-sync-plugins-social 2) https://together.jolla.com/question/162657/google-calendar-not-syncing-new-events/?sort=votes&page=1 3) https://github.com/Karry/mer-devel 4) https://git.merproject.org/mer-core/timed/blob/master/src/server/ server.pro#L17 ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Mer PIM build questions
Dne čtvrtek 18. ledna 2018 15:05:19 CET Pekka Vuorela napsal(a): > On Thu, 2018-01-18 at 12:57 +0100, Lukáš Karas wrote: > > Now the main question - when I try to build mer-core/timed, there are > > few > > `*.type` files that should be compiled by `iodata-qt5-type-to-c++` > > tool. > > But how this should be done in the build? In > > src/server/server.pro:17 > > is defined IODATA_TYPES with list of these files, but there is > > nothing about > > it in generated Makefile. There is some qmake plugin or preparison > > step > > that I overlook? > > server.pro: CONFIG += iodata-qt5 > Suppose that picks up above. libiodata there: > https://git.merproject.org/mer-core/libiodata > > Do wonder a bit where's the need for timed compilation, though. Timed is required by mKCal, see: https://git.merproject.org/mer-core/mkcal/blob/master/src/src.pro#L44 I do something wrong probably, I already have iodata in image: https://github.com/Karry/mer-devel/blob/master/pim-docker/Dockerfile > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org signature.asc Description: This is a digitally signed message part. ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Mer PIM build questions
Hi Rinigus. I don't need update QML frontend (it probably is closed-source), I want to fix just buteo plugin that is performing calendar synchronisation. It should be open-source, sources seems to be here: https://git.merproject.org/mer-core/buteo-sync-plugins-social/tree/master/src/ google Lukas Dne čtvrtek 18. ledna 2018 13:51:59 CET rinigus napsal(a): > Hi Liukas, > > I suspect you'll be hitting the closed source components: > > https://together.jolla.com/question/167645/open-source-roadmap-from-the-comm > unity-point-of-view/?answer=167780#post-id-167780 > > https://together.jolla.com/question/167645/open-source-roadmap-from-the-comm > unity-point-of-view/?answer=167658#post-id-167658 > > For some reason, there are no Jolla-backed replies regarding plans nor > timeline in opening them. > > As for buteo, I think you should be able to compile it (as much as you can) > on regular SDK. At least, as far as I remember, carddav/caldav could be > done there. As for `iodata-qt5-type-to-c++` tool - no idea. > > Good luck, > > Rinigus > > On Thu, Jan 18, 2018 at 1:57 PM, Lukáš Karas wrote: > > Hi all. > > > > I am little bit frustrated from the state of PIM on SFOS. > > It is painful to use Sailfish on primary phone when you are using google > > services for managing contacts and calendars. From rare activity > > in buteo-sync-plugins-social repository [1] seems to me that noone > > is activelly developing it right now. > > > > Fot that reason, I want to resolve some bugs [2] myself and create merge > > request. Before any programming I need environment for build and testing. > > I want to create docker environment (x86_64) for testing [3]. I am really > > the > > first one who is trying it? I don't find any existing docker image with > > Mer > > components... It is possibly that I am going to wrong direction, but I > > have > > good experince with developign inside docker and it was my first choice... > > > > Now the main question - when I try to build mer-core/timed, there are few > > `*.type` files that should be compiled by `iodata-qt5-type-to-c++` tool. > > But how this should be done in the build? In src/server/server.pro:17 > > is defined IODATA_TYPES with list of these files, but there is nothing > > about > > it in generated Makefile. There is some qmake plugin or preparison step > > that I overlook? > > > > Regards, Lukas > > > > 1) https://git.merproject.org/mer-core/buteo-sync-plugins-social > > 2) https://together.jolla.com/question/162657/google-> > > > calendar-not-syncing-new-events/?sort=votes&page=1 > > 3) https://github.com/Karry/mer-devel > > 4) https://git.merproject.org/mer-core/timed/blob/master/src/server/ > > server.pro#L17 > > ___ > > SailfishOS.org Devel mailing list > > To unsubscribe, please send a mail to devel-unsubscribe@lists. > > sailfishos.org signature.asc Description: This is a digitally signed message part. ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Mer PIM build questions
On Thu, 2018-01-18 at 12:57 +0100, Lukáš Karas wrote: > > Now the main question - when I try to build mer-core/timed, there are > few > `*.type` files that should be compiled by `iodata-qt5-type-to-c++` > tool. > But how this should be done in the build? In > src/server/server.pro:17 > is defined IODATA_TYPES with list of these files, but there is > nothing about > it in generated Makefile. There is some qmake plugin or preparison > step > that I overlook? server.pro: CONFIG += iodata-qt5 Suppose that picks up above. libiodata there: https://git.merproject.org/mer-core/libiodata Do wonder a bit where's the need for timed compilation, though. ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Mer PIM build questions
Hi Liukas, I suspect you'll be hitting the closed source components: https://together.jolla.com/question/167645/open-source-roadmap-from-the-community-point-of-view/?answer=167780#post-id-167780 https://together.jolla.com/question/167645/open-source-roadmap-from-the-community-point-of-view/?answer=167658#post-id-167658 For some reason, there are no Jolla-backed replies regarding plans nor timeline in opening them. As for buteo, I think you should be able to compile it (as much as you can) on regular SDK. At least, as far as I remember, carddav/caldav could be done there. As for `iodata-qt5-type-to-c++` tool - no idea. Good luck, Rinigus On Thu, Jan 18, 2018 at 1:57 PM, Lukáš Karas wrote: > Hi all. > > I am little bit frustrated from the state of PIM on SFOS. > It is painful to use Sailfish on primary phone when you are using google > services for managing contacts and calendars. From rare activity > in buteo-sync-plugins-social repository [1] seems to me that noone > is activelly developing it right now. > > Fot that reason, I want to resolve some bugs [2] myself and create merge > request. Before any programming I need environment for build and testing. > I want to create docker environment (x86_64) for testing [3]. I am really > the > first one who is trying it? I don't find any existing docker image with Mer > components... It is possibly that I am going to wrong direction, but I have > good experince with developign inside docker and it was my first choice... > > Now the main question - when I try to build mer-core/timed, there are few > `*.type` files that should be compiled by `iodata-qt5-type-to-c++` tool. > But how this should be done in the build? In src/server/server.pro:17 > is defined IODATA_TYPES with list of these files, but there is nothing > about > it in generated Makefile. There is some qmake plugin or preparison step > that I overlook? > > Regards, Lukas > > 1) https://git.merproject.org/mer-core/buteo-sync-plugins-social > 2) https://together.jolla.com/question/162657/google- > calendar-not-syncing-new-events/?sort=votes&page=1 > 3) https://github.com/Karry/mer-devel > 4) https://git.merproject.org/mer-core/timed/blob/master/src/server/ > server.pro#L17 > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscribe@lists. > sailfishos.org > ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] Mer PIM build questions
Hi all. I am little bit frustrated from the state of PIM on SFOS. It is painful to use Sailfish on primary phone when you are using google services for managing contacts and calendars. From rare activity in buteo-sync-plugins-social repository [1] seems to me that noone is activelly developing it right now. Fot that reason, I want to resolve some bugs [2] myself and create merge request. Before any programming I need environment for build and testing. I want to create docker environment (x86_64) for testing [3]. I am really the first one who is trying it? I don't find any existing docker image with Mer components... It is possibly that I am going to wrong direction, but I have good experince with developign inside docker and it was my first choice... Now the main question - when I try to build mer-core/timed, there are few `*.type` files that should be compiled by `iodata-qt5-type-to-c++` tool. But how this should be done in the build? In src/server/server.pro:17 is defined IODATA_TYPES with list of these files, but there is nothing about it in generated Makefile. There is some qmake plugin or preparison step that I overlook? Regards, Lukas 1) https://git.merproject.org/mer-core/buteo-sync-plugins-social 2) https://together.jolla.com/question/162657/google-calendar-not-syncing-new-events/?sort=votes&page=1 3) https://github.com/Karry/mer-devel 4) https://git.merproject.org/mer-core/timed/blob/master/src/server/ server.pro#L17 signature.asc Description: This is a digitally signed message part. ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
