Compiling Armagetron on Windows 10

[LittleSteps]

Hello, today I was trying to compile Armagetron Advanced version 0.4 on my Windows 10 desktop. Although the compiling seemed successful I received certain issues stating that I was unable to run any of the applications due to errors stating I did not have libxml2.dll, SDL2.dll, SDL2_image.dll and SDL2_mixer.dll. I am using code blocks with mingw and I tried to download the dll files and place them in the System32 folder but continued to had no luck.



Does this have anything to do with this bug?
"Bug #1317586: Winlibs too outdated to build"





On a side note is there any easy way to make the chat / output Armagetron puts out or the rubber meter bar stay in the middle screen if you had three screens (5760x1080) without needing to move everything inside the code? ( so it doesn't stretch retardedly ) like it does in this picture




ignore the god damn ugly ****** in my avatar picture fam LOL

[Z-Man]

Duplicate topic trashed, I suppose it was a silly copy/pasta spambot.

I tried to download the dll files and place them in the System32 folder

Why would you do that? Don't do that. It's not Windows 95 any more. Do you want to go to DLL Hell?
The correct procedure with DLLs like ours is to put them into the folder the executable is in. The "win32/makedist.bat" script should do that work for you after you build the workspace.

Does this have anything to do with this bug?
"Bug #1317586: Winlibs too outdated to build"

Possibly, but I just checked: The instructions here work swimmingly. I, err, just edited out the references to the trunk bzr modules, they very probably don't work. I replaced them with 0.4. Very important is the build batch file execution order, makedist.bat really needs to run AFTER the build. Also very important: only code::blocks version 13.12 and the mingw version coming with it are supported. That's an annoyance, but unfortunately unavoidable for that toolchain. The prebuild libraries in winlibs and the code::blocks project files together can only be compatible with one mingw version.
(Visual Studio is much more friendly there, each version comes with the SDKs and compilers of a whole bunch of previous versions and each project determines for itself which version is used. And there aren't so bloody many different versions of the SDK around.)

On a side note is there any easy way to make the chat / output Armagetron puts out or the rubber meter bar stay in the middle screen if you had three screens

Nope. Well, Origins had a configurable HUD. And, of course, on 0.4 you could build a custom cockpit.