EDIT: I found a way to disable the warnings from third-party codes using GCC. Look at this post right here: http://sphaleron.blogspot.se/2011/06/ignoring-gcc-warnings-on-per-file-basis.html Or as bames53 post said!
I've just upgraded my GCC compiler and all of a sudden I got loads of warnings I never had before. Basically everyone of them is a conversion from int to Sin16 when I don't specify that it should be Sint16.
This example below should throw such a warning:
int number = 6;
SDL_Rect rect = {number, number, number, number};
SDL_Rect expects a Sint16 as input. Anyway, I was starting to fix these warnings (because why not?) when I checked for new ones and to my surprise I received over 100 warnings from the glew file I added to be able to draw with OpenGL more efficiently. I have no plans to go into that code just to fix warnings.
What would you have done? How important is this? If I don't fix them is there a way for me to remove these warnings?
Clarification: I always fix more severe warnings, it's just that all the warnings from my code are Narrowing warnings (in glew.c it's "warning: 'variable' redeclared without dllimport attribute: previous dllimport ignored [-Wattributes]|") and I'm wondering how important it is to fix these, especially since glew threw a whole bunch at me.
glew.cwith the option-Wno-attributes(via makefile, IDE project settings, or the like). If you really don't care about any warnings from that file, use-w(note that this is a lower case w) - jerry