Re: Mozilla Windows CE Development

"Lieven" <[email protected]> wrote in message 
news:[email protected]...
> Lieven wrote:
>> FReD wrote:
>>
>>> "Doug Turner" <[email protected]> wrote in message 
>>> news:[email protected]...
>>>
>> <snipped>
>>
>>
>> The same here, the config.log file says:
>> ----
>> ...
>> configure:1459: arm-wince-gcc -o conftest    conftest.c  1>&5
>> Microsoft (R) C/C++ Optimizing Compiler Version 12.20.9615 for ARM
>> Copyright (C) Microsoft Corp 1984-2002. All rights reserved.
>>
>> conftest.c
>> c:\devel\lgo\mozilla\test-arm-build\conftest.c(0) : fatal error C1083: 
>> Cannot open include file: 'mozce_shunt.h': No such file or directory
>> configure: failed program was:
>>
>> #line 1454 "configure"
>> #include "confdefs.h"
>>
>> main(){return(0);}
>> -----
>>
>> Which probably is normal, as that file is included in the build section
>> for wince.
>>
>> So I moved on, to get stuck a bit later in the process.
>>
>> I moved over to step 3 of the notes.txt file, created some folders ( 
>> config & nsprpub/config ) under my mozilla/test-arm-build folder, and 
>> copied the two files in there ( after some modification for
>> my machine ).
>>
>> In step 4 I cd into the mozilla/test-arm-build folder and do following
>> command:
>> make ../client.mk build
>>
>> Only to get some more errors, propably relative-path related:
>> ---
>> cvs checkout: No CVSROOT specified!  Please use the `-d' option
>> cvs [checkout aborted]: or set the CVSROOT environment variable.
>> mozilla/build/autoconf/mozconfig2client-mk: not found
>> ../client.mk:282: 
>> /cygdrive/c/devel/lgo/mozilla/test-arm-build/mozilla/.mozconfig.mk: No 
>> such file or directory
>> ../client.mk:283: 
>> /cygdrive/c/devel/lgo/mozilla/test-arm-build/mozilla/build/unix/modules.mk: 
>> No such file or directory
>> make: *** No rule to make target 
>> `/cygdrive/c/devel/lgo/mozilla/test-arm-build/m
>> ozilla/build/unix/modules.mk'.  Stop.
>> ---
>>
>> So, somebody any thoughts here?
>>
>> Lieven.
>>
>>
>>
>>
>
>
> Ok, I missed some obvious points, though not documented in the Notes
> file. These probably answer FReD's question too.
>
> First, the tool-wrappers have embedded in the source the paths they use to 
> find the shunt include files. So, before running buildtools.bat first
> change the paths SHUNT_LIB and SHUNT_INC in toolpaths.h to the values
> for your build pc.
>
> Second, the shunt is not only include files, but also libraries. Which
> are not yet built in the standard mozilla source package, so this has
> to be done manually. The easy way: open the file shunt.vcw in 
> SOURCE_DIR\mozilla\build\wince\shunt\build. It should open Embedded
> Visual C++ 4.0 . Select Win32 (WCE ARMV4) Release from the target list.
> Press F7 to build, et voila. You could also make the Debug release,
> but then you would have to change SHUNT_LIB in toolpaths.h again.
>
> These steps made the make command actually finishing the configuration. 
> ( I had to install the zip package from cygwin, but that's unrelated to 
> the build process ).
>
> Note: you actually have to start the build process first, then copy the
> two autoconf.mk files and then start the build again.
>
> Next problem:
> C:\devel\lgo\mozilla\test-arm-build>make
> ----
> rm -f -rf ./dist/sdk
> /usr/bin/make -C config export
> make[1]: Entering directory 
> `/cygdrive/c/devel/lgo/mozilla/test-arm-build/config'
> nsinstall.c
> /cygdrive/c/devel/lgo/mozilla/build/cygwin-wrapper cl -o 
> host_nsinstall.o -c -TC -nologo -DXP_WIN32 -DXP_WIN -DWIN32 -D_WIN32 -DNO_X11 
>  -O2   -I../dist/include -I../dist/include 
> I../dist/include/nspr -I../dist/include/nspr 
> /cygdrive/c/devel/lgo/mozilla/config/nsinstall.c
> nsinstall.c
> c:/devel\lgo\mozilla\config\nsinstall.c(46) : fatal error C1083: Cannot 
> open include file: 'dirent.h': No such file or directory
> make[1]: *** [host_nsinstall.o] Error 2
> make[1]: Leaving directory 
> `/cygdrive/c/devel/lgo/mozilla/test-arm-build/config'
>
> make: *** [default] Error 2
> ---------
>
> So I'm stuck again. This seems to be an ongoing saga, but I thought to 
> post it here so others might not make the same mistakes I do.
>
> regards,
>
> Lieven.
>
Lieven,

Have you gotten any further with your compile?

Thanks,

FReD