UFO:Alien Invasion

Archive => Bugs prior to release 2.3 => Topic started by: White_Cat on September 01, 2009, 04:46:07 am

Title: Warnings generated by Code:Blocks...
Post by: White_Cat on September 01, 2009, 04:46:07 am
Quote
||=== ufo2map, windows_debug ===|
C:\Games\UFOAI-2.2.1\codeblocks\MinGW\include\jconfig.h|25|warning: "HAVE_STDLIB_H" redefined|
C:\Games\UFOAI-2.2.1\codeblocks\MinGW\include\SDL\SDL_config.h|67|warning: this is the location of the previous definition|
||=== ufo, windows_debug ===|
C:\UFOAI\src\client\campaign\cp_fightequip_callbacks.c|137|warning: 'AII_GetTechnologyToDisplay' defined but not used|
C:\UFOAI\src\client\renderer\r_error.h|49|warning: 'R_CheckErrorDebug' defined but not used|
||=== Build finished: 0 errors, 4 warnings ===|

While warnings don't really matter since they are so few of them... Might as well eliminate them...
Title: Re: Warnings generated by Code:Blocks...
Post by: polyvios on September 01, 2009, 04:43:07 pm
The first one is libjpeg's fault for a while now and for many programs.  I think the debian people edit libjpeg.h and remove the declaration in their packages, it creates this warning for everyone using autoconf with libjpeg.  To get rid of it, complain to libjpeg developers, or edit libjpeg.h and remove bogus #define.  You might *have* to, I think gcc 4.3 makes it an error now.
Title: Re: Warnings generated by Code:Blocks...
Post by: White_Cat on September 01, 2009, 11:31:27 pm
It should be fixed via svn...
Title: Re: Warnings generated by Code:Blocks...
Post by: Kildor on September 02, 2009, 03:20:45 am
The problem is "C:\Games\UFOAI-2.2.1\codeblocks\MinGW\include\jconfig.h" is not in SVN.
Title: Re: Warnings generated by Code:Blocks...
Post by: White_Cat on September 02, 2009, 03:29:06 am
The problem is "C:\Games\UFOAI-2.2.1\codeblocks\MinGW\include\jconfig.h" is not in SVN.

Well... What about the other two warnings?

Also is there any warning-less header files for the ones broken over here :)
Title: Re: Warnings generated by Code:Blocks...
Post by: Kildor on September 02, 2009, 03:32:20 am
Other warnings mean «Work in progress».And we see that messages as you.

> Also is there any warning-less header files for the ones broken over here
may be, but this is wrong way to fix.