To be honest, those instructions are probably quite a bit out of date now. But basically they involved installing GCC, figuring out what dependancies you'd actually need, installing those as well, then downloading the source and setting GCC to work on it.

It's all on GitHub these days, whereas when I last did it, I think it was using a different Version Control System.

On the plus side, it looks there's more to compile than just the base engine, this time.

To be honest, if you're running on anything more powerful than a netbook, the best solution probably involves using Wine.

Yeah, resident pretty much covered it. Although we moved to git instead of svn. The Linux build will likely need some errors fixed, since we don't have any designated Linux dev right now. Also there are two branches, at least in my github repository, one for in-progress dev (removes VC and plans to remove other dependencies and tidy the code somewhat), and another branch which is more or less the last thing with VC. (It's intended that VC will be removed in later versions, so this branch is more or less for fixing minor bugs, not for introducing new features)

Anyway, hopefully Linux dev goes okay, I haven't tried building Verge on Linux in a long while, but it was relatively painless last time.

EDIT: Fixed the URLs. I forgot to put tree/ in between ...github.org/Bananattack/ and the branch name in those addresses. Whoops!

http://verge-rpg.com/forums/verge-developers-forum/github-repositories

specifically:
https://github.com/Bananattack/verge3
https://github.com/speveril/VCLua
https://github.com/chuckrector/psdmap
https://github.com/chuckrector/maped2w
https://github.com/Bananattack/v3tiled

http://sourceforge.net/projects/vopenchr/

Yep, there's the About Verge contains all the useful repo information in one spot. Having said that though, the link could stand to be more visible, possibly a navigation item inside the header box, rather than a small link at the top of the page.

Never heard of this error before. Maybe make sure you're compiling Verge as a 32-bit executable?

Oh, right. I intentionally removed some of that functionality in my master branch, in the effort of removing VC, starting to phase out some VC-only libraries, like the dictionary class, which is entirely useless if you're using Lua, which has tables that do everything a dictionary or array could in VC, but better.

I didn't update the Makefile, because I was only testing these changes on Windows. There are probably some other dependencies like a_dict too that won't exist anymore. It should be trivial to remove them in the Makefile though.

If you're loading from my repository, and you want VC, you might want to be using the verge-3.2 branch, not the master. Unless you're fine with Lua only, and the chance of systems being removed/rewritten. The master branch is for developing new stuff that might eventually be for use in the "next" Verge release.

Fair enough. I just haven't had the time or incentives to update the makefile and build on Linux whenever I changed something, because there seemed to be very little demand for the Linux version.

Anyways. LuaBind is no longer a required dependency as of Verge 3.14. You can remove that as well, since Verge should not use it anywhere anymore. Basically, you just need to delete that -lluabind flag.

I guess it's been a few years since I've looked at the Linux build. I'm sorry about that, but the unfortunate truth is that the Makefile has not been actively maintained since I last built it about 2 or 3 years ago. And there have been a few releases since the last time that Linux build was touched. To fix the Linux build, you will probably need to go through changelogs for releases to find out what has changed.

I want to remedy these portability issue someday, but I have a 40 hour work week and a few other projects on the go.

If you feel like continuing with it, just ask me about what you need to know, however. I'd gladly accept changes that make the engine more portable.

Are you trying to run the binary by itself in an empty directory?

get this file:
http://verge-rpg.com/downloads/verge-3-1-2007-08-25-current-official-build

And unzip the contents into the same dir as your compiled binary.

Then run your binary.

Then tell me what happens!

Nope, no success. Probably because so much of the actual code is missing, lol. As an added bonus, I tried compiling the official build, again to no avail. It exits with

make: *** [../verge/Source/vc_core.o] Error 1

There are loads of warnings about deprecated conversions from strings and such, but the above error is the only one. It also happens after line 2252 of vc_core. Ironic that there are only 2254 lines.


Thanks for the correction. Perhaps I read proposed plans? Anyway, I will keep that that in mind, but I seem to be stuck a peculiar problem. All the hundreds of "undefined reference to __" problems seem to point to numerous timing functions.

Now, in xerxes.h already includes mac_system.h and g_script.cpp includes xerxes.h. So why is the compiler not realizing that these functions are defined and where to find them?

There may be a series of errors before all the timing function errors, but I am currently looking for a way to print the full compile log to see what the very first error is.

Thanks for the help and putting up with the noob :P

Edit: Found out how to write output to a file. Yay learning! Anyway, the first error seems to be

../verge/Source/a_common.o: In function `arandseed(unsigned int)':
a_common.cpp:(.text+0x5de): undefined reference to `timeGetTime()'

Once again, timeGetTime() appears to be fully defined in mac_system.cpp, which is included in xerxes.h, which is included a_commin.cpp.