Re: [warzone2100-dev] [Warzone 2100 Trac] #1066: Warzone doesn't support non-ASCII chars in PhysFS 2.0.0
On Monday, 28 February 2011 at 19:55, Safety0ff wrote: The precompiled version of physfs should be removed from the tarball (I've set things such that the Physfs 2 build overwrites the files from the tarball for the time being). As mentioned on IRC, we either need to add a tarball without physfs with different name, or just keep overwriting the old files. I don't care much about which solution is chosen, as long as nothing breaks. (Actually I'm thinking about using mingw-cross-env instead of our custom cross-build system, then a. other people can care about package versions etc, and b. it already includes qt (though not some other packages we use).) ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone 2100 Trac] #1066: Warzone doesn't support non-ASCII chars in PhysFS 2.0.0
Hey all, I'm pretty sure I've got this all figured out (tested it on Windows and it worked with unicode characters in addition to characters in the current code page). The implications are: CMake now required to cross compile (specifically for building Physfs 2). The precompiled version of physfs should be removed from the tarball (I've set things such that the Physfs 2 build overwrites the files from the tarball for the time being). Anyways, please review the two commits at the tip here: https://github.com/Safety0ff/warzone2100/commits/masterphysfs2 And voice your opinions concerns ASAP. I intend for these changes to be present in the next master alpha/release. Thanks. -Safety0ff ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone 2100 Trac] #1066: Warzone doesn't support non-ASCII chars in PhysFS 2.0.0
Hey all, I've post two patches to this ticket and It'd be great it if some people could test them. Requirements: You must have cmake installed (for physfs 2+ cross compilation) Instructions: Apply both patches and cross compile warzone. Put base.wz and mp.wz in a directory whose path contains non-ascii characters (see ticket for a better description of the issue). Try launching warzone (on windows) using the --datadir option. ( Zarel since you're one of the reporters in the original ticket, it'd be great if you could find a way to test this.) Let's get this 1+ year old ticket closed. :) -Safety0ff ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
