Compiling errors of doom, destruction, and doom.

[Gleeok]

[MENTION=38582]
Also, @DarkDragon asked me about using VS2015. I seem to recall that @Gleeok said that Microsloth changed something in VS2012 and later that made compiling in those newer versions impossible; and that it had something to do with how VS sees file paths. Is that right? I've never used a version newer than 2010, and the only full version that I have is 2008, so I'm not sure what broke.

I don't remember saying anything like that. AFAIK it might just work. ..?
I said I could put up 2010 files, but I didn't want to maintain two seperate projects, and if I switched to 2010 then support for 2008 would drop, so..

The project from shardstorm should work if the other one doesn't; nothing's really been changed. (Have I mentioned that I only work with the current code?)

[DarkDragon]

What is the "current code"? The github master branch?

[Gleeok]

Yeah, I don't even have a local checkout copy of the github 2.50.x branch. I don't think it's it's been up there very long.

The trunk should compile fine, unless you have 2015 and are trying to compile for 64-bit, then I'm not so sure. People have had trouble with this. Also there are no projects for the 3rd party libs, so from the perspective of having to do a complete setup and rebuild it's a bit of a clusterfuck - and not the good kind either.

[DarkDragon]

Dimentio: so after investigation, my conclusion is that the MSVC solution file in 2.50.x is out of date. Trying to copy files out of the master branch will NOT fix the problem. The easiest way forward is to compile the master branch rather than 2.50.x. If you want to fix 2.50.x, you will have to change the solution files so that each of the four projects correctly compiles the right subset of the source files (currently they are configured to use the "module" system of the master branch, which does not exist in the 2.50.x branch).

[Gleeok]

I thought Saffith said he changed the 2.50.x ones but I guess not. I'll see if I can get the old files out of the archive and put them up today. (If no one else beats me to it that is)

[side note] Even if you set up the build modules correctly for the 2.50.x branch it will not compile. This is because the master has had the benefit of some refactoring since 2.5.

[Saffith]

I did, but they may need updated.

I'm not sure there's any sense trying to use the master branch right now. It's gotten messy, and I think it's just going to be abandoned.

@Saffith : I presume that you are using the makefile, which is what I was originally suggesting that @Dimentio use. For Widows builds, are you using NMake, gcc (via CygWin), or something else? It would be helpful to know what you are using, as in any other situation, it should also work.

MinGW in MSYS.

[ZoriaRPG]

I did, but they may need updated.

I'm not sure there's any sense trying to use the master branch right now. It's gotten messy, and I think it's just going to be abandoned.


MinGW in MSYS.

@Gleeok
We needn't drop support for vs2008 just to add 2010 support. Those can coexist.
@Saffith
That would require merging all the bitmap changes with 2.50.x, and Gleeok did all of those. I know that he added bitmap creation, at the least, and reorganised some bitmap usage.

FWIW, 2.50.3 should be the master, and anything new and experimental should be a branch, merged into the master when it is known to work.

@Gleeok Are you sure that the ffscript symbol tables will compile? I thougjt that I saw an error in there. I have fixed versions of the tables though, for DrawBitmapEx args and such.

[Saffith]

Well, that's why we have git-merge.

[Gleeok]

I'm not sure there's any sense trying to use the master branch right now. It's gotten messy, and I think it's just going to be abandoned.

-_- ... what ...


What do you plan on leaving out amongst all the changes since 2.50?

[Saffith]

What's worth keeping? Let's throw out everything but that.