CodeBlocks Crashing, Massive Number of Build Warnings Recently

[Destructavator]

Just thought I'd let the coders know, over the past several days many SVN snapshots crash CodeBlocks, and those that don't compile the project with over a thousand and a half warnings, as opposed to over a week ago when there were only ~23 or so warnings.

I also wanted to upload a new dev build over the weekend, but kept getting very unstable builds with bugs that made the test installer unplayable.

I'm still using the same machine, same setup, same pre-packaged Codeblocks package that Mattn uploaded, etc., I'm not sure what's going on.

I've attached some logs from Codeblocks - am I doing something wrong?  Did the dependencies or setup for CodeBlocks change?

[attachment deleted by admin]

[Kildor]

there was a commit enabled all possible warnings while compiling. So, look to logs and revert it. And build itself is stable enougth for me, except Radiant, what doesn`t run at all.

[BTAxis]

mattn doesn't want to revert it in the SVN itself though. Also, it's easier to just change the option manually. Activate the ufo project, go to build options, then additional options and remove the last two -W statements there.

Also, C::B crashes for me too. It's actually random, with no relation to the actual SVN revision.

[Destructavator]

there was a commit enabled all possible warnings while compiling. So, look to logs and revert it.

Sorry, but I'm having trouble understanding your English in this statement, no offense intended - Could you please rephrase that or state it another way?

A more important question - Do I need to change any settings or do anything different to build UFO:AI?

I've been simply opening the workspace file and selecting "rebuild workspace" every time.

UPDATE:  Looks like you posted at about the same time, BTAxis - Is removing the two -W statements needed for the game to run better?  If the end result isn't any different, should I just go on as usual when Codeblocks doesn't crash?

[BTAxis]

The result isn't any different. I just find compilation takes much longer with the options on (because of all the message printing).

[Duke]

I'd strongly recommend to permanently remove those two -W options.
- As many of the generated warnings come from the std includes, what you're gonna do about it ??
- C::B is obviously not capable of handling them. It never crashed on me before.

Furthermore I get a lot of linking errors with current svn (rev 20029), e.g.
D:\UFO\src\client\cl_actor.c|256|undefined reference to `va'|
D:\UFO\src\client\cl_actor.c|256|undefined reference to `Cvar_Set'|

[Duke]

Update: Link errors are gone, probably because I let the update to rev 20030 replace ufo.cbp.

[bayo]

I also remove the -ansi  few day ago, it create a lot (euphemism) warning on Windows. Its a mistake if i commit it, but without it, we can compile in peace