150ac9cf05
Searched source for using declarations. Checked if those symbols reappear in the source file, even in comments or dead code but not in #include statements. If they don't reappear, remove the declaration. Remove includes whose symbol got removed. Change-Id: Ibb77163f63c1120070e9518e3dc0a78c6c59fab0 Reviewed-on: https://gerrit.libreoffice.org/24148 Reviewed-by: Jochen Nitschke <j.nitschke+logerrit@ok.de> Reviewed-by: Noel Grandin <noelgrandin@gmail.com> Tested-by: Noel Grandin <noelgrandin@gmail.com> |
||
|---|---|---|
| .. | ||
| source | ||
| test/javamaker | ||
| Executable_cppumaker.mk | ||
| Executable_javamaker.mk | ||
| Makefile | ||
| Module_codemaker.mk | ||
| README | ||
| StaticLibrary_codemaker.mk | ||
| StaticLibrary_codemaker_cpp.mk | ||
| StaticLibrary_codemaker_java.mk | ||
Generators for language-binding--specific representations of UNOIDL entities: - cppumaker generates header (.hdl and .hpp) files for the C++ UNO language binding - javamaker generates class files for the JVM language binding - the codemaker for .Net is in module cli_ure Some of the code is re-used by the skeletonmakers in module unodevtools. Note the different terminology used by cppumaker vs. gbuild for the three variants that can be generated by cppumaker for some of the inline functions: cppumaker switch: -L; cpputype.cxx: light; gbuild: normal; cppumaker switch: none; cpputype.cxx: normal; gbuild: bootstrap; cppumaker switch: -C; cpputype.cxx: comprehensive; gbuild: comprehensive; ...a recipe for confusion.