diff options
author | Volker Hilsheimer <[email protected]> | 2023-09-16 11:28:49 +0200 |
---|---|---|
committer | Volker Hilsheimer <[email protected]> | 2023-09-22 07:18:10 +0200 |
commit | 0022b05a9a222912ed91f658c058dff6955d2de4 (patch) | |
tree | 756117c07c0cec93fba0ef6e09a981ca61d78a4a /src/plugins/platforms/android/androidcontentfileengine.cpp | |
parent | dc126de22ea4d38736ae57c08c0b271f3c53fad9 (diff) |
JNI: rename our compile-time String type to CTString
The type lives in the QtJniTypes namespace, which is where types end up
that are declared through the Q_DECLARE_JNI_CLASS/TYPE macros. Having a
String type in that namespace prevents us from declaring the Java String
class as a QtJniTypes type, which is silly.
Perhaps this type becomes obsolete at some point with std::string being
a constexpr type in C++23, but until then we need it. It has no ABI, so
renaming it us safe.
Until submodules are ported, leave a compatibility alias String type,
which also prevents us from declaring a String JNI class in tests until
the alias is removed in a later commit.
Change-Id: I489a40a9b9e94e6495cf54548238438e9220d5c1
Reviewed-by: Zoltan Gera <[email protected]>
Reviewed-by: Tinja Paavoseppä <[email protected]>
Reviewed-by: Petri Virkkunen <[email protected]>
Diffstat (limited to 'src/plugins/platforms/android/androidcontentfileengine.cpp')
0 files changed, 0 insertions, 0 deletions