Le 28/08/2012 21:51, Bernd Zeimetz a écrit : > Hi, > >> This summer, during the Google Summer of Code (GSoC), we have been >> working to provide a way to rebuild the archive with a non-gcc compiler >> (in our case: clang). >> >> Our project's intent is not to change the default compiler, just use a >> secondary compiler to generate more errors or warnings for package >> maintainers to be aware of. In most cases, keeping both compilers happy >> would result in higher quality code, something I think we can all get >> behind. > I think it would be great if we could build all packages with scan-build > automatically - as soon as there is some way to specify a different compiler, > this should not be too hard. It might even be enough to use gcc/g++ as > compiler > in scan-build. I'm running some of my favourite packages trough it, which > makes > upstream happy (well or not, if some new errors show up again :)). So making > all > packages respect CC/CXX would be good to have not only to build them with > different compilers. You just spoiled one of my todo list item. ;)
For those who don't know scan-build, it is a free static analyzer distributed with clang. It gives nice feedbacks on common errors which cannot be find by "normal" checks by compiler. For example, scan-build on llvm & clang: http://lbalbalba.x90x.net/clang-analyzer/llvm-clang/r162646/ > Cheers and thanks for your work, Thanks for your feedback. Sylvestre -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/503d234b.6000...@debian.org
