Technical support > Linux
Debian: compiling maps and producing identical files
Mattn:
--- Quote from: apo on August 20, 2013, 11:40:14 am ---I have successfully compiled all maps for the first time. Of course the md5sums didn't match. ::)
Two requests:
Could you move http://ufoai.org/maps/2.5/MAPS into your git repository, at least for the final release version?
What do you think about adding the commit string to the file, so that it is clear against which version the maps were compiled?
--- End quote ---
that's python, i don't touch that ;) but patches are welcome. it's in contrib/map-get.
about adding that file to our repo... I don't see a reason yet to add it to the repo. What could one be? I don't think that this would help you to rebuild the maps to have the same checksum, no?
--- Quote ---For compiling the maps successfully only base/maps and base/textures are required, correct?
--- End quote ---
yes - base/ufos/entities.ufo is needed if you perform checks on the maps
--- Quote ---I use an intel based x86_64 linux system, your Makefile and commit: 480f1117edca8aea2dbc2073627c8af24ffe15fa from the 18th of August.
It took my core duo from 2009 10 hours to compile all maps. :)
--- End quote ---
that's long: http://ufoai.org/wiki/Mapping/Compile_time
apo:
--- Quote from: Mattn on August 20, 2013, 12:15:25 pm ---
about adding that file to our repo... I don't see a reason yet to add it to the repo. What could one be? I don't think that this would help you to rebuild the maps to have the same checksum, no?
--- End quote ---
My reasoning is that I would like to ship this file within the source package and integrate it into a check to verify that the outcome of the build process is identical to what you ship officially. I already have to create a source tarball from your git repository but I guess it doesn't really matter if I copy the file from git or perform some kind of wget command to retrieve the file. The only important thing is that this file is preserved somewhere, so that you can always compare the result despite the release of new revisions.
--- Quote from: Mattn on August 20, 2013, 12:15:25 pm ---that's long: http://ufoai.org/wiki/Mapping/Compile_time
--- End quote ---
Indeed. I will try if I can speed things up by using more threads and/or reducing your default nice value.
geever:
--- Quote from: Mattn on August 20, 2013, 12:15:25 pm ---that's python, i don't touch that ;) but patches are welcome. it's in contrib/map-get.
--- End quote ---
Hehe, I don't touch snakes either, but I can rewrite it in Perl if you would like and extend that... ;)
--- Quote from: Mattn on August 20, 2013, 12:15:25 pm ---that's long: http://ufoai.org/wiki/Mapping/Compile_time
--- End quote ---
I have the feeling for some time that our map compiling times multiplied recently... I wanted to do some tests.. but I don't like when my CPU goes up to 80C.... The stock cooler isn't cool enough for our maps. :)
-geever
Mattn:
--- Quote from: apo on August 20, 2013, 01:50:38 pm ---My reasoning is that I would like to ship this file within the source package and integrate it into a check to verify that the outcome of the build process is identical to what you ship officially. I already have to create a source tarball from your git repository but I guess it doesn't really matter if I copy the file from git or perform some kind of wget command to retrieve the file. The only important thing is that this file is preserved somewhere, so that you can always compare the result despite the release of new revisions.
--- End quote ---
i will change the make target to generate a md5sum list for all bsps that are put into the final zip file and will upload it to the release folder on sf.net. hope that works, too. i would rather not use the file that you linked, because that file is updated by a process running in the background. i don't exactly know when it's executed and stuff like that. so producing my own md5sums from the local files that i will put into the zip is safer imo.
O01eg:
--- Quote from: geever on August 15, 2013, 09:41:33 pm ---As far as I know mostly (if not only) floating-point weirdness can create different maps, so possibly they need to be compiled on the same CPU arch (but the compiled maps are not arch-dependent then.)
--- End quote ---
What if the server send maps to clients? Then the map on the server and clients will be same.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version