The application uses the FreeBSD
The first stage in porting this program is to split the project into - the engine (GUIAppEng) and the application (GUIApp).
-The engine is written in C. At its core is the
The engine's project specification file (
- The output file is
- The first UID specified (
- Splitting the project into engine and UI means that the definition of
-
- For more information on DLLs, see
- The implementation of checksum (
- The user interface provides two main menu commands;
- This code fragment is taken from
-
-
- The file name and checksum are appended to an array, the contents of
- which may be viewed by selecting
- The application program includes several STDLIB header files, located
- in
- For information on Symbian applications, their project specification,
- and resource files, see
Removing writeable static
-- The PETRAN stage of building may report a message similar to the - following: -
-
- This warning, which is not reported when building for the Emulator,
- indicates that the DLL contains non-const static data. This is not allowed in
- ARM builds. If it is not obvious where the problem occurs, the associated
-
Include file clashes
-- In C++ source files which use STDLIB routines, the Symbian platform - C++ include files must be included before any of the STDLIB files. Failure to - do this will result in the following warning: -
-Mixing C and C++
-
- C and C++ have different views about the names of functions. If you
- refer to a C function from C++, ensure that its prototype is declared as
-
- See for example
Stack usage
-- Some programs produce the following error: -
-- unless the amount of stack they use is reduced. Symbian threads have - only 8k stack by default. -
-Resource cleanup
-
- Symbian platform has a requirement that all resources which were
- allocated by an application must be cleaned up by the time the program
- terminates. On the Emulator, in debug builds, failure to do this will cause a
- panic from the
- Because the data allocated in the thread-local storage for STDLIB's
- DLL (the
- The function to achieve this is
- For example, see the destructor for
The application uses the FreeBSD
The first stage in porting this program is to split the project into + the engine (GUIAppEng) and the application (GUIApp).
+The
+engine is written in C. At its core is the
The engine's project specification file (
The output file is
+ The first UID specified (
+ Splitting the project into engine and UI means that the definition of
+
For more information on DLLs, see
The implementation
+of checksum (
The user interface provides two main menu commands;
+ This code fragment is taken from
The file name and checksum are appended to an array, the contents
+of which may be viewed by selecting
The application
+program includes several STDLIB header files, located in
+ For information on Symbian applications, their project specification,
+ and resource files, see
Removing writeable static
The PETRAN stage +of building may report a message similar to the following:
+ This warning, which is not reported when building for the Emulator,
+ indicates that the DLL contains non-const static data. This is not allowed
+in ARM builds. If it is not obvious where the problem occurs, the associated
+
Include file clashes
+ In C++ source files which use STDLIB routines, the Symbian platform + C++ include files must be included before any of the STDLIB files. Failure +to do this will result in the following warning:
Mixing C and C++
C and C++ have different views
+about the names of functions. If you refer to a C function from C++, ensure
+that its prototype is declared as
See for example
Stack usage
+ Some programs produce the following error:
unless the amount of stack they use is reduced. Symbian threads +have only 8k stack by default.
Resource cleanup
The Symbian platform
+has a requirement that all resources which were allocated by an application
+must be cleaned up by the time the program terminates. On the Emulator,
+in debug builds, failure to do this will cause a panic from the
Because the data allocated in the thread-local storage
+for STDLIB's DLL (the
The function to achieve this is
For example, see the destructor for