Symbian DLL and Lib (dynamic library loading, dynamic library loading, static library loading)

Currently, the common platform written by client/server side requires plug-ins. Each plug-in is hosted in a dynamic library. In Symbian, dynamic calling is not very convenient, now let's summarize the loading methods of various types of libraries.

0, static Library:

1. Dynamic Library:
A. Static Loading:
B. Dynamic Loading:
Several Issues about dynamic library loading:
1. The emulator cannot be loaded for several possible reasons:
1.1 this dynamic library uses the C library (such as strlen/malloc, free etc .) in the dependent Lib, you manually added estlib. lib, compiled successfully, but cannot load normally, because carbide. during DLL compilation, vs2.0.1 automatically adds estlib. lib, if you add estlib again. lib will cause loading failure. It is a bit difficult to compile the environment. This problem also occurs when I use openc. The dynamic library must be compiled using codewarrior to load in the debugging environment. Otherwise, a-2 error will be returned when the dynamic library is compiled using carbide. vs2.01.
1.2 but if you use EXE, you must add estlib. lib to the project, because EXE does not include estlib. Lib by default.
1.3 capability: The operation capability of the dynamic library must match that of the EXE/DLL loaded. The matching principle is. The EXE/DLL capability must be a subset of the DLL capability loaded by it (?)

2. Loading failed on the real machine:
2. 1. You are not authorized to access the directory:
The Directory of the dynamic library may be installed, and the loader has no access permission, such as sys/bin/directory, no access permission, or private directory. The error code returned is generally-46. You can add allfiles to your application.
2.2. Directory loading error (the returned value is usually-1)
2.3.