Dev-C++ and cURL linker errors in Windows

[catcha]

Hi,

I've downloaded the bzflag-2.0.10 and I'm trying to compile the project according to instructions given in README.DEVC++ with little success. I downloaded the devel version of SDL for mingw (http://www.libsdl.org/release/SDL-devel ... w32.tar.gz) and CURL nossl version 7.17.1 for windows (http://curl.haxx.se/latest.cgi?curl=win32-devel). I copied the *.a and *.la files from the lib folder from both packages and pasted them to my Dev-CPP/lib folder. The same thing with *.h files and include directories. Finally, I copied the SDL.dll library from SDL package into windows folder (with libcurl-7.17.1 there was no library file at all). I'm using Dev-C++ version 4.9.9.2. And I do this in WinXP.

When I try to compile project bzflag.dev I get several linker errors such as the ones below. Could someone please help me get on with this? The readme file just tells to get the source or binary distribution but gives no further instructions. Where should I copy the .exe? How can I compile the dll file from libcurl sources in Dev-C++? Sorry for your time and such stupid questions. I really appreciate your help.

[Linker error] undefined reference to `__cpu_features_init'
[Linker error] undefined reference to `_imp__curl_easy_init'

[joevano]

I don't think compiling with DevC++ has been maintained. When compiling on windows we have switched to Visual C++ (the Express editionn works fine and is free).
See instructions here http://my.bzflag.org/bb/viewtopic.php?f=13&t=13675

[catcha]

I don't think compiling with DevC++ has been maintained. When compiling on windows we have switched to Visual C++ (the Express editionn works fine and is free).
See instructions here http://my.bzflag.org/bb/viewtopic.php?f=13&t=13675

Ok, thanks, I'll try that. If DevC++ is no longer maintained, the current instructions are misleading and should perhaps be changed. I also thought the problems I had were trivial (a missing library etc) and could be solved easily, but maybe not so.

[blast]

They likely already have been changed in our development code (which is not compatible with 2.0.x)