Tadej Novak

`LD_LIBRARY_PATH`, `QML_IMPORT_PATH` and `QT_PLUGIN_PATH` are now referenced in the documentation.

Needs an update to the action to be able to set working directory.

We need stable Metal support so I do not plan this to be merged for version 3.0, but more for 3.1 or one of the later ones.

First the 3.0 release will be tagged with the OpenGL 2 backend. Then we can start thinking about Metal integration.

That's an interesting question. I think as long as no devices stop working, switching from OpenGL to Metal is not necessarily a breaking change. My idea was anyways to find...

The recent changes in `maplibre-gl-native` motivate spliting individual bindings/SDKs into separate repositories. For example the `main` branch there now does not work on macOS due to OpenGL update (until Metal...

Yes, that's correct. I want to put it in a separate library so we can make our custom public API, but still have it separated from core if people (like...

Indeed I plan to keep `QMapLibreGL` licensed under BSD to help Qt commercial users. For open-source users they are anyways directly bound by LGPL due to Qt itself.

> I wonder what would that "custom public API" would be. Is that something different from the one used by Qt in QtLocation QML? The end result will probably be...

Tagging also @kiibimees