diff -r 80ef3a206772 -r 48780e181b38 Symbian3/SDK/Source/GUID-E0284006-9173-5BC5-A899-E0873CA1AE1F.dita --- a/Symbian3/SDK/Source/GUID-E0284006-9173-5BC5-A899-E0873CA1AE1F.dita Fri Jul 16 17:23:46 2010 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,12 +0,0 @@ - - - - - -Native EXEs and LIBs vs. OE EXEs and LIBs

The conventional way of defining the entry point for a Symbian platform executable is by including "E32Main " in the application source. Since Symbian OS v9.3, you can define the entry point for an executable by including "main " instead of "E32Main ". With this approach, Symbian developers may easily port their C/C++ code to Symbian platform with less changes to the original source.

Symbian OS v9.3 and later releases provide an Open Environment (OE) to develop EXEs with the "main " entry point. The OE executables and libraries are identified by their targettype, which can either be STDEXE, STDDLL or STDLIB. An OE EXE may choose to have a wide character entry point using the MMP keyword, wcharentrypoint.

Here is a list of important differences between native Symbian platform executables and OE executables:

The build system has been modified to support compilation of C++ source files with extensions “.cc ”, “.cxx ” and “.c++ ”. This change is applicable to both OE and native Symbian platform executables and libraries. That is, from Symbian OS v9.3 onwards a native Symbian platform or an OE executable/library can be built using C++ source files with extensions “.cc ”, “.cxx ” and “.c++ ”.

\ No newline at end of file