Re: Problem with FILESYS_FSROMRAM

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello Dean

thank You for the insights of the build process.

I already have this makefile in my cesysgen folder.
It simply includes
$(_WINCEROOT)\public\common\cesysgen\CeSysgenPlatform.mak.
CeSysgenPlatform.mak calls
cefilter $(_TARGETPLATROOT)\files\platform.reg
$(_TARGETPLATROOT)\cesysgen\files

If I look at $(_TARGETPLATROOT)\cesysgen\files\platform.reg I see that the
sysgen process
worked on that file as it should. But my drivers .reg file is included in
this file with
#include "$(_TARGETPLATROOT)\SRC\DRIVERS\sdcard\at91_sdmmc.reg".
So at this point I think my drivers .reg file didn't get sysgened.

Does this mean that "; @CESYSGEN IF" doesn't work in included .reg files at
all?
Or what should I do in order to get my drivers .reg file sysgened?


TIA
--
Michael Reim
reim AT helmut-fischer DOT de

"Dean Ramsier" <ramsiernospam@xxxxxxxxxx> schrieb im Newsbeitrag
news:evhQUlaJGHA.2036@xxxxxxxxxxxxxxxxxxxxxxx
>I based the comment on the fact that I didn't see an fsromram component in
>WINCE500\PUBLIC\CEBASE\OAK\MISC\winceos.bat. That file uses fsysram and
>fsysrom as the object store file system component names, and as far as I
>know it's those component names that are used in the filtering process. If
>it works in common.reg, I don't know how. I suspect it's really a bug and
>doesn't work at all. Note that the way it is used in common.reg, if the
>filtering works as I described, the error message would never occur.
>
> In order for the filtering process to run on your files you need to have a
> cesysgen folder containing a makefile in the root of your BSP directory,
> which you're probably missing. See one of the sample platforms for an
> implementation you can just copy.
>
> --
> Dean Ramsier - eMVP
> BSQUARE Corporation


.