Main Page   Modules   Data Structures   File List   Data Fields   Globals   Related Pages  

Compilation Information

There are two main subdivisions of the Native codebase: code for PocketPC 2000 and code for PocketPC 2002. For both of these, there are binaries for the actual device and also for the emulator. Binaries are compiled for ARM processors.

Binary Files

The root of the binaries (as well as documentation and examples) is the C directory off the main installation directory. This contains directories for the examples, documentation and separate directories for PocketPC 2000 & 2002

For PocketPC 2002

For PocketPC 2002

Header Files

Header files for the native codebase are shared betwen the two PocketPC versions (and are also shared by the C Bindings version). The location of the header files is in include in the installation directory.

MQe_API.h
This is the "root" header file. If you include this you include all the functions that you could require. As the header files are shared, a definition is required to indicate which version of the codebase you are using.

   #define NATIVE                // or specify this as an option to the compiler
   #include <published/MQe_API.h>

You need to link against the following two libraries:

Generally, you should include both these files. Optimizing linkers should remove links to any functions and constants that you have not used.

The other MQe libraries are statically and dynamically linked with the main API library and will be included as required.

Threading

The Native codebase is designed to be re-entrant. The actual codebase does NOT use threads, but this does not preclude the use of multiple threads in the application. For example, an application thread could be created to repeatedly call mqeQueueManager_triggerTransmission().

If you wish to use multiple threads, there are no specific APIs that need to be called.

Whilst there is no requirement to have an exception block per thread, it is recommended that you do so. If you use one exception block shared across threads, there is the possibility that a thread that has failed will have its exception block overwritten by a thread that has succeeded.

Calling Convention

The calling convention for all the APIs has been explicitly set at __cdecl (although this does not preclude you from using a different default calling convention in your application).


Generated Thu Aug 11 23:27:18 2005 for Websphere MQ Everyplace for Multiplatforms C Programming Reference