Currently F-Droid builds split architecture .apks
by invoking ndk-make.sh with architecture argument.
This results in debug builds of the core.
This change makes debug builds explicit.
Setting __ANDROID_API__ manually causes
'__ANDROID_API__' macro redefined [-Werror,-Wmacro-redefined]
when compiling the `ring` crate dependency.
TARGET_CC wrapper should set necessary variables itself.
See similar issue in the `ring` bugtracker for explanation:
https://github.com/briansmith/ring/issues/1519
This allows to build the core on systems without rustup.
In this case system rust is used,
but there is no error due to `+1.64.0`
being unknown argument to non-rustup cargo.
Common way to configure `mold` is to set
RUSTFLAGS="-C linker=clang -C link-arg=-fuse-ld=/usr/bin/mold"
This breaks cross-compilation, as wrong linker is used.
* update CHANGELOG for 1.34.13
* nudge outselves to drop a line about what to test
the changelog is not always sufficient for that.
* bump version to 1.34.13
* factor out checkmark strings
* no automatic remote content for contact requests
loading remote content in contact requests
now always require explicit consent of the user.
moreover, contact request do not alter
the otherwise used never/once/always settings.
* re-applying patch from @Hocuri from #2458
* apply sandbox isolation patch from @WofWca
* wait for gc as suggested by @WofWca, @Simon-Laux and others
* Update res/raw/sandboxed_iframe_rtcpeerconnection_check.html
Co-authored-by: WofWca <wofwca@protonmail.com>
* Update res/raw/sandboxed_iframe_rtcpeerconnection_check.html
Co-authored-by: WofWca <wofwca@protonmail.com>
* improve progress bar, inspired by @Simon-Laux and @WofWca
* comment about the gist of setNetworkAvailable()
* unify url-loading; this cleans up things and makes adding CSP more straight-forward
---------
Co-authored-by: WofWca <wofwca@protonmail.com>
successor of #2444:
- there seems to be a maximal lenght of 500 characters for the changelog
(the 500 chars come from the changlog in #2444
that was truncated after 500 characters)
- the changelog is only needed if there is really a f-droid release scheduled;
move the instructions down
* update CHANGELOG for 1.34.9
* bump version to 1.34.9
* add a little device message for the 1.34.9 update
* add f-droid changelog
* make device message more clear and add it only for existing installations
* bump to 1.34.10
