I am currently experimenting with building ioq3 with clang/llvm. There are a couple of code style complaints (refering to certain outdated gnu specific styles).
Linking always issues a warning: LD build/release-freebsd-amd64/missionpack/uiamd64.so /usr/local/bin/ld: error in /usr/lib/crtendS.o(.eh_frame); no .eh_frame_hdr table will be created. But the resulting binaries work anyway, I don't think there is a lot of significance. What currently doesn't build are the modding tools: CGAME_Q3LCC code/cgame/cg_main.c build/release-freebsd-amd64/tools/q3lcc: fatal error in build/release-freebsd-amd64/tools/q3rcc gmake[2]: *** [build/release-freebsd-amd64/baseq3/cgame/cg_main.asm] Error 1 gmake[2]: Leaving directory `/usr/home/kamikaze/devel/ioq3/ioquake3-devel-1.36_SVN1783' gmake[1]: *** [targets] Error 2 gmake[1]: Leaving directory `/usr/home/kamikaze/devel/ioq3/ioquake3-devel-1.36_SVN1783' gmake: *** [release] Error 2 If I proceeded to fix the code style complaints and the q3lcc/q3rcc issue, would there be a reasonable chance of inclusion into the main branch? Game performance with clang built binaries is insignificantly better than with the gcc42 builds on my system (1%-2%). Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? _______________________________________________ ioquake3 mailing list ioquake3@lists.ioquake.org http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
