I spent the better part of last night trying to build an Allegiance.exe from just the unchanged trunk.
It's a nightmare.
If we want more people to participate in developing the game, we shouldn't throw up an entry bar in the form of having to buy or steal pro versions of compiling software.
Make it easier to compile alleg in VS express
-
Bunnywabbit
- Posts: 965
- Joined: Sun May 15, 2005 7:00 am
- Location: Amsterdam, the Netherlands
Last edited by Bunnywabbit on Sun Jan 15, 2012 12:37 pm, edited 1 time in total.

current version r158 new beta as of jan 23 2012-
Spunkmeyer
- Posts: 2013
- Joined: Fri Jun 27, 2003 7:00 am
- Location: Contact me regarding: CC, Slayer and AllegWiki.
So did you make it or no?
If you made it, a list of steps would be helpful, otherwise a list of issues would be helpful. It's pretty straightforward with the regular version so I don't know what the issues are - I'd have to set it up on a different machine.
If you made it, a list of steps would be helpful, otherwise a list of issues would be helpful. It's pretty straightforward with the regular version so I don't know what the issues are - I'd have to set it up on a different machine.
Last edited by Spunkmeyer on Sun Jan 15, 2012 3:05 pm, edited 1 time in total.
Want bigger games? Log on to play at the official game time: 9pmET/8pmCT/7pmMT/6pmPT every day of the week. Also Saturdays 8pm UTC.
-
Bunnywabbit
- Posts: 965
- Joined: Sun May 15, 2005 7:00 am
- Location: Amsterdam, the Netherlands
Not within the boundaries of the law, I didn't.
to clarify: no, I still havent gotten it to work. Spent upwards of six hours already just trying to set up the workspace and still not done.
to clarify: no, I still havent gotten it to work. Spent upwards of six hours already just trying to set up the workspace and still not done.
Last edited by Bunnywabbit on Sun Jan 15, 2012 10:24 pm, edited 1 time in total.

current version r158 new beta as of jan 23 2012-
privateerm
- Posts: 273
- Joined: Sun Aug 05, 2007 2:17 am
- Location: NB Canada
Ok, this doesn't solve the problem for everyone, but www.dreamspark.com
If are in school or even took a course with any number of the schools out there registered with them, then you can get most of the visual studio products(full versions) for free.
If are in school or even took a course with any number of the schools out there registered with them, then you can get most of the visual studio products(full versions) for free.
Blah blah blah blah (breath) blah blah blah blah (breath) oh, what was this thread about again......
-
Bunnywabbit
- Posts: 965
- Joined: Sun May 15, 2005 7:00 am
- Location: Amsterdam, the Netherlands
done.
to elaborate:
requirements: around 4 GB hard disk space on system partition, regardless of installation directory.
1.VS 2010 pro (Epress won't work). Ask Santa for a copy.
2. Windows SDK 7.1
- http://www.microsoft.com/download/en/details.aspx?id=8279
- Note: If you're downloading ISO, make sure you download the correct one (x64 or x86)!
3. Install DirectX SDK (June 2010)
- http://www.microsoft.com/download/en/details.aspx?id=6812
4. Install Visual Studio 2010 SP1
- http://www.microsoft.com/download/en/details.aspx?id=23691
5. Visual C++ 2010 SP1 Compiler Update for the Windows SDK 7.1
- http://www.microsoft.com/download/en/details.aspx?id=4422
with thanks to PKK for the hand-holding and muttering of soothing songs while I wrestled through this.
to elaborate:
requirements: around 4 GB hard disk space on system partition, regardless of installation directory.
1.VS 2010 pro (Epress won't work). Ask Santa for a copy.
2. Windows SDK 7.1
- http://www.microsoft.com/download/en/details.aspx?id=8279
- Note: If you're downloading ISO, make sure you download the correct one (x64 or x86)!
3. Install DirectX SDK (June 2010)
- http://www.microsoft.com/download/en/details.aspx?id=6812
4. Install Visual Studio 2010 SP1
- http://www.microsoft.com/download/en/details.aspx?id=23691
5. Visual C++ 2010 SP1 Compiler Update for the Windows SDK 7.1
- http://www.microsoft.com/download/en/details.aspx?id=4422
with thanks to PKK for the hand-holding and muttering of soothing songs while I wrestled through this.
Last edited by Bunnywabbit on Mon Jan 16, 2012 1:38 pm, edited 1 time in total.

current version r158 new beta as of jan 23 2012I find odd that you need to install the Win SDK and that express version doesn't work.
I can't test on my systems since they all have VS pro already on them but if someone can post the errors you get with the express version we might find where the problem is.
Because afaik, the code doesn't require anything the express version doesn't do.
Latest Direct X + VC Express should be all that is required to build Allegiance.
I can't test on my systems since they all have VS pro already on them but if someone can post the errors you get with the express version we might find where the problem is.
Because afaik, the code doesn't require anything the express version doesn't do.
Latest Direct X + VC Express should be all that is required to build Allegiance.
-
fuzzylunkin1
It's been known for a while that Express doesn't have everything needed. Something about ATL/MFC libs (for allsrv).KGJV wrote:QUOTE (KGJV @ Jan 16 2012, 01:08 PM) I find odd that you need to install the Win SDK and that express version doesn't work.
I can't test on my systems since they all have VS pro already on them but if someone can post the errors you get with the express version we might find where the problem is.
Because afaik, the code doesn't require anything the express version doesn't do.
Latest Direct X + VC Express should be all that is required to build Allegiance.
-
Bunnywabbit
- Posts: 965
- Joined: Sun May 15, 2005 7:00 am
- Location: Amsterdam, the Netherlands
In theory, practice should be the same as the theory. In practice, it isn't.
You get 1083 errors related to stuff like 'atlbase.h' and so on.
Also 'invalid option' (or somesuch) errors relating to an '-ologo' setting, which i'm guessing is a typo of a '-nologo' switch.
Basically you run into one error after another, VS is throwing up warnings and errors all over the place and you don't know which are important and which you can ignore.
That and the instructions on the wiki aren't correct or up to date (it says use FAZDebug when you should use FAZRetail if you just want to try out some simple changes), which makes it extremely hard for a relatively intelligent, yet clueless creature such as myself to participate.
Anyway, with help from PKK and Santa, I managed to get a working Dev environment set up, and I tested and submitted my very first patch. Go me.
You get 1083 errors related to stuff like 'atlbase.h' and so on.
Also 'invalid option' (or somesuch) errors relating to an '-ologo' setting, which i'm guessing is a typo of a '-nologo' switch.
Basically you run into one error after another, VS is throwing up warnings and errors all over the place and you don't know which are important and which you can ignore.
That and the instructions on the wiki aren't correct or up to date (it says use FAZDebug when you should use FAZRetail if you just want to try out some simple changes), which makes it extremely hard for a relatively intelligent, yet clueless creature such as myself to participate.
Anyway, with help from PKK and Santa, I managed to get a working Dev environment set up, and I tested and submitted my very first patch. Go me.

current version r158 new beta as of jan 23 20121083 errors are missing include files errors so indeed it must be missing ATL stuff.
and it's true that VC Express doesn't officially support ATL/MFC and the usual workaround, at least for ATL, is to install the WDK or the platform SDK. But then hand tweak some files too...
Ideally we need to do like we did with DirectPlay and add the missing includes & libs directly to the Allegiance source.
Well since you fixed your problem, I guess we will have to wait for someone else to run in the same problem again.
and it's true that VC Express doesn't officially support ATL/MFC and the usual workaround, at least for ATL, is to install the WDK or the platform SDK. But then hand tweak some files too...
Ideally we need to do like we did with DirectPlay and add the missing includes & libs directly to the Allegiance source.
Well since you fixed your problem, I guess we will have to wait for someone else to run in the same problem again.
-
Spunkmeyer
- Posts: 2013
- Joined: Fri Jun 27, 2003 7:00 am
- Location: Contact me regarding: CC, Slayer and AllegWiki.
