ea5641baee
Previously, all of the README files have been renamed to README.md and now, the contents of these files were changed to use Markdown format. Other than format inconsistency, some README.md files lacked information about modules, or were out of date. By using LibreOffice / OpenOffice wiki and other documentation websites, these files were updated. Now every README.md file has a title, and some description. The top-level README.md file is changed to add links to the modules. The result of processing the Markdown format README.md files can be seen at: https://docs.libreoffice.org/ Change-Id: Ic3b0c3c064a2498d6a435253b041df010cd7797a Reviewed-on: https://gerrit.libreoffice.org/c/core/+/113424 Tested-by: Jenkins Reviewed-by: Michael Stahl <michael.stahl@allotropia.de> Reviewed-by: Adolfo Jayme Barrientos <fitojb@ubuntu.com>
19 lines
834 B
Markdown
19 lines
834 B
Markdown
# Language Code Generators for UNOIDL Entities
|
|
|
|
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;
|
|
|
|
which can be a source of confusion.
|