Xenoveritas / abuse

Abuse SDL port originally from Crack-Dot-Com and released into the public domain
Other
128 stars 24 forks source link

Can't actually compile your Xenoveritas version #2

Open pasildan opened 6 years ago

pasildan commented 6 years ago

is there some better tutorial could be shared in order to compile this abuse version? Just set already SDL2 and SDL mixer files but then when building it on visual studio 15 2017 it sends a lot of errors and warning. Got a picture if ever helps.

https://imgur.com/Bb6zpdr

Would appreciate some help, thanks.

Xenoveritas commented 6 years ago

It works for me with VS 2017? The errors all appear to be saying an internal compiler error occurred. Unfortunately I don't know what's causing that and the error message and Microsoft's help page for error C1001 are vague enough to not give me any clues.

Note that there was an error in the build instructions: earlier versions required SDL1, but it's since been upgraded to use SDL2. I've corrected this in the documentation.

pasildan commented 6 years ago

Did you select any special feature in vs2017 installation? I could compile it 2 months ago but lost files unfortunately. Now tried to do again and got those messages.

pasildan commented 6 years ago

By the way I'm using lastest SDL2 + sdl mixer development folders with cmake, I'm using x86 files from them. I do have Windows 10 64 bits, When I managed to compile it first time I recieved another compiling errors about SDL port but they were related to x64 files from sdl2 + sdl mixer. I'm sorry if just coming too late I just read you stopped working in your version from 2014.

Xenoveritas commented 6 years ago

The only thing specific I can think of is making sure that "desktop development with C++" was installed. Beyond that it should be a standard Visual Studio 2017 install. I'm building on Windows 10 64-bit, although the project itself should be 32-bit, but the CMake-generated solution should do that.

The error being an "internal compiler error" you may need to reinstall Visual Studio? You could also try regenerating the solution files?

pasildan commented 6 years ago

just tried both of them unfortunately. Could be possible if you can share me the compiled files in some onedrive or dropbox link? I really appreciate your version from what I tested already.