* show 'remove relay' items in red
* show concrete meaning of 'default' or 'main'
* prepare for showing 'unpublished' state
* rework 'remove relay' dialog
* fix RPC building doc and remove temp. file
* add hint to be shown below relay list
* adapt to new core api
* use listTransportsEx()
* use rpc.setTransportUnpublished()
* keep hidden
* tweak remove dialog in case the relay is already hidden
* adapt to chat.delta.rpc.types.TransportListEntry classname
* remove outdated autogenerated file
* update CHANGELOG
* simplify deletion
* make spotless happy
* change button order so hide/delete are not together usually; this matches also more the gist of positive/negative/neutral
* Update src/main/res/values/strings.xml
Co-authored-by: Hocuri <hocuri@gmx.de>
* the dialog wording fits better when already hidden now
* move similar strings together, make translation easier
* actions are 'Title Case', however, this usually applies to nouns, verbs, adjectives, first and last word only, not to prepositions as 'from'
---------
Co-authored-by: Hocuri <hocuri@gmx.de>
Running ndk-make.sh triggers a complete rust rebuild, because some compiler flags are changed. Then when you run a normal cargo command again (cargo check etc.), there is another rebuild. My solution is to locally change the target directory. This PR makes ndk-make.sh support such custom target directories.
the idea of the script
is to prune all possible caches
that may cause problems when updating core.
it is run usually before a release
and to make sure a core is rebuild from scratch.
* update deltachat-core-rust to 'ref: More logging for ongoing and get_backup (#4289)' of branch 'stable-1.112'
* update changelog for 1.36.2
* bump version to 1.36.2
* add some feedback at end of upload-release script, similar to upload-beta
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
adbenitez