{"id":13166,"date":"2022-09-20T07:48:00","date_gmt":"2022-09-20T05:48:00","guid":{"rendered":"https:\/\/www.opengis.ch\/?p=13166"},"modified":"2022-10-13T09:02:49","modified_gmt":"2022-10-13T07:02:49","slug":"how-we-build-qfield-for-many-platforms-a-look-behind-the-curtain","status":"publish","type":"post","link":"https:\/\/www.opengis.ch\/it\/2022\/09\/20\/how-we-build-qfield-for-many-platforms-a-look-behind-the-curtain\/","title":{"rendered":"How we build QField for many platforms – A look behind the curtain"},"content":{"rendered":"\n

In the past year, the build system behind QField has been ported to vcpkg, a modern C++ dependency management system<\/a><\/strong>. It has been a great success for QField and considerably helped to streamline efforts, improve the development experience and to guarantee an outstanding stability of the application. In this blog post we will look at the history of building QGIS based applications for mobile systems and how it has become what it is today.<\/em><\/p>\n\n\n\n

When Marco Bernasocchi (CEO of OPENGIS.ch and chair of QGIS.org) started working on QGIS for Android<\/strong> in Google Summer of Code<\/a> a decade ago, the main job was to also build all QGIS dependencies for Android. This includes well-known libraries like proj<\/strong> and gdal<\/strong> and less-known ones like libxml2 or iconv. Each of them has its particularities and specific build flags. Working on this appears to be an endless iterative trial-and-error journey where you hope each day that eventually you will see the QGIS splash screen on your Android phone<\/a> while all you see are endless lines of code and compiler errors.<\/p>\n\n\n\n

As we know nowadays QGIS for Android has eventually seen the sunlight and its achievements are still the base for QGIS-based mobile apps like QField<\/a>.<\/p>\n\n\n\n

Sometime later we decided to modernize the build infrastructure into OSGeo4A a set of scripts where each dependency was built with a “recipe”. Modularized this way, it was easier to maintain, and general build code common for all libraries could be isolated. It was good enough to help drive QField for a couple of years, and a copy of it is still in use as the base for nowadays QGIS builds for macOS<\/a><\/strong>.<\/p>\n\n\n\n

When we decided to make QField also available on other platforms like iOS, Windows and macOS<\/strong> we quickly realized that duplicating build chains scales really bad and maintaining this is an immense effort we wanted to avoid. There are a couple of existing C++ dependency management systems, none of which convinced us ultimately. Lucky for us a mail on the QGIS mailing list mentioned a new one called vcpkg<\/a> which looked very promising.<\/p>\n\n\n\n

A couple of days later we had a build for Windows and later in the same year for macOS. With many dependencies already available in modern versions. Cheers.<\/p>\n\n\n\n

What’s left to do than just enable it for Android, and all our problems are suddenly solved? Alas, it’s not so easy. Cross-compiling is always a bit trickier.<\/strong> And so we started another journey to improve the situation. After a while, we had a working build chain based on vcpkg for Android in our R&D labs. Interestingly, this added a couple of features just because the community around vcpkg had already added them. For example using COG<\/a>-based raster data via HTTP was suddenly working (for the record: thanks to the availability of curl which we never took care of adding ourselves in OSGeo4A)<\/em>.<\/p>\n\n\n\n

Soon after we also wanted to try building for iOS with vcpkg<\/strong>, which after a few attempts also was successful, and even managed to resolve some weird crashes and other issues we had experienced with the old buildchain.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The main benefit was that we could upgrade the QGIS base libraries in one single place for every platform, in an isolated branch without playing the Jenga game on each upgrade. <\/p>\n\n\n\n

The only unfinished business we still had was that support for iOS and Android was still available only in our own vcpkg fork.<\/p>\n\n\n\n

So the last few weeks and months we have been working closely with upstream<\/strong> to bring building for Android and iOS up to the same level as desktop platforms. The relevant parts are now in a clean state. <\/p>\n\n\n\n

Advantages of this approach:<\/p>\n\n\n\n