Motorola MC3090G Integration Guide - Page 88

Components, as the Active WCE Configuration. Select Win32 WCE ARMV4 Debug as the active

Page 88 highlights

4 - 4 MC3000 Integrator Guide 4. The sample applications provide examples of how to interface with the Motorola API functions. To build a sample application, open the Samples folder from the Windows Start menu. Open the folder for the desired sample and then open the project file. The project file has an extension of VCP. Microsoft Visual C++ v4.0 automatically launches. Select WinCE as the Active WCE Configuration. Select Win32 (WCE ARMV4) Debug as the active configuration. NOTE If both Microsoft Visual C++ v3.0 and Microsoft Visual C++ v4.0 are installed on the development computer, ensure Microsoft Visual C++ v4.0 launches. Components The sample applications provide examples of how to interface with the Motorola API functions. To build a sample application, open the Samples folder from the Windows Start menu. Open the folder for the desired sample and then open the project file. The project file has an extension of VCP. Microsoft Visual C++ v4.0 automatically launches. Select WinCE as the Active WCE Configuration. Select Win32 (WCE ARMV4) Debug as the active configuration. NOTE If both Microsoft Visual C++ v3.0 and Microsoft Visual C++ v4.0 are installed on the development computer, ensure Microsoft Visual C++ v4.0 launches. Table 4-2 lists the EMDK for C components. Table 4-2 EMDK for C Components and Locations Components Directory Location EMDK (API) Help file and Readme file \Program Files\Symbol Mobility Developer Kit vx.x for C\ Sample applications for quick-start development \Program Files\Symbol Mobility Developer Kit vx.x for C\Samples\evc\ Header files with API prototypes and structures* \Program Files\Windows CE Tools\wce420\WinCE\Include\armv4 Import Library files* \Program Files\Windows CE Tools\wce420\WinCE\Lib\armv4 Start Menu Readme Help Platform Integrator Samples Web Updates \Documents and Settings\All Users\Start Menu\Programs * The header files and library files are time and date stamped so they can be easily identified in the armv4 directories. The "date" is the date on which the software release was assembled and the time is the version of the release. For example, a time of 1:00 signifies version 1.0. Note: Directory locations may vary depending upon software versions.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236

4 - 4
MC3000 Integrator Guide
4.
The sample applications provide examples of how to interface with the Motorola API functions. To build a
sample application, open the Samples folder from the Windows
Start
menu. Open the folder for the desired
sample and then open the project file. The project file has an extension of VCP. Microsoft Visual C++ v4.0
automatically launches. Select
WinCE
as the Active WCE Configuration. Select Win32 (WCE ARMV4) Debug
as the active configuration.
Components
The sample applications provide examples of how to interface with the Motorola API functions. To build a sample
application, open the Samples folder from the Windows
Start
menu. Open the folder for the desired sample and
then open the project file. The project file has an extension of VCP. Microsoft Visual C++ v4.0 automatically
launches. Select
WinCE
as the Active WCE Configuration. Select Win32 (WCE ARMV4) Debug as the active
configuration.
Table 4-2
lists the EMDK for C components.
NOTE
If both Microsoft Visual C++ v3.0 and Microsoft Visual C++ v4.0 are installed on the development computer,
ensure Microsoft Visual C++ v4.0 launches.
NOTE
If both Microsoft Visual C++ v3.0 and Microsoft Visual C++ v4.0 are installed on the development computer,
ensure Microsoft Visual C++ v4.0 launches.
Table 4-2
EMDK for C Components and Locations
Components
Directory Location
EMDK (API) Help file and Readme file
\Program Files\Symbol Mobility Developer Kit v
x.x
for C\
Sample applications for quick-start
development
\Program Files\Symbol Mobility Developer Kit v
x.x
for C\Samples\evc\
Header files with API prototypes and
structures*
\Program Files\Windows CE Tools\wce420\WinCE\Include\armv4
Import Library files*
\Program Files\Windows CE Tools\wce420\WinCE\Lib\armv4
Start Menu
Readme
Help
Platform Integrator
Samples
Web Updates
\Documents and Settings\All Users\Start Menu\Programs
* The header files and library files are time and date stamped so they can be easily identified in the armv4
directories. The “date” is the date on which the software release was assembled and the time is the version of the
release. For example, a time of 1:00 signifies version 1.0.
Note: Directory locations may vary depending upon software versions.