Dear WinCE team,
This is with regard to our discussion today morning, below is the description of the issues we are facing. We need your help to identify the root cause and solution to fix these issues.
Description:
Hardware Platform: AM3517.
BSP: AM3517.
Operating System: Windows Embedded Compact 7.
Steps Performed:
1. We have build the BSP in Platform Builder to get the OS Image (NK.BIN)
2. We have then created SDK from Platform Builder by selecting all the catalog items. [This SDK is build so that we can develop applications that shall run on the hardware platform.]
3. The Platform Builder generated, MySDK.MSI file. [We have installed this SDK on our PC under folder “C:\Program Files\Windows CE Tools\SDKs\MySDK\]
4. Open VS2008 and select New Project. Project Type as Smart Device under Visual C++ and Template Type as MFC Smart Device Application.
5. In the wizard of New Project creation, select Platform SDK that needs to be added to the current project. [i.e. Select only MySDK]
6. In the wizard of New Project creation, in Application Type, select Dialog Based and Use of MFC as Shared DLL.
7. After classes are generated, create STL Map Object by including these lines in the .CPP file of the application.
#include <string>
#include <map>
using namespace std;
typedef map<string,string> MAP_LIST;
MAP_LIST m_MapList;
8. Check the sequence of fall down paths for Include and Library files for MySDK Platform. [VS2008 IDE -> Tools -> Option -> Projects and Solutions -> VC++ Directories]
a. First keep VC\CE path for Include and Library Files.
b. Second keep MySDK path for Include and Library Files.
9. Build the application. It will compile but will give linker errors.
10. Even if we change the fall down paths for Include and Library files for MySDK Platform in reverse order, i.e.,
a. First keep MySDK path for Include and Library Files.
b. Second keep VC\CE path for Include and Library Files.
11. Build the application. It will compile but will give linker errors and this time the count of linker errors are more.
12. If we perform the same operation by using MFC as Static linking, then it gets build successfully.
13. If we perform the same operation by selecting Template Type as Win32 Smart Device Project, then it also gets build successfully (fall down option similar to Step 8). But if we change the fall down option and make it as Step 10, then it fails to build.
If you or your team have any queries then please let me know. We can have a teleconference to discuss and resolve the above issues.
Regards,
Feroz
