How to package and generate static libraries for Mini Programs

The advantages of the Mini Program are as follows:

1. No need to install, open and use, and leave when you run out;

2. Save traffic, save installation time, and do not occupy the desktop;

4. For enterprises, the development cost of Mini Programs is lower and the development cycle is shorter;

Mini program is an application that can be used without **installation, it realizes the dream of "at your fingertips" of the application, and the user can open the application by scanning or searching. It also embodies the concept of "use up and go", and users don't have to worry about whether they install too many apps. Apps will be everywhere and ready to use, but without the need to install or uninstall.

For developers, the threshold for the development of Mini Programs is relatively low, and the difficulty is not as high as that of APP, which can meet the needs of simple basic applications, and is suitable for the conversion of offline stores of life services and low-frequency applications that are not just needed. The Mini Program can realize seven functions such as message notification, offline code scanning, and *** association. Among them, through *** association, users can realize the mutual jump between *** and Mini Programs.

First of all, when referencing a database file in your program, the path should not be written as an absolute path, but preferably as a path relative to the exe. For example, there is a database directory in all directories of the exe, which is dedicated to storing database files. In this way, when you do the installer, you only need to put the database in the corresponding database in the installed exe directory.

Of course, you can write the installer to decide whether to create or modify the configuration file to accommodate the new database location after the installation is complete.

In enterprise development, some core technologies or common frameworks, for security and stability reasons, do not want to be known by the outside world, so they will package the core ** into a static library, and only expose the header files to programmers for use (such as: third-party SDKs such as Umeng and maps).

The form in which static and dynamic libraries exist.

Static Library:a andframework

Dynamic Library:dylib andframework

The difference between a static library and a dynamic library.

Static libraries: When linked, static libraries are copied in their entirety to the executable file, and there are multiple redundant copies when used multiple times.

Dynamic library: It is not copied when linked, and the program is dynamically loaded into memory by the system when it is running, so that the program can be called, and the system only loads it once, and multiple programs share it to save memory.

Note: If a dynamic library is used in the project, it will be rejected by Apple.

Versions of static library files (4 types).

Real - debug version.

Genuine-release version.

Emulator - debug version.

Emulator-release version.

debug version.

1. Contains complete symbol information for easy debugging.

2. It will not optimize **.

release version.

1. It will not contain complete symbol information.

2. The execution of ** has been optimized.

3. The size will be slightly smaller than the debug version.

4. In terms of execution speed, the release version will be faster (but it does not mean that there will be a significant improvement).

Therefore, we generally package a release version in development and provide it to the outside world.

The hassle-free solution is done using cocoapod.

The easiest way to do this is to compile the release version and send it to the other party. Then when the other party clicks Run,It will mention what library is missing.,Argument and then you find bin in your qt installation directory.。。 Find the one that goes hand in hand.

dll file, just put it in your exe directory.

iOS is an operating system developed by Apple for the iPhone. It is mainly used for iPhone, iPod touch and iPad. Just like the Mac OS X operating system on which it is based, it is also based on Darwin.

Originally, the system was called iPhone OS, until the WWDC conference announced on June 7, 2010, the system architecture was divided into four levels: the core operating system layer, the core service layer, the ** layer, and the touchable layer. System operation takes up approximately 240MB of memory space.

Method 1:

Manually create the above folder and copy the static library in;

Method 2: Do the above action by compiling the configuration. The details are as follows:

1.Separate the compilation part of the dynamic library from the compilation part of the static library;

2.Create a lib folder (this must be the name) in the working directory, copy the third-party static library into it, and add a compilation configuration file as follows:

Android: How to introduce static libraries when compiling dynamic libraries.

This compilation configuration file is to generate intermediate files under the obj for use elsewhere.

The list of documents is as follows:

Android: How to introduce static libraries when compiling dynamic libraries.

3.Create a folder in the working directory and copy all the files related to the dynamic library. The name here is SRC, but of course there are other names as well. It reads as follows:

Android: How to introduce static libraries when compiling dynamic libraries.

Here, you just need to directly import the third-party library.

The list of documents is as follows:

Android: How to introduce static libraries when compiling dynamic libraries.

third is the header file of the static library, which is very simple, it is a function that adjusts the open functions in the static library in order, and the content is as follows:

Android: How to introduce static libraries when compiling dynamic libraries.

3.Add a compilation configuration file to the working directory, which is used to find all the subdirectories in the working directory to compile. The content is as follows:

Android: How to introduce static libraries when compiling dynamic libraries.

Okay, the work is done, let's go into the working directory mm -b and try it, you can compile it successfully.

Find the files with the suffixes dsp and dsw in the project directory, and double-click any of the two files with the mouse to open them.