Thank you for your interest in the Windows CE work we are doing. I have gotten alot of feedback from my posting to the newsgroup regarding help on building a great browser for Windows CE. I thought I would take this moment to tell you the progress I have made and point out a few areas where I think you can help.
So, as of today, if you had a bit of time, you could build yourself a browser that is based on the Mozilla source code.
I have been able to port Minimo -- a smaller configuration of Mozilla over to Windows CE. The heavy lifting is mostly done with respect to porting. In fact, I have a IPAQ 6315 for a phone and it is the browser I use daily. There are a few loose ends such as XPTCall (http://www.mozilla.org/scriptable/xptcall-faq.html), build and config changes, https, and code reviews. Most of these items have people working on them. If you are interested in any, please let me know. The tracking bug for all things windows ce related is here: https://bugzilla.mozilla.org/show_bug.cgi?id=277211.
Currently, I am building against the Pocket PC 2003 SDK. We may want to adjust this at some point, but I thought it would be acceptable place to start. The binary is 3.8MB compressed not including security. To run the build I have, you need about 5mb of memory to display www.google.com (this is a pretty soft number. i need a better tool to determine exact rss usage -- if you have a tool in mind, please let me know)
I have written up some notes on how to go about building this stuff. I don't claim the notes are perfect, but they are a start. Ideally, the notes will turn into a "how to build for windows ce" webpage. If someone wants to help on this, please let me know. The notes are here: http://www.meer.net/~dougt/minimo_ce/NOTES.txt. The short term plan is to make building windows CE very simple -- as simply as building the Mozilla suite or Firefox.
The build works great on the device, but I am having some troubles getting things to compile for the emulator. Maybe someone can help here. I have toolwrappers (read my notes) for the emulator that I can send you. Just to note, it looks like libraries are building built but nothing is being exported.
On to the application itself...
If you try the build now you will find there is alot of windows integration work that needs to happen. For example, we need to be able to get our app into the start menu. I don't have a clue on how to do this yet and am hoping that one of you do.
Another thing you will notice is the UI for the application is terrible. I really need your input and windows ce coding skills here. If you want to take a look at the current code for the application, it is here: http://lxr.mozilla.org/seamonkey/source/embedding/minimo/wince.
You can download a sneak peak at this build here: http://www.meer.net/~dougt/minimo_ce/MinimoCE_0.002.zip. Keep in mind, it is basically the second build that I made that actually rendered a page successfully. When you check it out, remember I told you: Lots of work to do; Lots of work to do.
> I have written up some notes on how to go about building this stuff. I > don't claim the notes are perfect, but they are a start. Ideally, the > notes will turn into a "how to build for windows ce" webpage. If > someone wants to help on this, please let me know. The notes are here: > http://www.meer.net/~dougt/minimo_ce/NOTES.txt. The short term plan is > to make building windows CE very simple -- as simply as building the > Mozilla suite or Firefox.
...
Doug,
I tried to download the tools from the ftp server and folder as explained in your notes, but apparently it isn't there. Did I miss something?
Hi Dug, your work looks very fine, i'm testing Minimo with a Fujitsu-Siemens Pocket Loox 720 with VGA resolution and it works; Minimo seems to be very very fast with wi-fi connection (my PDA has 128MB of ram). I've written a message on an Italian Forum and i hope some people can help you with your project. You can find my post here: http://www.solopalmari.com/forum/viewtopic.php?t=994
> Thank you for your interest in the Windows CE work we are doing. I have > gotten alot of feedback from my posting to the newsgroup regarding help > on building a great browser for Windows CE. I thought I would take this > moment to tell you the progress I have made and point out a few areas > where I think you can help.
> So, as of today, if you had a bit of time, you could build yourself a > browser that is based on the Mozilla source code.
> I have been able to port Minimo -- a smaller configuration of Mozilla > over to Windows CE. The heavy lifting is mostly done with respect to > porting. In fact, I have a IPAQ 6315 for a phone and it is the browser > I use daily. There are a few loose ends such as XPTCall > (http://www.mozilla.org/scriptable/xptcall-faq.html), build and config > changes, https, and code reviews. Most of these items have people > working on them. If you are interested in any, please let me know. The > tracking bug for all things windows ce related is here: > https://bugzilla.mozilla.org/show_bug.cgi?id=277211.
> Currently, I am building against the Pocket PC 2003 SDK. We may want to > adjust this at some point, but I thought it would be acceptable place to > start. The binary is 3.8MB compressed not including security. To run > the build I have, you need about 5mb of memory to display www.google.com > (this is a pretty soft number. i need a better tool to determine exact > rss usage -- if you have a tool in mind, please let me know)
> I have written up some notes on how to go about building this stuff. I > don't claim the notes are perfect, but they are a start. Ideally, the > notes will turn into a "how to build for windows ce" webpage. If > someone wants to help on this, please let me know. The notes are here: > http://www.meer.net/~dougt/minimo_ce/NOTES.txt. The short term plan > is to make building windows CE very simple -- as simply as building the > Mozilla suite or Firefox.
> The build works great on the device, but I am having some troubles > getting things to compile for the emulator. Maybe someone can help > here. I have toolwrappers (read my notes) for the emulator that I can > send you. Just to note, it looks like libraries are building built but > nothing is being exported.
> On to the application itself...
> If you try the build now you will find there is alot of windows > integration work that needs to happen. For example, we need to be able > to get our app into the start menu. I don't have a clue on how to do > this yet and am hoping that one of you do.
> Another thing you will notice is the UI for the application is terrible. > I really need your input and windows ce coding skills here. If you > want to take a look at the current code for the application, it is > here: http://lxr.mozilla.org/seamonkey/source/embedding/minimo/wince.
> You can download a sneak peak at this build here: > http://www.meer.net/~dougt/minimo_ce/MinimoCE_0.002.zip. Keep in mind, > it is basically the second build that I made that actually rendered a > page successfully. When you check it out, remember I told you: Lots of > work to do; Lots of work to do.
This sounds great. A while back I had to write a wrapper around the Pocket Internet Explorer control to program around the various bugs that PIE had/still has at the time. How I wished for a open source browser then.
It's been some time since I pulled out eVC++ but I do remember the aggravation of the Start Menu problem. Obviously you'd think that adding a short cut to the \Windows\Start Menu directory would take care of things. Unfortuately from PPC2002 on the number of items in the menu is fixed. So for the iPAQ 63xx HP has beaten you it by adding in a bunch of irrelevant items - is the bluetooth manager still 3rd on the list? Previous to PPC2002 the start menu just scrolled...
So you could remove a few items from the Start Menu directory, be sure there are equivalents in the Programs sub-directory.
Here is the short-cut format if you didn't already know:
Where 60 is the character count, a '#' separator, then path to command and args
NB: It seems that you can't copy a shortcut file with File Explorer from a PC, or if you can be sure to tell me how. I ended up creating this file with PocketWord, saving it as text then changing the extension from txt to lnk with FileExplorer on the PC - what a hassle.
I'll download your code and see if there is anything I could add. I remember writing a little piece that resized the app when the SIP (the virtual keyboard) popped up so I'll see if you are handling that.
> Doug Turner wrote: > ... >> I have written up some notes on how to go about building this stuff. I >> don't claim the notes are perfect, but they are a start. Ideally, the >> notes will turn into a "how to build for windows ce" webpage. If someone >> wants to help on this, please let me know. The notes are here: >> http://www.meer.net/~dougt/minimo_ce/NOTES.txt. The short term plan is >> to make building windows CE very simple -- as simply as building the >> Mozilla suite or Firefox. > ...
> Doug,
> I tried to download the tools from the ftp server and folder as explained > in your notes, but apparently it isn't there. Did I miss > something?
>>>I have written up some notes on how to go about building this stuff. I >>>don't claim the notes are perfect, but they are a start. Ideally, the >>>notes will turn into a "how to build for windows ce" webpage. If someone >>>wants to help on this, please let me know. The notes are here: >>>http://www.meer.net/~dougt/minimo_ce/NOTES.txt. The short term plan is >>>to make building windows CE very simple -- as simply as building the >>>Mozilla suite or Firefox.
>>...
>>Doug,
>>I tried to download the tools from the ftp server and folder as explained >>in your notes, but apparently it isn't there. Did I miss >>something?
I'll be trying to build this this when I get some time. My sincere thanks to you for getting this so far!
> For example, we need to be able to get our app into the start menu.
On PocketPCs, create a shortcut in the Windows\Start Menu directory and it'll appear at the high level (deleting Internet Explorer.lnk will free up space). If you just want it to appear in the "programs" submenu of the start menu, drop a link in Windows\Start Menu\Programs
On HPCs, create a shortcut in Windows\Programs.
It's normal for an installer to do this for you. CabWizard is what is provided to build cab files for PocketPC installation. I will quite happily look after creating the necessary inputs to build the CAB files if that helps, for both PocketPC and HPC. Cheers, nick. -- "Why don't you go and bother that nice Ms Rowling?" - Terry Pratchett http://www.chiark.com
>>>>I have written up some notes on how to go about building this stuff. I >>>>don't claim the notes are perfect, but they are a start. Ideally, the >>>>notes will turn into a "how to build for windows ce" webpage. If >>>>someone wants to help on this, please let me know. The notes are here: >>>>http://www.meer.net/~dougt/minimo_ce/NOTES.txt. The short term plan is >>>>to make building windows CE very simple -- as simply as building the >>>>Mozilla suite or Firefox.
>>>...
>>>Doug,
>>>I tried to download the tools from the ftp server and folder as explained >>>in your notes, but apparently it isn't there. Did I miss >>>something?
> Thank you for your interest in the Windows CE work we are doing. I have > gotten alot of feedback from my posting to the newsgroup regarding help on > building a great browser for Windows CE. I thought I would take this > moment to tell you the progress I have made and point out a few areas > where I think you can help.
> So, as of today, if you had a bit of time, you could build yourself a > browser that is based on the Mozilla source code.
> I have been able to port Minimo -- a smaller configuration of Mozilla over > to Windows CE. The heavy lifting is mostly done with respect to porting. > In fact, I have a IPAQ 6315 for a phone and it is the browser I use daily. > There are a few loose ends such as XPTCall > (http://www.mozilla.org/scriptable/xptcall-faq.html), build and config > changes, https, and code reviews. Most of these items have people working > on them. If you are interested in any, please let me know. The tracking > bug for all things windows ce related is here: > https://bugzilla.mozilla.org/show_bug.cgi?id=277211.
> Currently, I am building against the Pocket PC 2003 SDK. We may want to > adjust this at some point, but I thought it would be acceptable place to > start. The binary is 3.8MB compressed not including security. To run the > build I have, you need about 5mb of memory to display www.google.com (this > is a pretty soft number. i need a better tool to determine exact rss > usage -- if you have a tool in mind, please let me know)
> I have written up some notes on how to go about building this stuff. I > don't claim the notes are perfect, but they are a start. Ideally, the > notes will turn into a "how to build for windows ce" webpage. If someone > wants to help on this, please let me know. The notes are here: > http://www.meer.net/~dougt/minimo_ce/NOTES.txt. The short term plan is to > make building windows CE very simple -- as simply as building the Mozilla > suite or Firefox.
> The build works great on the device, but I am having some troubles getting > things to compile for the emulator. Maybe someone can help here. I have > toolwrappers (read my notes) for the emulator that I can send you. Just > to note, it looks like libraries are building built but nothing is being > exported.
> On to the application itself...
> If you try the build now you will find there is alot of windows > integration work that needs to happen. For example, we need to be able to > get our app into the start menu. I don't have a clue on how to do this > yet and am hoping that one of you do.
> Another thing you will notice is the UI for the application is terrible. I > really need your input and windows ce coding skills here. If you want to > take a look at the current code for the application, it is here: > http://lxr.mozilla.org/seamonkey/source/embedding/minimo/wince.
> You can download a sneak peak at this build here: > http://www.meer.net/~dougt/minimo_ce/MinimoCE_0.002.zip. Keep in mind, it > is basically the second build that I made that actually rendered a page > successfully. When you check it out, remember I told you: Lots of work to > do; Lots of work to do.
> Please let me know what you think and sign up for work if you can. we > can't make this happen without you.
> Regards, > Doug
Does anyone have any ideas on how to correct this compile problem? I got to the end of Doug's "Building WINCE" doc and am still getting this error. The output of the error is below.
C:\mozilla>make -f client.mk build Adding client.mk options from /cygdrive/c/mozilla/.mozconfig: MOZ_CO_PROJECT=suite MOZ_OBJDIR=$(TOPSRCDIR)/obj-arm WINCE=1 MINIMO=1 cd /cygdrive/c/mozilla/obj-arm /cygdrive/c/mozilla/configure Adding configure options from /cygdrive/c/mozilla/.mozconfig: --enable-application=suite --target=arm-wince --enable-win32-target=WINCE --enable-default-toolkit=windows --without-libIDL --disable-md --disable-xul --disable-profilesharing --disable-profilelocking --enable-single-profile --disable-extensions --disable-accessibility --disable-composer --enable-plaintext-editor-only --disable-mailnews --disable-ldap --disable-postscript --disable-mathml --disable-jsd --disable-jsloader --disable-installer --disable-xpinstall --disable-xpfe-components --disable-necko-disk-cache --enable-necko-small-buffers --disable-dtd-debug --disable-logging --disable-tests --enable-crypto --enable-necko-protocols=http,file,res,jar --enable-image-decoders=png,gif,jpeg --enable-strip --disable-debug loading cache ./config.cache checking host system type... i686-pc-cygwin checking target system type... arm-unknown-wince checking build system type... i686-pc-cygwin cross compiling from i686-pc-cygwin to arm-unknown-wince checking for host c compiler... checking for gcc... gcc gcc checking for host c++ compiler... checking for c++... c++ c++ checking for ranlib... no checking for ar... no checking whether the host c compiler (gcc ) works... yes checking whether the host c++ compiler (c++ ) works... yes checking for arm-wince-gcc... arm-wince-gcc checking for gcc... arm-wince-gcc checking whether the C compiler (arm-wince-gcc ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. *** Fix above errors and then restart with "make -f client.mk build" make: *** [/cygdrive/c/mozilla/obj-arm/Makefile] Error 1
> Does anyone have any ideas on how to correct this compile problem? I got to > the end of Doug's "Building WINCE" doc and am still getting this error. The > output of the error is below.
> C:\mozilla>make -f client.mk build > Adding client.mk options from /cygdrive/c/mozilla/.mozconfig: > MOZ_CO_PROJECT=suite > MOZ_OBJDIR=$(TOPSRCDIR)/obj-arm > WINCE=1 > MINIMO=1 > cd /cygdrive/c/mozilla/obj-arm > /cygdrive/c/mozilla/configure > Adding configure options from /cygdrive/c/mozilla/.mozconfig: > --enable-application=suite > --target=arm-wince > --enable-win32-target=WINCE > --enable-default-toolkit=windows > --without-libIDL > --disable-md > --disable-xul > --disable-profilesharing > --disable-profilelocking > --enable-single-profile > --disable-extensions > --disable-accessibility > --disable-composer > --enable-plaintext-editor-only > --disable-mailnews > --disable-ldap > --disable-postscript > --disable-mathml > --disable-jsd > --disable-jsloader > --disable-installer > --disable-xpinstall > --disable-xpfe-components > --disable-necko-disk-cache > --enable-necko-small-buffers > --disable-dtd-debug > --disable-logging > --disable-tests > --enable-crypto > --enable-necko-protocols=http,file,res,jar > --enable-image-decoders=png,gif,jpeg > --enable-strip > --disable-debug > loading cache ./config.cache > checking host system type... i686-pc-cygwin > checking target system type... arm-unknown-wince > checking build system type... i686-pc-cygwin > cross compiling from i686-pc-cygwin to arm-unknown-wince > checking for host c compiler... checking for gcc... gcc > gcc > checking for host c++ compiler... checking for c++... c++ > c++ > checking for ranlib... no > checking for ar... no > checking whether the host c compiler (gcc ) works... yes > checking whether the host c++ compiler (c++ ) works... yes > checking for arm-wince-gcc... arm-wince-gcc > checking for gcc... arm-wince-gcc > checking whether the C compiler (arm-wince-gcc ) works... no > configure: error: installation or configuration problem: C compiler cannot > create executables. > *** Fix above errors and then restart with "make -f client.mk build" > make: *** [/cygdrive/c/mozilla/obj-arm/Makefile] Error 1
> Thanks,
> FReD
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. ---
> 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.
Its great to have Minimo ported! I develop on the HPC2000 (wince3.0) platform, other wince platforms and also Palm platform.
I'm testing the build on my machine and see if there is any tweaks required for the HPC2000 platform. I think the HPC handhelds can really do with an updated (Read: Better than PIE4.01) browser!! :)
> Thank you for your interest in the Windows CE work we are doing. I have > gotten alot of feedback from my posting to the newsgroup regarding help > on building a great browser for Windows CE. I thought I would take this > moment to tell you the progress I have made and point out a few areas > where I think you can help.
> So, as of today, if you had a bit of time, you could build yourself a > browser that is based on the Mozilla source code.
> I have been able to port Minimo -- a smaller configuration of Mozilla > over to Windows CE. The heavy lifting is mostly done with respect to > porting. In fact, I have a IPAQ 6315 for a phone and it is the browser > I use daily. There are a few loose ends such as XPTCall > (http://www.mozilla.org/scriptable/xptcall-faq.html), build and config > changes, https, and code reviews. Most of these items have people > working on them. If you are interested in any, please let me know. The > tracking bug for all things windows ce related is here: > https://bugzilla.mozilla.org/show_bug.cgi?id=277211.
> Currently, I am building against the Pocket PC 2003 SDK. We may want to > adjust this at some point, but I thought it would be acceptable place to > start. The binary is 3.8MB compressed not including security. To run > the build I have, you need about 5mb of memory to display www.google.com > (this is a pretty soft number. i need a better tool to determine exact > rss usage -- if you have a tool in mind, please let me know)
> I have written up some notes on how to go about building this stuff. I > don't claim the notes are perfect, but they are a start. Ideally, the > notes will turn into a "how to build for windows ce" webpage. If > someone wants to help on this, please let me know. The notes are here: > http://www.meer.net/~dougt/minimo_ce/NOTES.txt. The short term plan > is to make building windows CE very simple -- as simply as building the > Mozilla suite or Firefox.
> The build works great on the device, but I am having some troubles > getting things to compile for the emulator. Maybe someone can help > here. I have toolwrappers (read my notes) for the emulator that I can > send you. Just to note, it looks like libraries are building built but > nothing is being exported.
> On to the application itself...
> If you try the build now you will find there is alot of windows > integration work that needs to happen. For example, we need to be able > to get our app into the start menu. I don't have a clue on how to do > this yet and am hoping that one of you do.
> Another thing you will notice is the UI for the application is terrible. > I really need your input and windows ce coding skills here. If you > want to take a look at the current code for the application, it is > here: http://lxr.mozilla.org/seamonkey/source/embedding/minimo/wince.
> You can download a sneak peak at this build here: > http://www.meer.net/~dougt/minimo_ce/MinimoCE_0.002.zip. Keep in mind, > it is basically the second build that I made that actually rendered a > page successfully. When you check it out, remember I told you: Lots of > work to do; Lots of work to do.
Doug - I would not say I'm an expert in anything, but having built a few commercial Pocket PC applications myself, I believe I can help a little bit. Since I project manage 3 commercial Pocket PC apps plus design, develop, and manage a fourth (Pocket Informant - http://www.pocketinformant.com/) I barely have time for my own work. However, I have had such a huge desire to see Minimo for the Pocket PC that I'd like to be able to provide real and tangible help to this project. At the very least, I may be able to provide source code/samples/help on CE Win32 problems all the way from the Connection Manager to basic UI. At best, I'd like to actually contribute some coding.
I'll be honest and upfront and say that my biggest weak point is configuring projects to build in new IDEs with new compilers than they were setup for. But if you have things setup in eVC 4 (which is my guess), I may be able to at least take a looksie.
>> 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:
>> 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.
First- wonderful! Thanks! I've been looking forward to this day for quite a while. A couple quick issues:
1. On a VGA Pocket PC in real-VGA mode, the minimo window only takes up ~240x320, not the full screen. I imagine this would be a problem for folks even with QVGA PPCs, running it in landscape mode. 2. Minimo doesn't seem to quit. In the end, I had to reboot. 3. Can't wait til we have tabs- then I can think about retiring NetFront and ftxBrowser. :)
Doug Turner wrote: > If you try the build now you will find there is alot of windows > integration work that needs to happen. For example, we need to be able > to get our app into the start menu. I don't have a clue on how to do > this yet and am hoping that one of you do.
Putting an app in the Start Menu is easy. You just put a shortcut to the executable (or the executable itself, but that is poor practice) in the "\Windows\Start Menu" folder.
On Pocket PC/Windows Mobile, it is more appropriate to put the app not into the Start Menu, but into the "Programs" launcher. This is very similar- just place a shortcut or executable in "\Windows\Start Menu\Programs". On Pocket PC, the Start Menu is something the user maintains, picking which apps to put there out of what they have in the Programs launcher.
On vanilla WinCE, the practice is that you do put it in "\Windows\Start Menu", not the .\Programs folder. One thing to keep in mind.
There are programmatic ways to do this, naturally. One is by just creating the shortcut file, which is pretty easy. There is also a Windows API call IIRC that will do this, but this piece I do not have.
> First- wonderful! Thanks! I've been looking forward to this day for > quite a while. A couple quick issues:
> 1. On a VGA Pocket PC in real-VGA mode, the minimo window only takes up > ~240x320, not the full screen. I imagine this would be a problem for > folks even with QVGA PPCs, running it in landscape mode. > 2. Minimo doesn't seem to quit. In the end, I had to reboot. > 3. Can't wait til we have tabs- then I can think about retiring > NetFront and ftxBrowser. :)
> Doug Turner wrote:
>> If you try the build now you will find there is alot of windows >> integration work that needs to happen. For example, we need to be > able >> to get our app into the start menu. I don't have a clue on how to do
>> this yet and am hoping that one of you do.
> Putting an app in the Start Menu is easy. You just put a shortcut to > the executable (or the executable itself, but that is poor practice) in > the "\Windows\Start Menu" folder.
> On Pocket PC/Windows Mobile, it is more appropriate to put the app not > into the Start Menu, but into the "Programs" launcher. This is very > similar- just place a shortcut or executable in "\Windows\Start > Menu\Programs". On Pocket PC, the Start Menu is something the user > maintains, picking which apps to put there out of what they have in the > Programs launcher.
> On vanilla WinCE, the practice is that you do put it in "\Windows\Start > Menu", not the .\Programs folder. One thing to keep in mind.
> There are programmatic ways to do this, naturally. One is by just > creating the shortcut file, which is pretty easy. There is also a > Windows API call IIRC that will do this, but this piece I do not have.
areic...@gmail.com wrote: > First- wonderful! Thanks! I've been looking forward to this day for > quite a while. A couple quick issues:
> 1. On a VGA Pocket PC in real-VGA mode, the minimo window only takes up > ~240x320, not the full screen. I imagine this would be a problem for > folks even with QVGA PPCs, running it in landscape mode.
Yes, working on that right now as a matter of fact. I was initally just rendering into a fix size dialog. Hey -- it worked for the winembed test application.
I moved this over to a simple window which determines how big it should be at runtime.
> 2. Minimo doesn't seem to quit. In the end, I had to reboot.
Minimo isn't for quiters! :-)
Working on it...
> 3. Can't wait til we have tabs- then I can think about retiring > NetFront and ftxBrowser. :)
we have alot of other features we need to add to match them. If you have feature request or ideas, lets put them in bugzilla.mozilla.org so that we can compile a list of things to do.
> Could I a ask a "dumb" question : Does the Minimo's code for UNIX (cvs) is > the same for WinCE ?! Is Its GUI built using GTK !?
Great question.
Short answer: no.
Longer answer:
The souce code that comprises mozilla is more or less modular. FireFox, ThunderBird, the Mozilla Suite, SunBird, etc. all share alot of code. For example, from the network pipe all the way to presentation is exactly the same -- the difference between these apps is the UI and business logic of their specific application.
Minimo is a build configuration the shared code. We basically disable, reduce, or otherwise remove code that we deamed wasn't required or it was something that could be optimized for reduced footpring.
For the minimo application, we have two "front ends". These are native front ends -- linux uses GTK (and I have gotten a QT version going, but was sidetracked), and windows uses WinCE APIs.
In the long(er) term, I would like these two front ends to use XUL so that we can share UI resources, further extend the gecko platform, etc.
First, I'd like to say thank you to Minimo's devteam! A project like Minimo has been awaiting for long time.
Doug Turner napisał(a):
> [...] > For the minimo application, we have two "front ends". These are native > front ends -- linux uses GTK (and I have gotten a QT version going, but > was sidetracked), and windows uses WinCE APIs. > [...]
Simple question: If the source code of mozilla (and minimo) is modular and - as I understand - UI part is separated from the logic why not to use one of Microsoft's UI framework wrapping Win32 API and simplifying its usage? I have one such in mind. It is called Windows Template Library wich is published on Common Public License (http://sourceforge.net/projects/wtl/).
It provides ATL-based templatized framework wrapping Win32 API to build robust and small binaries. It is a very very thin layer just above the API. I use it programming applications for desktop Windows OSs and for Window CE based OSs like Pocket PC, Smartphone etc.
|
