Win32 Development Binary Installer Links

[iliaarpad]

New installer (r22752) was here.

EDIT: Installer installs non-working game. Please don't use it until a resolution is found. Sorry for the inconvenience.
EDIT 2: Removed file from FileFront.

[Muton]

> EDIT: Installer installs non-working game. Please don't use it until a resolution is found. Sorry for the inconvenience.

What's you'r problem, and ho do you build UfoAI
In my newest build i can run the game
but after pressing "single-player" the game crash
with no message

[iliaarpad]

Did you build your own installer and does that crash when single player is selected, too? Because right now I'm about to start pulling my hair out.

The problem is exactly that the game crashes after selecting single player and I assumed it was the fault of my installer.
When running with the Codeblocks debugger I get the message that the program got a SIGSEGV because of a Segmentation Fault. Unfortunately I'm really not at home with non-object oriented languages (such as C) so I can't really tell what is causing the Segmentation Fault.

More precisely the debugger message is

Code: [Select]

Program received signal SIGSEGV, Segmentation fault.
In ?? () ()

[Muton]

remove the newly added option
<Add option="-O2" />
inside build\projects\ufo.cbp
and rebuild
codeblocks.exe --rebuild V:\MinGW\ufoai\build\projects\ufo.cbp

I was able to build a working ufo.exe with these options too
<Add option="-march=i686" />
<Add option="-fexpensive-optimizations" />
but the option
<Add option="-O3" />
or
<Add option="-O2" />
let ufo.exe crash again

I've build ufo.exe before with options
<Add option="-march=i686" />
<Add option="-fexpensive-optimizations" />
<Add option="-O3" />
and had no problem
during 22707 (last working build was 22614) the game crash with these options
and with
<Add option="-O2" />
allone too

I'm currently not using the last C::B build from BTAxis
maybe thats the problem

[BTAxis]

I don't think that should matter. The only difference with the older package is the gettext version. If that was causing trouble it would crap out on the main menu, probably.

[iliaarpad]

After rebuilding from scratch and watching it crash again, I decided to give it a try and removed the optimization option. The funny thing is that now it doesn't crash. Is it possible that the optimization produces buggy code? I'm using MingW gcc 3.4.5.

After further experimentation it would seem that it crashes whenever I compile it with O2 or more aggressive optimization. When using second level optimization (-O1) or less it works fine and does not crash when selecting the Single Player menu. Anything above that causes a Segmentation Fault.

I suppose it could also be a problem with the compiler (the gcc packaged with MingW is quite old)... I can't really think of anything else.

[Destructavator]

Not being a serious coder outside of HTML and the web-based stuff, so far all of you have used terminology I'm unfamiliar with, but I will say that I've been following the wiki to the letter and using the pre-packaged CB and included MinGW and have not had issues.

I will say that I do have a programming background, coming from working on C64 machines waaaaay back in the '80s and such, and that I suspect these issues mentioned in the last several posts here are simply because some people here are trying to do something fancy that might not be necessary.  I admit I could be wrong and way off, as I don't work with C too much, but that's my guess.

Regardless, I've just built a new installer of rev 22773 with fully re-built maps and I'm going to upload it to Filefront tonight over-night.

[iliaarpad]

I was following the wiki as well - except that the MingW packaged with the Codeblocks version there didn't quite work for me (my bet would be my OS: Vista). I had to install the candidate MingW compiler separately which may still have some bugs.
Meaning I have to use a (in theory) unstable compiler
Since you also create installers regularly using a stable compiler and you are also uploading to FileFront I'll stay in reserve.
My builds also have O1 optimization only so in theory your builds should be faster, as well.

@Muton: what compiler version are you using?

[Destructavator]

I was following the wiki as well - except that the MingW packaged with the Codeblocks version there didn't quite work for me (my bet would be my OS: Vista). I had to install the candidate MingW compiler separately which may still have some bugs.

Strange - I'm building the installers on Vista, specifically Home Premium, 32-bit.  Do you have other compilers, IDEs, or other programming tools installed that could be conflicting or otherwise interfering with building UFO: AI?

I also admit that I have no idea what you're referring to with "optimization" and the levels of it - I just use mostly the default settings within the pre-packaged CB, except that I set it to use more than one thread to take advantage of both cores on the machine.

Edit: This is probably a very *long* shot, but do you compile with the target "win32" or "win32_debug"?  I've been using the debug target, not the release one when I build the installers I upload.

[Destructavator]

http://files.filefront.com/13319767

[iliaarpad]

I'm using the default settings as well. I didn't touch anything. I still think that this is because I use the 3.4.5 version of the gcc compiler while the prepackaged Codeblocks comes with version 3.4.2 of the gcc compiler.

Optimization makes the generated code run faster. The more aggressive it is the more effective the code can become. However applying too much optimization can lead sometimes to code instability. The default UFO: AI Codeblocks project adds an option to the compiler telling it to use third level optimization, which should be safe, unless the compiler is buggy. This is why I started to suspect the compiler.

As for other IDE-s, I have Eclipse with sun JDK and Visual Studio 8 installed but I don't think they could cause the problem. When I tried to compile UFO: AI with the 3.4.2 version of the compiler the linker couldn't find some libraries. As soon as I replaced it with the 3.4.5 compiler it started to work.

Since Muton seems to have the same problem as I have, I'm quite curious as to what gcc version he is using. If it is 3.4.5...

Edit:

This is probably a very *long* shot, but do you compile with the target "win32" or "win32_debug"?

Argh... You are right! I don't know when or how but looks like I somehow accidentally changed the target to windows from windows_debug. But I still don't understand why that causes a problem.

[Muton]

@Muton: what compiler version are you using?

mingw-gcc 3.4.2

Destructavator build a debug version
Debugging options do not include any optimation
So there is no magic!

'Couse i'm using optimation on ufo.exe for quite some time (ufo2map too [speed up by >10%])
i knew there was no problem with -O2 or -O3 before 22707
only with optimation -march
Anything higher i686 let the game crash.

[iliaarpad]

Okay, I think I figured it out.

The problem seems to arise at revision 22688 (r22687 runs without segmentation fault when compiled as a release with O2 optimization).
More precisely the problem occurs when the line

Code: [Select]

visiblewhen "mn_main eq singleplayerInGame"
is missing from the button_save block in menu_singleplayer.ufo.

When I add the line back the game runs fine (at least it doesn't crash after selecting the Single Player menu).
So, if you would like to build a release version with O2 optimization enabled add the line above in the button_save block. After that the game will work.
Muton, could you verify it? Could you try adding the line above to the button_save block? Thanks!

[odie]

Okay, I think I figured it out.

The problem seems to arise at revision 22688 (r22687 runs without segmentation fault when compiled as a release with O2 optimization).
More precisely the problem occurs when the line

Code: [Select]

visiblewhen "mn_main eq singleplayerInGame"
is missing from the button_save block in menu_singleplayer.ufo.

When I add the line back the game runs fine (at least it doesn't crash after selecting the Single Player menu).
So, if you would like to build a release version with O2 optimization enabled add the line above in the button_save block. After that the game will work.
Muton, could you verify it? Could you try adding the line above to the button_save block? Thanks!

Hi iliaarpad,

I have been following this thread too. I last built 22773 and i face the same problems.

I guess i will wait for u folks to try fix this before i post more on this.

For now, for your reference, my system:
Win XP SP3, fully patched as of feb 09.

Previously running smoothly up to i believe 22650+- that revision. I patch and update every morning, recompile and bring home to try out. (That is continue the previous save games until it breaks).

As of last nite 22773, it works perfectly up to the single player mode. All other options in the menu (credits, multiplayer, options, even the exit) works fine.

For reference pls.

[geever]

We have investigated this problem last night and Bayo committed a possible fix in r22790.

note: it was only reproducible on windows, release build.

-geever