User Ratings

★★★★★
★★★★
★★★
★★
0
0
1
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • Quick test, there are 2*2*2=8 relevant crosser versions, what you'll need for a Windows freeciv test depends on the download.gna.org/freeciv/packages/windows/testing/cazfi/crosser/ binary: Either 32 or 64 bit, either crosser 0.15 (for Freeciv 2.5, 2.6, or 3.0=trunk) or crosser 1.0.x (for Freeciv 2.6 or newer), either "full" (for Qt + freeciv-ruledit) or not (fails for Qt + freeciv-ruledit). The stuff without Qt takes about 90MB (crosser) + 30MB (freeciv). Otherwise it would be about 350MB (full dllstack incl. Qt) + the same 30MB (freeciv). After downloading one of the 8 crosser versions + a matching windows/testing binary you have to merge the two unpacked 7z archives; IOW, unpack them in the same test directory of your choice. Then run the supplied setup.bat once (on a command line). Then (still on a command line still in your chosen directory) run launch.bat, it temporarily creates an environment variable WINSTACK_ROOT (= your chosen directory), and adds the lib + bin subdirectories to your PATH. The lib + various other things are presumably pointless if all you want is to test one or more of the Freeciv binaries. Unsurprisingly freeciv-ruledit.exe won't start without the "full" stuff, but the gtk2/gtk3/sdl clients can be started (in the same still open command line window, otherwise repeat the launch.bat step).