Re: WCESHELLFE_MODULES_MSIMESP
- From: "Henrik Viklund" <henrik.viklund@xxxxxxxxx>
- Date: 27 Feb 2007 06:04:38 -0800
I think the general consensus among the knowledgable people on this
group is that the kind of tampering you've done with the build system
is "strongly discouraged".
You're effectively changing the behaviour of the build system on a
global basis, i.e. the changes you've made will be reflected in *all*
projects you build from now on, and you've also set yourself up for a
classic scenario where your changes may be overwriten by a monthly
update.
Finally, you've added a module that is not officially supported for
the locale you've set for your image, and in my experiance stuff is
usually "not supported" for a good reason.
Henrik Viklund
http://www.addlogic.se
On Feb 27, 1:54 pm, "Michael Reim"
<nospamr...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thank you Henrik for this information.
I found this in wceshellfe.bat:
REM $$$ Fix later, these don't build for other locales
set __SYSGEN_IMES=
if "%LOCALE%"=="0804" set __SYSGEN_IMES=1
if "%LOCALE%"=="1004" set __SYSGEN_IMES=1
if "%LOCALE%"=="0404" set __SYSGEN_IMES=1
if "%LOCALE%"=="0C04" set __SYSGEN_IMES=1
if "%LOCALE%"=="1404" set __SYSGEN_IMES=1
if "%LOCALE%"=="0411" set __SYSGEN_IMES=1
if "%LOCALE%"=="0412" set __SYSGEN_IMES=1
if not "%__SYSGEN_IMES%"=="1" goto noIMES
So the problem is not a missing component, but the wrong locale of my image
(US).
Since I want to support multiple languages, I don't want to set the default
locale to Chinese.
To work around my problem I modified wceshellfe.bat this way:
set __SYSGEN_IMES=1
goto MyTest
REM $$$ Fix later, these don't build for other locales
set __SYSGEN_IMES=
if "%LOCALE%"=="0804" set __SYSGEN_IMES=1
if "%LOCALE%"=="1004" set __SYSGEN_IMES=1
if "%LOCALE%"=="0404" set __SYSGEN_IMES=1
if "%LOCALE%"=="0C04" set __SYSGEN_IMES=1
if "%LOCALE%"=="1404" set __SYSGEN_IMES=1
if "%LOCALE%"=="0411" set __SYSGEN_IMES=1
if "%LOCALE%"=="0412" set __SYSGEN_IMES=1
:MyTest
if not "%__SYSGEN_IMES%"=="1" goto noIMES
Believe it or not, the chinese IME works now.
So what does this "Fix later, these don't build for other locales" mean?
And is there a better workaround than modifying wceshellfe.bat?
--
Michael Reim
reim AT helmut-fischer DOT de
"Henrik Viklund" <henrik.vikl...@xxxxxxxxx> schrieb im Newsbeitragnews:1172577196.094371.206670@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
If you can't find the info in the help, you can do it by working your
way backwards through the build system:
Under "..\PUBLIC\CEBASE\OAK\MISC\" there's a bunch of batch files that
the build system use to figure out what module control variables needs
to be set for various sysgen variables.
Now, looking at the first part of the module variable name, we find
that the prime suspect is "wceshellfe.bat". Now, to find what
conditions needs to be met for WCESHELLFE_MODULES_MSIMESP to be set
you should search for the last part of the variable -"msimesp" in
"wceshellfe.bat". Look at the conditionals surrounding the "set
WCESHELLFE_MODULES=%WCESHELLFE_MODULES% msimesp" and you should be
able to figure out what sysgen variables needs to be set.
Henrik Viklund
http://www.addlogic.se
On Feb 27, 11:27 am, "Michael Reim"
<nospamr...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hello all,
what component do I have to include in order to get
WCESHELLFE_MODULES_MSIMESP set?
And how can I find the answer on my own, without asking a newsgroup?
TIA
--
Michael Reim
reim AT helmut-fischer DOT de- Hide quoted text -
- Show quoted text -
.
- Follow-Ups:
- Re: WCESHELLFE_MODULES_MSIMESP
- From: Michael Reim
- Re: WCESHELLFE_MODULES_MSIMESP
- References:
- Re: WCESHELLFE_MODULES_MSIMESP
- From: Henrik Viklund
- Re: WCESHELLFE_MODULES_MSIMESP
- From: Michael Reim
- Re: WCESHELLFE_MODULES_MSIMESP
- Prev by Date: Re: WMMX registers mangled after a context switch
- Next by Date: Re: DHCP differences between VMini and NDIS
- Previous by thread: Re: WCESHELLFE_MODULES_MSIMESP
- Next by thread: Re: WCESHELLFE_MODULES_MSIMESP
- Index(es):
Relevant Pages
|
Loading