wince support

[clarified]

I was looking for wince images, and the latest that I could find were at
https://github.com/navit-gps/navit/releases
The latest there is 0.5.6 which is approaching 2 years old.

Are there compiled images for the latest versions for wince?

I have no expertise in wince, so would probably struggle to compile my own.

I have also posted about this on the forum.

[lains]

Hello, even if you may not feel comfortable with rebuilding the executable for WinCE, there are instructions on how to do so here.

[lains]

Or rather, on the new Wiki:
https://navit.readthedocs.io/en/v0.5.6/development/wince_development.html

[clarified]

On Fri, Dec 02, 2022 at 11:53:58PM -0800, lains wrote: Or rather, on the new Wiki: https://navit.readthedocs.io/en/v0.5.6/development/wince_development.html

That does look a bit dated, and I know almost nothing about winCE, so I suspect that is going to take time and effort to get the right tools installed and configured. Maybe I have to bite the bullet and do all of that. I don't think the average navit user with a winCE satnav is going to be able to do all of that just to update their system. But, yes I know it is all volunteer work, and someone has to be motivated to produce regular winCE iamges. I thought that used to be automated/scripted and so needed little effort. I see "The libraries below are not needed anymore since navit brings its own version of glib." I had the impression that winCE had serious limitations which mean that only a subset of C could be used in the sources. Maybe the builtin glib removes that problem? You will gather that I have very little idea of what is going on here. Thanks for the reply and work. ael/clarified

[mvglasow]

In theory, you could also grab the latest build from CI. In practice, you need to be sure to get an artifact from the master branch (not from some unstable feature branch – unless you know what you’re doing). As CircleCI deletes artifacts after 30 days, this will work only if master had any changes within the last 30 days.

Go to the main project page on Github, click the green check mark next to the latest commit, then click Details. Choose build_wince (or whatever platform you want prebuilt binaries for – you might need to log on to CircleCI for that), then go to the artifacts tab. If the job is no older than 30 days, you will find a list of all the artifacts the build has produced. Not sure what you need for WinCE – the ZIP file should contain all the files needed to run Navit, the CAB file should be the installable package (iirc – it’s been a while since I last used WinCE).

By the way, this also means we do test that every new commit still builds correctly on WinCE. In theory, you could also analyze the CI script and replicate the steps there to get a tried-and-true build recipe.

[lains]

If you have a Linux machine, you can also try to build inside the docker container that is used by circleci.

Below is a summary of the steps:

On your host:

docker pull navit/dockerfiles:wince
mkdir /tmp/wince_docker_app
(cd /tmp/wince_docker_app && git clone https://github.com/navit-gps/navit.git)

Then, launch the docker container:
docker run -it --rm --mount type=bind,source=/tmp/wince_docker_app,target=/app navit/dockerfiles:wince

When getting the docker container's prompt, the following step inside the container will compile navit for WinCE:

bash scripts/setup_wince.sh
bash scripts/build_wince.sh

If the build succeeds, you will get the the following binaries (on your host filesystem):

• /tmp/wince_docker_app/navit/wince/output/navit.zip
• /tmp/wince_docker_app/navit/wince/output/navit.exe

I have just compiled it on my machine from the code on master (at commit 51656c7), and I'm getting:

$ ls -al /tmp/wince_docker_app/navit/wince/output/navit.{exe,zip}
-rwxr-xr-x 1 root root 5636931 déc.   4 12:06 /tmp/wince_docker_app/navit/wince/output/navit.exe
-rw-r--r-- 1 root root 4585267 déc.   4 12:06 /tmp/wince_docker_app/navit/wince/output/navit.zip

[lains]

And if you don't want to go through the compilation by yourself, I have shared it on:
https://sendgb.com/mdODMtU70LG
MD5SUM: 9fe822ce54a808c3ed34cf481b16c3fd
SHA1SUM: 2f89c27523c2642ddb11fcf68c86bdc235b54930

The above link is valid for 5 days, but trusting exe binaries downloaded from cloud shares is not something I would do, honestly...

[clarified]

By the way, this means we do test that every new commit still builds correctly on WinCE.

That's good to know: I wasn't sure that was still the case.
It looks as if it may be a bit simpler to complie my own exe then.

Thanks again.

[clarified]

And if you don't want to go through the compilation by yourself, I have shared it on: https://sendgb.com/mdODMtU70LG MD5SUM: 9fe822ce54a808c3ed34cf481b16c3fd SHA1SUM: 2f89c27523c2642ddb11fcf68c86bdc235b54930

The above link is valid for 5 days, but trusting exe binaries downloaded from cloud shares is not something I would do, honestly...

Indeed. I have a copy, but I will see if I can compile my own local version first.
Short of time as ever, but hope to try the various options suggested as soon as possible.

Thanks to all for all this: very encouraging. I had feared that winCE was being orphaned.
I am not fan of winCE, butI have a pecfectly good winCE satnav which works well, if somewhat slowly, and there is no obvious open source replacement hardware. Given more time I had wondered about building something around a raspberry Pi, but that is going to be a bit clucky at best...

[clarified]

Grrr..., typos:

pecfectly -> perfectly
clucky -> clunky