家里有一台旧的联想T440笔记本，某天来了兴致安装了ubuntu 22.04，默认情况下指纹识别是无法使用的。
查看硬件属于 Elan 指纹识别设备，Ubuntu 自带的 Libfprint 已经提供了支持。
|
1 |
$ sudo apt install fprintd libpam-fprintd |
执行
|
1 |
$ sudo pam-auth-update |
将第一项，用空格勾选上，然后点“确定”。这样就授权指纹识别登录设备。
打开“设置---用户---指纹登录”，此时就可以打开了。点击“+”，录入第一个指纹吧
在平时的开发过程中，我们一般会自定义函数对变量是否为 null 进行检查，当检查函数返回成功的时候，对象一定不是 null 。
但是，这个自定义的函数，对于 Android Studio/IntelliJ IDEA 来说，是无法感知到的，导致 Android Studio/IntelliJ IDEA 会发出警告，没有对变量是否为 null 进行检查。
出现上述问题的例子如下：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
import java.util.Random; public class Test { // validator method static boolean hasText(String s) { return !(s == null || s.trim().isEmpty()); } public static void main(String[] args) { // s could come from anywhere and is null iff the data does not exist String s = (new Random().nextBoolean()) ? "valid" : null; if (hasText(s)) { // Potential null pointer access: The variable s may be null at this location System.out.println(s.length()); // ... do actual stuff ... } } } |
那么，有没有办法告知 Android Studio/IntelliJ IDEA ，我们已经对 null 进行过检查了呢？
网上搜索许久，尝试过 @CheckForNull / @EnsuresNonNullIf 注解，都不能解决问题。
最终发现使用 jetbrains 的 @Contract 注解能解决此问题。
上述的例子增加以下注解，明确告知编译器，如果参数是 null 函数一定返回 false，就可以阻止编译器发出警告了。
如下：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
import java.util.Random; import org.jetbrains.annotations.Contract; public class Test { // validator method @Contract("null -> false") static boolean hasText(String s) { return !(s == null || s.trim().isEmpty()); } public static void main(String[] args) { // s could come from anywhere and is null iff the data does not exist String s = (new Random().nextBoolean()) ? "valid" : null; if (hasText(s)) { // Potential null pointer access: The variable s may be null at this location System.out.println(s.length()); // ... do actual stuff ... } } } |
Intel E3-1230 v3 可以成功安装， AMD Ryzen 5900 CPU 在 Linux 系统上，需要配置 CPU 模仿 Intel CPU 的特性。并且 CPU 部分，不要启用 嵌套VT-x/AMD-V 。
在 macOS (实验使用的系统是 macOS Big Sur (11.7.1))系统上，执行如下命令，生成系统安装镜像
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
$ hdiutil create -o /tmp/HighSierra.cdr -size 7200m -layout SPUD -fs HFS+J $ hdiutil attach /tmp/HighSierra.cdr.dmg -noverify -mountpoint /Volumes/install_build $ sudo ~/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/install_build # 如果安装过程中卡住，查看安装日志，发现有多个安装提供者，无法确定使用哪一个，则必须执行如下命令，更详细的参考下面的解释 $ rm -rf /Volumes/Install\ macOS\ High\ Sierra/Install\ macOS\ High\ Sierra.app/Contents/MacOS $ hdiutil detach /Volumes/Install\ macOS\ High\ Sierra $ mv /tmp/HighSierra.cdr.dmg ~/Desktop/InstallSystem.dmg $ hdiutil convert ~/Desktop/InstallSystem.dmg -format UDTO -o ~/Desktop/HighSierra.iso |
flutter项目下执行 flutter run 提示信号灯超时时间已到
|
1 |
Failed to download https://chrome-infra-packages.appspot.com/dl/flutter/web/canvaskit_bundle/+/8MSYGWVWzrTJIoVL00ZquruZs-weuwLBy1kt1AawJiIC. Ensure you have network connectivity and then try again. SocketException: 信号灯超时时间已到 |
1、问题截图如下：
2、解决办法
终端输入
|
1 |
export FLUTTER_STORAGE_BASE_URL=https://storage.flutter-io.cn |
后回车
再次执行flutter run 启动项目即可成功。
注：
|
1 |
export FLUTTER_STORAGE_BASE_URL=https://storage.flutter-io.cn |
为设置使用国内镜像
Failed to download https://chrome-infra-packages.appspot.com/dl/flutter/web/canvaskit_bundle 超时 解决办法
在 ubuntu 22.04 通过 snap 安装了 Flutter SDK（当前是Flutter 3.3.4)，如果第三方的依赖了 CMake 3.10.2 更高的版本，会在编译的时候报错：
|
1 |
CMake 3.14 or higher is required. You are running version 3.10.2 |
这个报错的原因是由于 snap 安装的 Flutter SDK 构建了一个沙箱环境，在这个环境中的 CMake 是 3.10.2 版本，不管系统安装的是哪个版本的 CMake ，都是无效的。
要解决这个问题，或者等待 snap 的 Flutter SDK 更新版本，或者参照 Linux install Flutter 的说明，手工安装并配置 Flutter SDK 。
可以参考如下代码：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 |
$ sudo snap remove flutter $ sudo apt-get install curl $ sudo apt-get install clang $ sudo apt-get install git $ sudo apt-get install ninja-build $ sudo apt-get install pkg-config $ sudo apt install gettext $ sudo apt-get install libgtk-3-dev $ sudo apt install libstdc++-12-dev $ git clone https://github.com/flutter/flutter.git -b stable $ export PATH="$PATH:`pwd`/flutter/bin" $ cd `pwd`/flutter/bin $ ./flutter doctor |
公司上架了一款App，因为产品运营需要去修改App名称，在iOS应用市场提交新版本的时候可以改App名称。那么Android 各大市场如何更改APP名称呢？
目前上架的Android 应用市场有：360手机助手、腾讯应用宝、百度手机助手、阿里应用分发市场（豌豆荚）、安智市场、小米应用商店、华为应用市场、OPPO商店、魅族应用商店、vivo应用市场、搜狗手机助手等平台。
每家Android应用市场的规则都不同，小编整理了Android 各大市场更改APP名称的规则。
1、 百度 : 百度平台的最简单。直接更新app的版本即可(应用名称是系统从您提交的应用中解析的，如需修改请联系贵司技术修改apk包内信息。)
2、应用宝: 用上线后，开发者可通过工单系统提交应用名称修改需求 （入口1：如图点击“名称更改指引”即可直接跳转到修改应用名称的工单系统；入口2：管理中心-->点击需要修改名称的应用-->基础服务-->工单系统-->应用宝商务类-->移动应用名称修改-->填单提交）。修改应用名称需要提供软件著作权； 若暂无软著，可提供此款应用在其他外市场，改过名字后的前后台上线管理截图（其他证明文件均不接受）；
重要提示：根据平台规则，应用上线后，应用名称最多可支持修改2次，超过修改次数将不再受理，请谨慎确定好需要修改的应用名称后，再提交工单申请。
3、华为: 在开发者后台在该应用下点击上架或者升级，上传更名后的APK包，并在应用信息处更改应用名称，如应用分类涉及软著要求，请在“版本信息”的“应用版权证书或代理证书”处更新应用软著及免责函，提交应用审核。
4、360移动开放平台和百度移动开放平台是一样的，直接更新app的版本即可。
5、 vivo开放平台:
1)应用类APP需要修改名称： 直接在后台编辑更新，保证apk包内和在后台填写的名称一致即可；若名称相差较大，请在版权证明栏补充软著；游戏类APP（网游/单机）需要修改名称：需联系对接商务处理。
2)若需要更改应用包名，请联系贵司技术人员；更改之后再在平台创建应用提交新包名应用，旧包名应用需申请下架（登录平台--管理中心--点击您的应用--“下架申请”即可）。
6、 OPPO开放平台：也是上传后将自动解析包名。
7、魅族开放平台：也是上传后将自动解析包名。
8、小米市场: 应用名称修改需于应用包内及应用信息一同更改。应用包内名称更改还请贵司技术开发人员自行更改。（可以试一下直接上传后将自动解析包名。）
9、豌豆荚（阿里云应用分发平台）：也是上传后将自动解析包名。
数据保存在数据库中，根据表名称获取所有记录的列表，并在"ListView.builder"中显示的代码如下：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 |
class _EmployeesListScreenState extends State<EmployeesListScreen> { var db = new DatabaseHelper(); // CALLS FUTURE @override Widget build(BuildContext context) { return Scaffold( appBar: AppBar( title: const Text('List Of Employees'), ), body: FutureBuilder<List>( future: db.getAllRecords("tabEmployee"), initialData: const [], builder: (context, snapshot) { return snapshot.hasData ? ListView.builder( itemCount: snapshot.data?.length, itemBuilder: (_, int position) { final item = snapshot.data?.elementAt(position); //get your item data here ... return Card(child: ListTile( title: Text('Employee Name: ${item?.row[1]}'), ), ); }, ); }, ), ); } } |
参照 Flutter 2.8.1本地化/国际化应用程序名称 可以实现 Android/macOS/iOS/Web 的应用名称相关的国际化。Linux 参考 Flutter 3.0实现Linux本地化/国际化。
那么在 Windows 应用上如何相同的功能呢？
下面我们探讨一下一个比较简单的解决方案，就是直接修改RC文件，这个方案 适用于涉及到的语言类型不太多的情况。
Windows 代码编译，需要安装 Microsoft Visual Studio 2022 Community，但是不能直接使用 Microsoft Visual Studio 2022 Community 编辑 RC 文件，打开就会报错：
|
1 |
fatal error RC1015: cannot open include flie 'winres.h' |
具体的操作方法如下：
我们假定工程的名字为 LanauageTest
首先在项目根目录下，执行
|
1 |
$ flutter build windows |
生成 build 目录，然后使用 Microsoft Visual Studio 2022 Community 打开 build\windows\LanauageTest.sln 文件。
接着在资源视图中找到字符串资源（如果不存在则新建），选择默认的 StringTable ，然后右键选择 “插入副本”
虽然可以使用上面的操作来添加语言，但是只能作为参考，原因在于 Microsoft Visual Studio 2022 Community的 RC 文件编辑器在修改 LanauageTest.RC 文件的时候，把预定义的宏进行了展开，直接使用宏的实际值替代了宏本身，导致这些数据失去动态变化的能力。我们只能手工再编辑一次，恢复原来的宏才可以。
至于使用的话，可以通过 LoadString 加载定义的字符串资源，更详细参考 Using Resources。
参照 Flutter 2.8.1本地化/国际化应用程序名称 可以实现 Android/macOS/iOS/Web 的应用名称相关的国际化。但是在 Linux 应用上如何相同的功能，目前暂时没有一个统一的标准。
研究了许久，终于基本上算是搞定，解决方案如下：
使用 gettext 来实现国际化相关的功能。
首先配置，调整工程的目录如下：
project/
project/linux
project/linux/flutter
project/linux/flutter/CMakeLists.txt
project/linux/locale/en_US/app.po
project/linux/locale/zh_CN/app.mo
project/linux/locale/CMakeLists.txt
project/linux/CMakeLists.txt
project/linux/main.cc
project/linux/my_application.cc
project/linux/my_application.h
对应语言 i18n 相关配置文件的内容如下：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 |
# This file controls Flutter-level build steps. It should not be edited. cmake_minimum_required(VERSION 3.10) set(OUTPUT_NAME "app") set(LOCALE_DIR "${CMAKE_CURRENT_SOURCE_DIR}") set(LOCALE_BUILD_DIR "${CMAKE_BINARY_DIR}/locale") set(LOCALE_INSTALL_DIR "${CMAKE_INSTALL_PREFIX}/locale") # Setting up Internationalisation (i18n) find_package (Intl REQUIRED) if (Intl_FOUND) message(STATUS "Internationalization (i18n) found:") message(STATUS " INTL_INCLUDE_DIRS: ${Intl_INCLUDE_DIRS}") message(STATUS " INTL_LIBRARIES: ${Intl_LIBRARIES}") message(STATUS " Version: ${Intl_VERSION}") include_directories(${Intl_INCLUDE_DIRS}) link_directories(${Intl_LIBRARY_DIRS}) else () message(STATUS "Internationalization (i18n) Not found!") endif () find_package(Gettext REQUIRED) if (Gettext_FOUND) message(STATUS "Gettext found:") message(STATUS " Version: ${GETTEXT_VERSION_STRING}") else () message(STATUS "Gettext Not found!") endif () find_program(GETTEXT_XGETTEXT_EXECUTABLE xgettext) find_program(GETTEXT_MSGMERGE_EXECUTABLE msgmerge) find_program(GETTEXT_MSGFMT_EXECUTABLE msgfmt) if (GETTEXT_XGETTEXT_EXECUTABLE) message(DEBUG " xgettext: ${GETTEXT_XGETTEXT_EXECUTABLE}") file(GLOB_RECURSE PO_FILES RELATIVE ${CMAKE_SOURCE_DIR} ${CMAKE_SOURCE_DIR}/*.po) add_custom_target( pot-update COMMENT "pot-update: Done." DEPENDS ${LOCALE_DIR}/${OUTPUT_NAME}.pot ) add_custom_command( TARGET pot-update PRE_BUILD COMMAND ${GETTEXT_XGETTEXT_EXECUTABLE} --from-code=utf-8 --force-po --output=${LOCALE_BUILD_DIR}/${OUTPUT_NAME}.pot --keyword=_ --width=80 ${PO_FILES} WORKING_DIRECTORY ${CMAKE_SOURCE_DIR} COMMENT "pot-update: Pot file generated: ${LOCALE_BUILD_DIR}/${OUTPUT_NAME}.pot" ) else () message(STATUS "pot-update not created!") endif (GETTEXT_XGETTEXT_EXECUTABLE) if (GETTEXT_MSGMERGE_EXECUTABLE) message(DEBUG " msgmerge: ${GETTEXT_MSGMERGE_EXECUTABLE}") add_custom_target( pot-merge COMMENT "pot-merge: Done." DEPENDS ${LOCALE_BUILD_DIR}/${OUTPUT_NAME}.pot ) file(GLOB PO_FILES ${LOCALE_DIR}/*/${OUTPUT_NAME}.po) message(TRACE " PO_FILES: ${PO_FILES}") foreach(PO_FILE IN ITEMS ${PO_FILES}) message(DEBUG " Adding msgmerge for: ${PO_FILE}") add_custom_command( TARGET pot-merge PRE_BUILD COMMAND ${GETTEXT_MSGMERGE_EXECUTABLE} ${PO_FILE} ${LOCALE_BUILD_DIR}/${OUTPUT_NAME}.pot COMMENT "pot-merge: ${PO_FILE}" ) endforeach() else () message(STATUS "pot-merge not created!") endif (GETTEXT_MSGMERGE_EXECUTABLE) if (GETTEXT_MSGFMT_EXECUTABLE) message(DEBUG " msgmerge: ${GETTEXT_MSGFMT_EXECUTABLE}") file(GLOB PO_LANGS LIST_DIRECTORIES true ${LOCALE_DIR}/*) message(TRACE " PO_LANGS: ${PO_LANGS}") add_custom_target( po-compile COMMENT "po-compile: Done." ) foreach(PO_LANG IN ITEMS ${PO_LANGS}) if(IS_DIRECTORY ${PO_LANG}) message(STATUS " Adding msgfmt for: ${PO_LANG}") file(RELATIVE_PATH REL_PO_LANG "${LOCALE_DIR}" "${PO_LANG}") set(MO_BUILD_DIR "${LOCALE_BUILD_DIR}/${REL_PO_LANG}") file(MAKE_DIRECTORY "${MO_BUILD_DIR}") set(MO_NAME "${MO_BUILD_DIR}/${OUTPUT_NAME}.mo") add_custom_command( TARGET po-compile PRE_BUILD COMMAND ${GETTEXT_MSGFMT_EXECUTABLE} --output-file=${MO_NAME} ${OUTPUT_NAME}.po WORKING_DIRECTORY "${PO_LANG}" COMMENT "po-compile: ${PO_LANG}" ) install(FILES "${LOCALE_BUILD_DIR}/${REL_PO_LANG}/${OUTPUT_NAME}.mo" DESTINATION "${LOCALE_INSTALL_DIR}/${REL_PO_LANG}/LC_MESSAGES" COMPONENT Runtime) endif() endforeach() else () message(STATUS "pot-compile not created!") endif (GETTEXT_MSGFMT_EXECUTABLE) |
接下来，修改 Linux 工程的配置文件，增加对 本地化（i18n） 文件的引用，在合适的位置增加如下代码：
|
1 2 3 |
# locale build and install set(FLUTTER_LOCALE_DIR "${CMAKE_CURRENT_SOURCE_DIR}/locale") add_subdirectory(${FLUTTER_LOCALE_DIR}) |
完整的代码参考如下：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 |
# Project-level configuration. cmake_minimum_required(VERSION 3.10) project(runner LANGUAGES CXX) # The name of the executable created for the application. Change this to change # the on-disk name of your application. set(BINARY_NAME "abc") # The unique GTK application identifier for this application. See: # https://wiki.gnome.org/HowDoI/ChooseApplicationID set(APPLICATION_ID "xxx.xxx.xxx") # Explicitly opt in to modern CMake behaviors to avoid warnings with recent # versions of CMake. cmake_policy(SET CMP0063 NEW) # Load bundled libraries from the lib/ directory relative to the binary. set(CMAKE_INSTALL_RPATH "$ORIGIN/lib") # Root filesystem for cross-building. if(FLUTTER_TARGET_PLATFORM_SYSROOT) set(CMAKE_SYSROOT ${FLUTTER_TARGET_PLATFORM_SYSROOT}) set(CMAKE_FIND_ROOT_PATH ${CMAKE_SYSROOT}) set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER) set(CMAKE_FIND_ROOT_PATH_MODE_PACKAGE ONLY) set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY) set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY) endif() # Define build configuration options. if(NOT CMAKE_BUILD_TYPE AND NOT CMAKE_CONFIGURATION_TYPES) set(CMAKE_BUILD_TYPE "Debug" CACHE STRING "Flutter build mode" FORCE) set_property(CACHE CMAKE_BUILD_TYPE PROPERTY STRINGS "Debug" "Profile" "Release") endif() # Compilation settings that should be applied to most targets. # # Be cautious about adding new options here, as plugins use this function by # default. In most cases, you should add new options to specific targets instead # of modifying this function. function(APPLY_STANDARD_SETTINGS TARGET) target_compile_features(${TARGET} PUBLIC cxx_std_14) target_compile_options(${TARGET} PRIVATE -Wall -Werror) target_compile_options(${TARGET} PRIVATE "$<$<NOT:$<CONFIG:Debug>>:-O3>") target_compile_definitions(${TARGET} PRIVATE "$<$<NOT:$<CONFIG:Debug>>:NDEBUG>") endfunction() # Flutter library and tool build rules. set(FLUTTER_MANAGED_DIR "${CMAKE_CURRENT_SOURCE_DIR}/flutter") add_subdirectory(${FLUTTER_MANAGED_DIR}) # System-level dependencies. find_package(PkgConfig REQUIRED) pkg_check_modules(GTK REQUIRED IMPORTED_TARGET gtk+-3.0) add_definitions(-DAPPLICATION_ID="${APPLICATION_ID}") # Define the application target. To change its name, change BINARY_NAME above, # not the value here, or `flutter run` will no longer work. # # Any new source files that you add to the application should be added here. add_executable(${BINARY_NAME} "main.cc" "my_application.cc" "${FLUTTER_MANAGED_DIR}/generated_plugin_registrant.cc" ) # Apply the standard set of build settings. This can be removed for applications # that need different build settings. apply_standard_settings(${BINARY_NAME}) # Add dependency libraries. Add any application-specific dependencies here. target_link_libraries(${BINARY_NAME} PRIVATE flutter) target_link_libraries(${BINARY_NAME} PRIVATE PkgConfig::GTK) # Run the Flutter tool portions of the build. This must not be removed. add_dependencies(${BINARY_NAME} flutter_assemble) # Only the install-generated bundle's copy of the executable will launch # correctly, since the resources must in the right relative locations. To avoid # people trying to run the unbundled copy, put it in a subdirectory instead of # the default top-level location. set_target_properties(${BINARY_NAME} PROPERTIES RUNTIME_OUTPUT_DIRECTORY "${CMAKE_BINARY_DIR}/intermediates_do_not_run" ) # Generated plugin build rules, which manage building the plugins and adding # them to the application. include(flutter/generated_plugins.cmake) # Run the Flutter tool portions of the build. This must not be removed. add_dependencies(${BINARY_NAME} po-compile) # === Installation === # By default, "installing" just makes a relocatable bundle in the build # directory. set(BUILD_BUNDLE_DIR "${PROJECT_BINARY_DIR}/bundle") if(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT) set(CMAKE_INSTALL_PREFIX "${BUILD_BUNDLE_DIR}" CACHE PATH "..." FORCE) endif() # locale build and install set(FLUTTER_LOCALE_DIR "${CMAKE_CURRENT_SOURCE_DIR}/locale") add_subdirectory(${FLUTTER_LOCALE_DIR}) # Start with a clean build bundle directory every time. install(CODE " file(REMOVE_RECURSE \"${BUILD_BUNDLE_DIR}/\") " COMPONENT Runtime) set(INSTALL_BUNDLE_DATA_DIR "${CMAKE_INSTALL_PREFIX}/data") set(INSTALL_BUNDLE_LIB_DIR "${CMAKE_INSTALL_PREFIX}/lib") install(TARGETS ${BINARY_NAME} RUNTIME DESTINATION "${CMAKE_INSTALL_PREFIX}" COMPONENT Runtime) install(FILES "${FLUTTER_ICU_DATA_FILE}" DESTINATION "${INSTALL_BUNDLE_DATA_DIR}" COMPONENT Runtime) install(FILES "${FLUTTER_LIBRARY}" DESTINATION "${INSTALL_BUNDLE_LIB_DIR}" COMPONENT Runtime) foreach(bundled_library ${PLUGIN_BUNDLED_LIBRARIES}) install(FILES "${bundled_library}" DESTINATION "${INSTALL_BUNDLE_LIB_DIR}" COMPONENT Runtime) endforeach(bundled_library) # Fully re-copy the assets directory on each build to avoid having stale files # from a previous install. set(FLUTTER_ASSET_DIR_NAME "flutter_assets") install(CODE " file(REMOVE_RECURSE \"${INSTALL_BUNDLE_DATA_DIR}/${FLUTTER_ASSET_DIR_NAME}\") " COMPONENT Runtime) install(DIRECTORY "${PROJECT_BUILD_DIR}/${FLUTTER_ASSET_DIR_NAME}" DESTINATION "${INSTALL_BUNDLE_DATA_DIR}" COMPONENT Runtime) # Install the AOT library on non-Debug builds only. if(NOT CMAKE_BUILD_TYPE MATCHES "Debug") install(FILES "${AOT_LIBRARY}" DESTINATION "${INSTALL_BUNDLE_LIB_DIR}" COMPONENT Runtime) endif() |
使用多语言的代码如下：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 |
#include "my_application.h" #include <flutter_linux/flutter_linux.h> #ifdef GDK_WINDOWING_X11 #include <gdk/gdkx.h> #endif #include <sys/stat.h> #include <libgen.h> #include <locale.h> #include <libintl.h> #include "flutter/generated_plugin_registrant.h" #define LOCALE_DIR "/locale/" #define PACKAGE "app" #define _(String) gettext(String) struct _MyApplication { GtkApplication parent_instance; char **dart_entrypoint_arguments; }; G_DEFINE_TYPE(MyApplication, my_application, GTK_TYPE_APPLICATION) // 118n static void setup_app_locale() { struct stat sb; const char *proc_name = "/proc/self/exe"; if (lstat(proc_name, &sb) >= 0) { /* Add one to the link size, so that we can determine whether the buffer returned by readlink() was truncated. */ ssize_t bufsiz = sb.st_size + 1; /* Some magic symlinks under (for example) /proc and /sys report 'st_size' as zero. In that case, take PATH_MAX as a "good enough" estimate. */ if (0 == sb.st_size) { bufsiz = PATH_MAX; } ssize_t loc_dir_len = bufsiz + strlen(LOCALE_DIR) + 1; char *buf = (char *)malloc(loc_dir_len); if (NULL != buf) { ssize_t nbytes = readlink(proc_name, buf, bufsiz); if (nbytes >= 0) { /* If the return value was equal to the buffer size, then the the link target was larger than expected (perhaps because the target was changed between the call to lstat() and the call to readlink()). Warn the user that the returned target may have been truncated. */ if (nbytes == bufsiz) { g_message("(Returned buffer may have been truncated)\n"); } if (nbytes <= bufsiz) { buf[nbytes] = '\0'; } char *dir = dirname(buf); strncat(dir, LOCALE_DIR, strlen(LOCALE_DIR)); char *loc = setlocale(LC_ALL, NULL); g_message("current locale is:%s", loc); g_message("locale files dir is:%s", buf); setlocale(LC_ALL, ""); bindtextdomain(PACKAGE, buf); textdomain(PACKAGE); } free(buf); } } } // Implements GApplication::activate. static void my_application_activate(GApplication *application) { MyApplication *self = MY_APPLICATION(application); GtkWindow *window = GTK_WINDOW(gtk_application_window_new(GTK_APPLICATION(application))); // Use a header bar when running in GNOME as this is the common style used // by applications and is the setup most users will be using (e.g. Ubuntu // desktop). // If running on X and not using GNOME then just use a traditional title bar // in case the window manager does more exotic layout, e.g. tiling. // If running on Wayland assume the header bar will work (may need changing // if future cases occur). gboolean use_header_bar = TRUE; setup_app_locale(); #ifdef GDK_WINDOWING_X11 GdkScreen *screen = gtk_window_get_screen(window); if (GDK_IS_X11_SCREEN(screen)) { const gchar *wm_name = gdk_x11_screen_get_window_manager_name(screen); if (g_strcmp0(wm_name, "GNOME Shell") != 0) { use_header_bar = FALSE; } } #endif if (use_header_bar) { GtkHeaderBar *header_bar = GTK_HEADER_BAR(gtk_header_bar_new()); gtk_widget_show(GTK_WIDGET(header_bar)); gtk_header_bar_set_title(header_bar, _("app_name")); gtk_header_bar_set_show_close_button(header_bar, TRUE); gtk_window_set_titlebar(window, GTK_WIDGET(header_bar)); } else { gtk_window_set_title(window, _("app_name")); } gtk_window_set_default_size(window, 1280, 720); gtk_widget_show(GTK_WIDGET(window)); g_autoptr(FlDartProject) project = fl_dart_project_new(); fl_dart_project_set_dart_entrypoint_arguments(project, self->dart_entrypoint_arguments); FlView *view = fl_view_new(project); gtk_widget_show(GTK_WIDGET(view)); gtk_container_add(GTK_CONTAINER(window), GTK_WIDGET(view)); fl_register_plugins(FL_PLUGIN_REGISTRY(view)); gtk_widget_grab_focus(GTK_WIDGET(view)); } // Implements GApplication::local_command_line. static gboolean my_application_local_command_line(GApplication *application, gchar ***arguments, int *exit_status) { MyApplication *self = MY_APPLICATION(application); // Strip out the first argument as it is the binary name. self->dart_entrypoint_arguments = g_strdupv(*arguments + 1); g_autoptr(GError) error = nullptr; if (!g_application_register(application, nullptr, &error)) { g_warning("Failed to register: %s", error->message); *exit_status = 1; return TRUE; } g_application_activate(application); *exit_status = 0; return TRUE; } // Implements GObject::dispose. static void my_application_dispose(GObject *object) { MyApplication *self = MY_APPLICATION(object); g_clear_pointer(&self->dart_entrypoint_arguments, g_strfreev); G_OBJECT_CLASS(my_application_parent_class)->dispose(object); } static void my_application_class_init(MyApplicationClass *klass) { G_APPLICATION_CLASS(klass)->activate = my_application_activate; G_APPLICATION_CLASS(klass)->local_command_line = my_application_local_command_line; G_OBJECT_CLASS(klass)->dispose = my_application_dispose; } static void my_application_init(MyApplication *self) {} MyApplication *my_application_new() { return MY_APPLICATION(g_object_new(my_application_get_type(), "application-id", APPLICATION_ID, "flags", G_APPLICATION_NON_UNIQUE, nullptr)); } |
最近，入手了一部 NanoPi R5S ，官方是提供了 Anroid 12 的系统镜像，但是却没有给出相应的源代码（2023年10月12日，NanoPi 官方已经给出了Android 12的源代码，整个共享目录大约130GB左右，建议直接使用官方源代码进行编译）。尝试用官方提供的 Anroid 11 编译，结果编译出的系统镜像无法正常运行。
凑巧看到 研华科技 放出了 RSB-4810 开发板的 Anroid 12 编译指南，两者的配置差不多，试了一下，竟然可以正常运行！！
系统要求，内存不低于 32GB，否则编译过程中可能会由于内存不足，造成编译失败。
研华科技 官方文档是通过 docker 利用 ubuntu 18.04 进行编译的，如下：
1. 配置 docker 运行环境
|
1 2 3 4 5 6 7 8 9 10 11 12 |
$ sudo apt-get install docker $ sudo docker pull advrisc/u18.04-rk3399abv10:latest; # 注意，创建的目录必须是home的子目录，否则会在挂载的时候报错 # docker: Error response from daemon: error while creating mount source path '/data/r5s': mkdir /data: read-only file system. $ mkdir r5s $ sudo docker run --privileged -it --name android_S12 -v ~/r5s:/home/adv/BSP:rw advrisc/u18.04-rk3399abv10 /bin/bash $ sudo chown adv:adv -R BSP |
2. 下载源代码并进行编译
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
$ cd ~/BSP $ git clone https://github.com/ADVANTECH-Rockchip/repo.git $ mkdir rk3568_android_S12 $ cd rk3568_android_S12 $ git config --global user.name 'Your Name' $ git config --global user.email you@example.com $ git config --global http.postBuffer 52428800000 $ git config --global http.maxRequestBuffer 100M $ git config --global core.compression 0 $ ../repo/repo init -u https://dev.azure.com/AIM-Linux/RISC-RK3568-Android/_git/android-manifest -b rk3568-androidS12 -m RK3568_S12_AIV0001.xml $ ../repo/repo sync -c -f --no-clone-bundle -j16 |
3. 下载并解压缩编译工具（ prebuilts.tar.gz 密码: 1234）
|
1 2 3 4 5 6 7 |
Exit docker and copy the file to /home/your-name/myandroid $ cp prebuilts.tar.gz ~/r5s/rk3568_android_S12/android In container and Unzip file $ docker attach android_S12 $ tar zxvf ~/BSP/rk3568_android_S12/android/prebuilts.tar.gz |
4. 编译代码
|
1 2 3 |
$ source build/envsetup.sh;lunch rsb4810_s-userdebug; $./build.sh -AUCKu |
5. 核对编译后的文件
编译完成后的产物在 rockdev/Image-rsb4810_s/ 目录下，具体的文件列表如下：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
MiniLoaderAll.bin baseparameter.img boot-debug.img boot.img config.cfg dtbo.img misc.img parameter.txt pcba_small_misc.img pcba_whole_misc.img recovery.img resource.img super.img uboot.img update.img vbmeta.img |
5. 刷机
按照正常的流程刷机，整个流程走起来会比较繁琐，此处给相对简单的做法。