I just looked the MSVC compile and it seems to be outdated, it still uses SVN stuff but the main dev part seems to be in a git repo -.-
I have some old stuff I would like to test in new main/branch =.=
And some interest stuff I could dig from my old harddisk -.-
Hmm how to compile current version?
-
AWarZoner
- Trained
- Posts: 129
- Joined: 21 May 2013, 17:03
-
Lord Apocalypse
- Regular
- Posts: 678
- Joined: 29 Jul 2009, 18:01
Re: Hmm how to compile current version?
That page is outdated for windows as well. I have some files around here somewhere... I don't think any of the current WZ devs use windows so windows related compiles are highly outdated and highly unreliable.
I will see what I can do on creating a new compile package though as I have been using VS2010 for Vega Strike. Another project that for the longest had no windows devs (had to rebuild the entire win32 project by hand based off 2 year old build. Was not fun).
Anyway, not sure where I have all that stuff so give me a few days to sort it out. I do remember there being several issues getting it running though. You can check out the thread I created awhile back Compiling 3.1 with Visual Studio. Read over the whole thing and you will get an idea of how to get it compiled correctly. Be aware that even that post/devpkg is a year old and may not fully work with git-master.
If you have any problems let me know in my old thread. Maybe we can get the name changed and the thread stickied.
I will see what I can do on creating a new compile package though as I have been using VS2010 for Vega Strike. Another project that for the longest had no windows devs (had to rebuild the entire win32 project by hand based off 2 year old build. Was not fun).
Anyway, not sure where I have all that stuff so give me a few days to sort it out. I do remember there being several issues getting it running though. You can check out the thread I created awhile back Compiling 3.1 with Visual Studio. Read over the whole thing and you will get an idea of how to get it compiled correctly. Be aware that even that post/devpkg is a year old and may not fully work with git-master.
If you have any problems let me know in my old thread. Maybe we can get the name changed and the thread stickied.