Generally speaking, static libraries cannot continue to be optimized. We can only find other alternative solutions to replace static libraries, or optimize in other aspects, such as resource optimization, image, audio and video compression, etc.;
Your question is not clear. If you are optimizing executable files, it is recommended to use Google's first generation heap. If you are optimizing static libraries, it is recommended to compile and optimize first to avoid compiling multiple architectures, and then find alternative solutions.
Static library files can be compressed first, such as into .gz format, and then write a filter class to decompress all .gz format data. Specifically, you can use this jar package directly: https://sourceforge.net /proje...
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Generally speaking, static libraries cannot continue to be optimized. We can only find other alternative solutions to replace static libraries, or optimize in other aspects, such as resource optimization, image, audio and video compression, etc.;
Your question is not clear. If you are optimizing executable files, it is recommended to use Google's first generation heap. If you are optimizing static libraries, it is recommended to compile and optimize first to avoid compiling multiple architectures, and then find alternative solutions.
Static library files can be compressed first, such as into .gz format, and then write a filter class to decompress all .gz format data. Specifically, you can use this jar package directly: https://sourceforge.net /proje...