b3c072a4ee
When IWYU is used to check cxx files it also checks associated hxx (but for .hxx -> .h too) files too and gives addition/removal recommendations There is no documented way of disabling this. Currently f-u-i does not differentiate between recommendations for the checked file and its header and prints everything. Which means sometimes I need to update .hxx files or blacklist warnings that interestingly are not shown when the same .hxx is checked with IWYU. The worst example is ucb/source/ucp/ftp/curl.hxx where IWYU gives recommendations for /usr/include/x86_64-linux-gnu/curl/curl.h Remedy this with considering the full filename + should add these lines: / should remove these lines: string as beginning of interesting recommendations Also remove some now obsolete blacklist entries from yaml files Change-Id: I1d139536992e4b56c699c31a4cc6491d373c2002 Reviewed-on: https://gerrit.libreoffice.org/80172 Tested-by: Jenkins Reviewed-by: Miklos Vajna <vmiklos@collabora.com> |
||
|---|---|---|
| .. | ||
| inc/helper | ||
| qa | ||
| source | ||
| test/accessibility | ||
| util | ||
| CppunitTest_toolkit.mk | ||
| IwyuFilter_toolkit.yaml | ||
| JunitTest_toolkit_complex.mk | ||
| JunitTest_toolkit_unoapi_1.mk | ||
| JunitTest_toolkit_unoapi_2.mk | ||
| JunitTest_toolkit_unoapi_3.mk | ||
| JunitTest_toolkit_unoapi_4.mk | ||
| Library_tk.mk | ||
| Makefile | ||
| Module_toolkit.mk | ||
| README | ||
"Abstract" windowing thing, UNO implementations of windowing stuff so that it can be used from Basic or Java. But also stuff that has no connection to Basic or Java. Note that the "awt" here has no relation to the Java awt, as far as I know. It might be inspired by it API-wise, perhaps. (If you know differently, feel free to improve this README file.) Note that toolkit/ is itself not really a toolkit, it is at root a reasonably simple wrapper of vcl/ - if you came here looking for a toolkit, please checkout vcl/ instead.