On Sun, Mar 06, charlie@cferrero.net wrote:
Thorsten Kukuk (kukuk@suse.de) wrote:
Now I only need to find out why with random map builds the TYP file will not be used by the GARMIN device, while it is there :(
That's something I only saw until now after the merge with the index branch and with some of the index branch build tests yesterday.
Thorsten
I know it's obvious, and may not be the cause of your problem, but in my case *every* time the TYP has failed to be associated with the gmapsupp.img is because either I had failed to put the TYP where it should have been, or because it was open in another programme locked for access, or because it had the wrong family ID. Just a thought.
I ruled that already out. My script checks that this all is ok, and re-running the script again without modifying something creates a working map. The next time I see this I will diff the resulting map (by the way, do we store the date or anything else, which changes from build to build in the map?) and verify, that this is not again one of the caching problems of the 62s which bit me already more than once. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)