Openc problems affect installation, compilation, dynamic libraries, link sequence, runtime environment, and interface programs.

1. installation:
Download the openc plug-in from the Nokia website and then decompress it. Download its releasenotes.txt file to install and configure it. You can also download the demo file. When running, install the relevant plug-in sisfile on the running mobile phone as required. You can also add the running plug-in to the developed SIS release. Related methods can be packaged according to the release notes of the plug-in.
2. Compilation impact:
Make the following changes to the original C-compatible library in symbianc ++: A. Add % epocroot \ include \ stdapis to the header file directory, delete the original % epocroot \ include \ libc.
Delete estlib. Lib from the Linked Library and add libc. Lib. Libc. lib is usually placed at the beginning, and cannot be placed in eikctl. lib and other libraries, otherwise there will be a bunch of Link errors, and the obvious link error information is not seen from the error information, it took me a long time to compile a project to solve such a strange problem.
3. Impact on dynamic databases:
When openc is used in the dynamic library, it turns out that it cannot be dynamically loaded. First, in the debugging environment, if you use carbide. when using the vs tool, the dynamic library generated using openc cannot be loaded successfully on the simulator, and the error-2 is always returned. Check the relevant information. No clear description is provided for all Symbian data. This should be a problem with the carbide. vs tool. It can be compiled into the debug version by replacing it with codeworroir. This problem also occurs when you use the symbianc library, that is, carbide. vs, debugging version, cannot add estlib. lib. Otherwise, it cannot be loaded successfully. when compiling the release version, you must add estlib. lib. Otherwise, compilation fails ., Carbide. Vs, there's always a problem with Nokia. It's not easy to love you.
4. Impact on operation.
There is nothing to do with an EXE using openc, but if the dynamic library using openc is used, the program will not run properly. The GUI cannot be displayed normally. When I delete the plug-in stdioserver installed on the mobile phone as the runtime environment of openc. after the SIS, the GUI is normally displayed and cannot be understood. when reading the plug-in's release notes, the following message is displayed in the text: for debugging purposes only, and not to install it on the release mobile phone. Strange :)