User forums > Nightly builds
The 16 June 2013 build (9158) is out.
White-Tiger:
my CB build currently has "-w" set :P 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 :P)
Alpha:
--- Quote from: White-Tiger on October 30, 2013, 02:37:21 pm ---my CB build currently has "-w" set :P 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 :P)
--- End quote ---
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:
--- Quote from: White-Tiger on October 30, 2013, 03:40:14 pm ---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.
--- End quote ---
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.
Navigation
[0] Message Index
[*] Previous page
Go to full version