Solution of maven pom.xml dependency invalidation in IntelliJ 

https://blog.csdn.net/weixin_33400820/article/details/78855594?utm_medium=distribute.pc_relevant.none-task-blog-baidujs_title-0&spm=1001.2101.3001.4242

The Maven project was created in IntelliJ, and the dependencies of slf4j and log4j were added to pom.xml. However, when writing the program, we found that IntelliJ had no text assistance about slf4j and log4j at all. After checking, we found that although the dependencies in pom.xml had been downloaded to the local repository, they were not added to the extended libraries of the project path
as shown in the figure:

After Google and Baidu, they didn’t find the same type of problems, so they had to explore their own solutions. They found that there was a management window for Maven project in IntelliJ

View –> Tool Windows –> Maven Projects

If the dependencies folder is not found, there is no dependency in the project, but the content required for dependency has been added to the pom.xml file. Later, it is found that the content of Maven’s pom.xml file needs to be re imported, as shown in the figure:

Re import can find all the dependent packages in external libraries

To solve the problem that windows Remote Desktop Services cannot copy and paste: restart rdpclip.exe

After connecting to the remote server, even if you select the “clipboard” function in the “local resources” tab, you still can’t copy and paste. The solution is found through Baidu, because the rdpclip.exe on the remote server doesn’t work properly. The solution is to open the task manager on the remote server, find the rdpclip.exe process, and close it.

Then enter rdpclip.exe in the start menu search box, press enter, and it will run again.

Rk3399 boot into loader mode

Problem description

After burning the software on the main board of rk3399, it enters the loader mode again after restarting. You can view the following print records by viewing the log.

[ 11.254728] init: init first stage started!
[ 11.260572] init: Using Android DT directory /proc/device-tree/firmware/android/
[ 11.274173] init: [libfs_mgr]fs_mgr_read_fstab_default(): failed to find device default fstab
[ 11.463441] init: [libfs_mgr]by-name symlink not found for partition: 'recovery'
[ 11.471083] init: [libfs_mgr]avb_slot_verify failed, result: 2

reason

Looking at the above problem, it seems that Baidu pointed to AVB, a feature of Android. After comparison, we found that DTS was compiled incorrectly,
the DTS we used was rk3399-tve1030g-avb, but it was compiled into rk3399-tve1030g, which may be due to the lack of AVB function, leading to the failure of startup.

remarks

Rk3399 if you want to replace the kernel, you need to burn the boot partition. If you burn kenel and resource, it is invalid.

error: (-215:Assertion failed) !ssize.empty() in function ‘resize‘

error: (-215:Assertion failed) ! ssize.empty() in function ‘resize‘

1. Cause of the problem:

(1) The image path is correct, and does not contain Chinese, but the image path is not the whole path
(2) the image path is wrong, and no image is found
(3) the image path contains Chinese, and the function reports an error

2. Solution:
step by step check
(1) whether the file path is correct
(2) whether it is an absolute path
(3) whether the file name contains Chinese characters

If there is no way to solve, more detailed steps reference! Empty() in function ‘CV:: cascade classifier’
the errors are different, but the solutions are similar.

Automatic configuration of springboot and application.yml

We need to know that when springboot starts, it will be automatically configured, find meta-inf/spring. Factors , and load it into the IOC container

enter the file and find any class
click in<

see the @ enableconfigurationproperties ({serverproperties. Class}) annotation
click in serverproperties. Class

this means that the class is bound to the application.yml file
in which the value of prefix represents the

in the YML file All kinds of properties of this class are those of this class

the above is spring boot auto configuration and application. YML contact!!!

not found libc++.so

Problem: the installation of install depends on the APK with so library, so it can’t load so normally. Error: not found libc + +. So
for example: system. Loadlibrary (“inittest”);

analysis:

    on Android/prebuilds/tools/GCC SDK, run the following command:
    readelf – DW libinittest. So
    to view the dynamic dependency Library of libinittest. So. Since relying on libc + +. So Android n, Google has contracted the dependent permissions of so library. Only the application under system/APP system/priv app can be relied on. Some so libraries cannot be loaded by the installation application under data/APP
    the following/system/etc/public.libraries.txt is the white list of dynamically dependent libraries. Libc + +. So is not among them

    libandroid.so
libaaudio.so
libamidi.so
libbinder_ndk.so
libc.so
libcamera2ndk.so
libdl.so
libEGL.so
libGLESv1_CM.so
libGLESv2.so
libGLESv3.so
libicui18n.so
libicuuc.so
libjnigraphics.so
liblog.so
libmediandk.so
libm.so
libnativewindow.so
libneuralnetworks.so
libOpenMAXAL.so
libOpenSLES.so
libRS.so
libstdc++.so
libsync.so
libvulkan.so
libwebviewchromium_plat_support.so
libz.so

    Scheme 1:
    add libc + +. So to the white list

    Scheme 2:
    add the following configuration in the source code android.mk of libinittest.so:

    LOCAL_NDK_STL_VARIANT := c++_static
LOCAL_SDK_VERSION := 8

    Scheme 3:
    copy libc + +. So to the same level directory of libinittest.so in your app to generate APK.