I cannot build activex support on a certain CE6 sdk, caused by sal.h
that comes with the SDK. After days of hacking, I found the root of the
problem. The toolpath put SDK_INC before WCE_INC, which is wrong. I've
tested in VS2008SP1 projects, and VS always put WCE_INC before SDK_INC.
WCE_INC contains latest headers and updated C++ libraries, and some of them
are mandatory for altmfc. After I swapped them, the errors are gone, and
there are much less warnings.
I'm not sure if this is a real bug, or workaround for some other
issues.
diff --git a/build/wince/tools/toolspath.c b/build/wince/tools/toolspath.c
--- a/build/wince/tools/toolspath.c
+++ b/build/wince/tools/toolspath.c
@@ -194,17 +194,17 @@ DWORD run(char** args)
int i, j;
// Clear any link env variable that might get us tangled up
_putenv("LINK=");
_putenv("LIBPATH=");
_putenv("CC=");
- _putenv("INCLUDE=" SHUNT_INC ";" WM_SDK_INC ";" OGLES_SDK_INC ";"
WCE_INC);
+ _putenv("INCLUDE=" SHUNT_INC ";" WCE_INC ";" WM_SDK_INC ";"
OGLES_SDK_INC);
_putenv("LIB=" WCE_LIB ";" OGLES_SDK_LIB ";" WCE_CRT);
i = strlen(args[0]);
for (j=0; j<i; j++)
{
if (args[0][j] == '/')
args[0][j] = '\\';
}
--
city-anchoret
I _think_ this code is used for Windows Mobile builds of Fennec and
Windows CE builds of Firefox. It appears to be set up for the Mobile
build at present and this change may cause a problem there. Can anyone
confirm ?
-Nick Thomas
I also find that _WIN32_WCE (0x502) is hardcoded in the wrapper. For
my case, I need to change it to 0x600 (Windows CE 6.0).
I feel that the app is a little faster (maybe my feeling only). But a
lot of warnings are gone.