To develop programs in C, using the WebSphere MQ Everyplace Development
Kit, you need the following tools:
-
-
- Microsoft eMbedded Visual C++ (EVC) Version 3.0.
- This is included in Microsoft eMbedded Visual Tools 3.0, which is
available as a free download from the Microsoft web page:
http://msdn.microsoft.com/mobile/
You must use version 3.0 as version 4.0 does not support
PocketPC.
- An SDK for your chosen platform
- Microsoft eMbedded Visual Tools 3.0 includes an SDK for PocketPC
2000. You can also download an SDK for PocketPC 2002 from
Microsoft:
http://msdn.microsoft.com/mobile/
The two main subdivisions of the native C codebase are code for PocketPC
2000 and code for PocketPC 2002. For both, there are binary files for
the actual device and also for the emulator. Binary files are compiled
for the ARM processors.
The root of the binarie, as well as documentation and examples, is the C
directory, found in the main installation directory. This contains
directories for the examples, documentation, and separate directories for
PocketPC 2000 and 2002.
-
-
- PocketPC 2002
-
- DLL files in C\PocketPC 2002\arm\bin
- LIB files in C\PocketPC 2002\arm\lib
- PocketPC 2000
-
- DLL files in C\PocketPC 2000\arm\bin
- LIB files in C\PocketPC 2000\arm\lib
You can compile applications using the EVC Integrated Development
Environment (IDE), or optionally, from the command line. However, you
must consider the following:
- Set the appropriate "Active WCE Configuration", using the WCE
Configuration toolbar. To do this, under Target Operating
System select either PocketPC or PocketPC 2002. Also, under
Target Processor , select one of the following:
- Win32 (WCE x86em) Debug
- Win32 (WCE x86em) Release
- Win32 (WCE ARM) Debug
- Win32 (WCE ARM) Release
- Note:
- Some of the Target Processor or Target Operating System
options may not be available, depending on which SDKs you have
installed.
- Include the header files for the native C codebase. These are
shared between the two versions of PocketPC and by the C Bindings. The
header file location is in the installation directory under
include. If you include the root header file,
MQe_API.h, you include all the functions that you may require.
As header files are shared, you need to define which version of the codebase
you are using, as shown in the following example:
#define NATIVE
#define MQE_PLATFORM PLATFORM_WINCE
/*Alternatively, we recommened that you add this to the Preprocessor Definintions
in the Project Settings Dialog. Add the following to the start
of the list*/
NATIVE,MQE_PLATFORM=PLATFORM_WINCE
#include <published\MQe_API.h>
- Include an entry for the top level WebSphere MQ Everyplace include
directory in "Additional include directories". This varies according to
where you install the product.
- Insert the following .lib file names in the "Project Settings"
dialog, under Link -- > Input :
- HMQ_nativeAPI.lib
- HMQ_nativeCnst.lib
- Note:
- There are variations of these files for each supported release, for example
one for PocketPC 2000 ARM, one for PocketPC 2000 x86em, and so on. To
ensure that you use the correct verion, qualify the filename fully for each
target build.
We recommend that you develop applications using the PocketPC or
PocketPC2002 emulator as this typically provides a faster compilation and
debug environment. However, current emulators are API emulators,
meaning that they do not emulate ARM hardware. They emulate PocketPC
API calls, but the code is still x86, that is running in an x86 virtual
machine in the PocketPC 2002 emulator case. Therefore, we recommend
that you regularly test the application on the real target device, as many
problems such as byte-alignment only becomes apparent on the real
device.
- Note:
- WebSphere MQ Everyplace emulator binaries are provided only for development
purposes and are not suitable for deployment into a production
environment.
© IBM Corporation 2002. All Rights Reserved