Compiling the Client on Windows
Posted: Wed Jun 11, 2014 11:34 pm
I know Kevin Zheng has been working on making the Crossfire Client more easily compiled on various platforms. For the most part, things seem to work. I'm not getting any compiler errors or warnings, except the linker infallibly crashes (returning value 5), thus causing the compilation to fail. With a verbose Makefile generated by CMake 2.8.11.2, the last line printed is
This is 1283 characters long, making me wonder if I could be overflowing a buffer. I was also using Orwell Dev-C++ to compile it, and one place it output the message was truncated, which may also have something to do with this.
Does anyone have any ideas or confirmation of what the issue is here, or, more importantly, how to fix this issue?
Code: Select all
C:\PROGRA~2\Dev-Cpp\MinGW64\bin\gcc.exe -std=c99 -Wl,--whole-archive CMakeFiles\crossfire-client-gtk2.dir/objects.a -Wl,--no-whole-archive -o crossfire-client-gtk2.exe -Wl,--out-implib,libcrossfire-client-gtk2.dll.a -Wl,--major-image-version,0,--minor-image-version,0 ..\..\common\libcfclient.a C:\Users\TuxRules\Downloads\curl-7.34.0\bin\libcurl.dll C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libfreetype.dll.a C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libgtk-win32-2.0.dll.a C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libgdk-win32-2.0.dll.a C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libcairo.dll.a C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libpango-1.0.dll.a C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libgdk_pixbuf-2.0.dll.a C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libgio-2.0.dll.a C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libatk-1.0.dll.a C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libgobject-2.0.dll.a C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libglib-2.0.dll.a -lglu32 -lopengl32 C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libpng14.dll.a C:\Users\TuxRules\Downloads\gtk_2.24.10\lib\libz.dll.a C:\Windows\System32\wsock32.dll C:\Windows\System32\winmm.dll -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32
Does anyone have any ideas or confirmation of what the issue is here, or, more importantly, how to fix this issue?