fixed #12059 - added --fsigned-char and --funsigned-char command-line options

[firewave]

No description provided.

[danmar]

why not just create a platform file instead? we get multiple options to perform the same task.

[firewave]

why not just create a platform file instead? we get multiple options to perform the same task.

Because it can be controlled via a compiler flag. The platform would only reflect the default (which we are not doing properly yet) and if you want to change that you have to create a temporary copy of the platform file and adjust that value which is very inconvenient.

This is in preparation of #4960.

Also it being a compiler flag that could actually modified for each file separately. So that should not be part of the platform at all but needs to be handled completely different. How much sense that would make is questionable to me.

[danmar]

It still feels redundant but well supporting some gcc flags does make sense to me..

Also it being a compiler flag that could actually modified for each file separately. So that should not be part of the platform at all but needs to be handled completely different. How much sense that would make is questionable to me.

Yeah why would people do that? :-)

[firewave]

Yeah why would people do that? :-)

Thinking about it. In case of projects files which might contains various different resulting binaries that might be valid though.

[firewave]

See https://trac.cppcheck.net/ticket/12089 also. I need to elaborate more in the ticket though.