1 |
Hi all, |
2 |
|
3 |
I've been wondering - is there any eclass for fixing gcc warnings in $SUBJ |
4 |
for C/C++ source files? I know it's upstream's job to fix these, and that they |
5 |
have no effect on the compilation, but all there needs to be done is |
6 |
'echo "" >> $file', and let's face it - it looks nicer when the code compiles |
7 |
without unnecessary warnings, to both dev's and user's eye. This is especially |
8 |
valid for packages which have main development for Windows version, and |
9 |
upstream simply does not care. |
10 |
|
11 |
If there is not such a tool and there is some positive feedback about this, I |
12 |
will write an eclass for this. |
13 |
|
14 |
IDEA: merge this new functionality with fixheadtails.eclass and change the |
15 |
name to something like sourceutils.eclass, where possibly similar tools could |
16 |
be added in the future. |
17 |
|
18 |
-- |
19 |
Andrej "Ticho" Kacian <ticho at gentoo dot org> |
20 |
Gentoo Linux Developer - net-mail, antivirus, amd64 |