tl;dr: When I work on the client for the macOS file provider extension on a daily basis with a plain Nextcloud Docker container on localhost via HTTP and admin:admin and just demo content I want to leave out the build and inclusion of a whole Chrome engine every time I build the app (which happens often) and only include it when necessary.
Situation
- Our client includes a whole QtWebEngine (basically Chromium) to support global scale login.
- That makes up half of our app and bloats it significantly. See Nextcloud Desktop Client Size Analysis for a detailed analysis.
- There is a
BUILD_WITH_WEBENGINE switch in our build system but it only controls the linking against, not the build and inclusion, of the QtWebEngine dependency.
Goals
- Disable
BUILD_WITH_WEBENGINE by default in local developer builds in developer environments. This is particularly relevant for (in example) the macOS file provider extension (specifically the NextcloudDev target).
- Drastically reduce our app size.
- Drastically speed up the build times.
- Maybe restrict the global scale login to customer branded clients of relevance as a feature flag in our CI?
- Reduce feedback loop of contributors between code changes and actually running the build significantly.
Dependencies
tl;dr: When I work on the client for the macOS file provider extension on a daily basis with a plain Nextcloud Docker container on
localhostvia HTTP andadmin:adminand just demo content I want to leave out the build and inclusion of a whole Chrome engine every time I build the app (which happens often) and only include it when necessary.Situation
BUILD_WITH_WEBENGINEswitch in our build system but it only controls the linking against, not the build and inclusion, of the QtWebEngine dependency.Goals
BUILD_WITH_WEBENGINEby default in local developer builds in developer environments. This is particularly relevant for (in example) the macOS file provider extension (specifically theNextcloudDevtarget).Dependencies