The 16 June 2013 build (9158) is out.

[ToApolytoXaos]

The files you've opened have both windows and linux line endings in them. This is just a warning.

OK, but the files have been created under Debian as I have been doing for ages and never had any similar issue. Oh well...

Search the forum for the proper -fno- blabla option to disable them. Probably you can fine them in the topics for mingw 4.8 or tdm 4.8.

I have done so with wxMSW compilation procedure and still would get warning messages periodically; with C::B workspace though, where shall I add the specific flag to disable all these warnings?

[oBFusCATed]

Project or compiler level...

[Alpha]

It might be best to add the flags to the global variable cb_release_type.

[stahta01]

I added the "-Wno-unused-local-typedefs" to the Compiler Global "other options".

Tim S.

[ToApolytoXaos]

It might be best to add the flags to the global variable cb_release_type.

It seems your way is indeed very convenient next to -g. Thank you both @stahta01 and @Alpha; currently compiling it and I hope it will finish sooner than 300 minutes without my interruption LOL!

[White-Tiger]

my CB build currently has "-w" set It just took ages otherwise.... (and as I'm not a CB dev, and not gonna fix ya bugs, I don't care about warnings )

[Alpha]

my CB build currently has "-w" set It just took ages otherwise.... (and as I'm not a CB dev, and not gonna fix ya bugs, I don't care about warnings )

I think my build has a few more flags than yours
-ansi -Wall -Wextra -Wmissing-include-dirs -Wunreachable-code -Winline -Wundef -Wcast-align -Wredundant-decls -Winit-self -Wshadow -Wnon-virtual-dtor -Wno-long-long -Wno-variadic-macros -Wno-unused-local-typedefs -Werror=return-type

[White-Tiger]

You're on Linux right? Well.. in my Windoze machine it takes 20-40 minutes to compile CB and it's contrib items.
If I had warnings enabled, it would take more then 3 hours because of that warning spam I get... (and the fact that Windoze is slow as hell... especially in terms of console output^^)
As I'm always using the latest GCC, I was probably one of the first ones who have seen all these numerous warnings. It all started with GCC 4.8.. before that, the warnings were few and not really important. (I don't know how much impact they had...)

Anyway.. none the less it would be nice to see you guys not ignoring these warnings and instead fixing them Actually they all have their reasons and it's way easier once you've got rid of them. As then, every warning will be a single one caused by recent changes and is easy to see and fix.

[stahta01]

You're on Linux right? Well.. in my Windoze machine it takes 20-40 minutes to compile CB and it's contrib items.
If I had warnings enabled, it would take more then 3 hours because of that warning spam I get... (and the fact that Windoze is slow as hell... especially in terms of console output^^)
As I'm always using the latest GCC, I was probably one of the first ones who have seen all these numerous warnings. It all started with GCC 4.8.. before that, the warnings were few and not really important. (I don't know how much impact they had...)

Anyway.. none the less it would be nice to see you guys not ignoring these warnings and instead fixing them Actually they all have their reasons and it's way easier once you've got rid of them. As then, every warning will be a single one caused by recent changes and is easy to see and fix.

I suggest you do this at the wxWidgets team and see the results.

You do realize the cause of the warning is them or can you NOT read!

Tim S.