Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
compiling errors
07-03-2007, 10:24 AM,
compiling errors
I'm triing to compile Vdrift with Visual Studio, but i'm having a lot of problems with the libraries.
When i try to compile the source i have a lot of errors, for example:

I have installed the openAL libraries but there's the following error:
fatal error C1083: Cannot open include file: 'AL/al.h': No such file or directory

In the file "settings.cpp" the compiler give to me the follwing errors:
...\controls.h(77) : see declaration of 'CONTROL::controltype'
...\controls.h(115) : error C2440: '=' : cannot convert from '_MEDIA_TYPE' to 'ControllerEnum' Conversion to enumeration type requires an explicit cast (static_cast, C-style cast or function-style cast)
...\settings.cpp(926) : error C3861: 'sort': identifier not found
...\settings.cpp(928) : error C3861: 'unique': identifier not found
...\settings.cpp(944) : error C3861: 'mkdir': identifier not found

in the file net.cpp:
...\gamestate.h(125) : error C2039: 'sort' : is not a member of 'std'
...\gamestate.h(125) : error C3861: 'sort': identifier not found


Is a problem of libraries or compatibility with Visual Studio? Some one know what i have to do?

07-03-2007, 03:34 PM,
I don't mean to be rude or anything...but no one here has ever tried to compile VDrift with Visual Studio. Why don't you ask if you can use Dev-C++ for your project? I'm sure most reasonable professors wouldn't mind. I haven't used VS much before, at least not for C++, and from what I've heard it is not easy to debug. Keep in mind that Dev-C++ uses the GNU compiler and many GNU libraries which would make things a lot easier on you. Either way, you're not going to find any info here on Visual Studio. VDrift is a Free Software project and we use only Free Software to create it.

Also, you'll probably have to compile all the libraries with VS in order to use them with a project compiled with VS. If you really are serious about using VS, write sample code using the basics in each library and get that working first, then move to making it work with VDrift once you have a known working configuration for the libraries. Otherwise you'll never be able to tell if the problems are related to the libs or VDrift itself.

Finally, please stop creating new threads every time you have a question. One thread is enough. Just because a thread is old doesn't mean no one will respond. Ideally you could have one thread "Compiling VDrift with Visual Studio" and all the questions you've already asked, plus any future ones could go in there. I'm not going to bother consolidating your previous threads as there's not much point. I suggest you give this thread a more meaningful subject ("compiling errors" is very, very ambiguous) and just use this one.

Sorry if I sound like a jerk, please look at this from our viewpoint...
07-03-2007, 05:32 PM,
Ok, anyway thanks to the reply and sorry for the too many posts, i have never used forums before and i hope to use it better in the future.

Forum Jump:

Users browsing this thread: 1 Guest(s)