CarlE
10-21-2003, 05:24 PM
I am porting an application from the Windows
desktop, to Pocket PC 2003, using eMbedded Visual C++ 4.0 (SP2) and
the Pocket PC 2003 SDK.
The application makes extensive use of C++ exception
handling (with the "try", "catch", and "throw" keywords).
When I build the ported application for the Pocket PC 2003
emulator (with the /GX compiler flag manually set so as to
enable unwind semantics), I get linker errors for unresolved
external symbols. The unresolved symbols are named
"`eh vector destructor iterator'" and "`eh vector constructor iterator'".
While searching the Internet for help on what was wrong, I found the
website of a company named "ENTREK". They had a page
(at http://www.entrek.com/rttipatch.htm)
that described a problem with using RTTI with the Pocket PC 2003 SDK.
They provided a "patch", a (free) file to download and link to named
"RTTIPatch.lib" (as well as an associated runtime "RTTIPatch.dll").
When I link against this file, my project then builds with no linker errors.
However, on the ENTREK site, I find the following:
>>>>>
Please note that this solution is only
for ARM/XScale-based Pocket PC 2003 devices.
It will not work on the Pocket PC 2003
emulator as this configuration of Pocket
PC 2003 lacks RTTI support.
>>>>>
And sure enough, the "RTTIPatch.lib" will not link to the emulator
configuration, due to a module machine type / target machine type mismatch.
I have the following questions:
1) Is it true that the Pocket PC 2003 SDK has a
problem with RTTI? Will a corrected version be
released anytime soon? Is there any other solution
that does not require linking the ENTREK file into
my application?
2) Is it true that the Pocket PC 2003 emulator lacks RTTI
support? Is a version forthcoming that will include
this support?
3) Is there anywhere in the Windows CE, or eMbedded Visual C++, or
Pocket PC 2003 SDK documetation where I can get accurate information on what C++ language features are and are not supported for different configurations?
desktop, to Pocket PC 2003, using eMbedded Visual C++ 4.0 (SP2) and
the Pocket PC 2003 SDK.
The application makes extensive use of C++ exception
handling (with the "try", "catch", and "throw" keywords).
When I build the ported application for the Pocket PC 2003
emulator (with the /GX compiler flag manually set so as to
enable unwind semantics), I get linker errors for unresolved
external symbols. The unresolved symbols are named
"`eh vector destructor iterator'" and "`eh vector constructor iterator'".
While searching the Internet for help on what was wrong, I found the
website of a company named "ENTREK". They had a page
(at http://www.entrek.com/rttipatch.htm)
that described a problem with using RTTI with the Pocket PC 2003 SDK.
They provided a "patch", a (free) file to download and link to named
"RTTIPatch.lib" (as well as an associated runtime "RTTIPatch.dll").
When I link against this file, my project then builds with no linker errors.
However, on the ENTREK site, I find the following:
>>>>>
Please note that this solution is only
for ARM/XScale-based Pocket PC 2003 devices.
It will not work on the Pocket PC 2003
emulator as this configuration of Pocket
PC 2003 lacks RTTI support.
>>>>>
And sure enough, the "RTTIPatch.lib" will not link to the emulator
configuration, due to a module machine type / target machine type mismatch.
I have the following questions:
1) Is it true that the Pocket PC 2003 SDK has a
problem with RTTI? Will a corrected version be
released anytime soon? Is there any other solution
that does not require linking the ENTREK file into
my application?
2) Is it true that the Pocket PC 2003 emulator lacks RTTI
support? Is a version forthcoming that will include
this support?
3) Is there anywhere in the Windows CE, or eMbedded Visual C++, or
Pocket PC 2003 SDK documetation where I can get accurate information on what C++ language features are and are not supported for different configurations?