Gitiles
Code Review Sign In
gerrit.collaboraoffice.com / core / 29d56f91ee09f91dc7955e2f1ecb711f2f680c4e
commit29d56f91ee09f91dc7955e2f1ecb711f2f680c4e[log] [tgz]
authorPatrick Luby <guibmacdev@gmail.com>Mon Apr 28 19:10:24 2025 -0400
committerChristian Lohmaier <lohmaier+LibreOffice@googlemail.com>Wed Apr 30 12:24:22 2025 +0200
tree1523d8aedf61ee034dec9f9b146f7fb6e616f3cc
parentcb2710979fce2990dd47b4f09d44843ca323f5d3 [diff]
tdf#144200 Add CFBundleSupportedPlatforms key with MacOSX as its only platform

The necessity of including the CFBundleSupportedPlatforms key in an
application that does not include the Intel architecture is described
in the following post:

https://github.com/microsoft/vscode/issues/121169#issuecomment-820653677

The above post is quoted below:

"Its just an issue with which attribute the storage info queries to
decide the kind, the output of system_profiler SPApplicationsDataType -xml
shows the arch_kind is arch_ios. I think these look for
CFBundleSupportedPlatforms attribute and if not present default to the ios
kind for arm64 executables.

Given the universal and intel labels show up correctly, and considering
the output of other apple silicon apps in the image posted. I don't think
this needs a fix, but leaving it open for anyone to address as a good
first issue."

Change-Id: Ic96ce4407e060fbb0cb8c7b0b72dcf8f61dade19
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/184738
Tested-by: Jenkins
Reviewed-by: Patrick Luby <guibomacdev@gmail.com>
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
(cherry picked from commit 562a40f453caa003187ff28c7798647d9e0b4ded)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/184771
1 file changed
tree: 1523d8aedf61ee034dec9f9b146f7fb6e616f3cc
  1. .git-hooks/
  2. .github/
  3. .vscode/
  4. accessibility/
  5. android/
  6. animations/
  7. apple_remote/
  8. avmedia/
  9. basctl/
  10. basegfx/
  11. basic/
  12. bean/
  13. bin/
  14. binaryurp/
  15. bridges/
  16. canvas/
  17. chart2/
  18. cli_ure/
  19. codemaker/
  20. comphelper/
  21. compilerplugins/
  22. config_host/
  23. configmgr/
  24. connectivity/
  25. cppcanvas/
  26. cppu/
  27. cppuhelper/
  28. cpputools/
  29. cui/
  30. dbaccess/
  31. desktop/
  32. distro-configs/
  33. docmodel/
  34. drawinglayer/
  35. editeng/
  36. embeddedobj/
  37. embedserv/
  38. emfio/
  39. eventattacher/
  40. extensions/
  41. external/
  42. extras/
  43. filter/
  44. forms/
  45. formula/
  46. fpicker/
  47. framework/
  48. helpcompiler/
  49. hwpfilter/
  50. i18nlangtag/
  51. i18npool/
  52. i18nutil/
  53. icon-themes/
  54. idl/
  55. idlc/
  56. include/
  57. instsetoo_native/
  58. io/
  59. ios/
  60. javaunohelper/
  61. jurt/
  62. jvmaccess/
  63. jvmfwk/
  64. l10ntools/
  65. librelogo/
  66. libreofficekit/
  67. lingucomponent/
  68. linguistic/
  69. lotuswordpro/
  70. m4/
  71. msicreator/
  72. nlpsolver/
  73. o3tl/
  74. odk/
  75. offapi/
  76. officecfg/
  77. oovbaapi/
  78. oox/
  79. opencl/
  80. osx/
  81. package/
  82. pch/
  83. postprocess/
  84. pyuno/
  85. qadevOOo/
  86. readlicense_oo/
  87. registry/
  88. remotebridges/
  89. reportbuilder/
  90. reportdesign/
  91. ridljar/
  92. sal/
  93. salhelper/
  94. sax/
  95. sc/
  96. scaddins/
  97. sccomp/
  98. schema/
  99. scp2/
  100. scripting/
  101. sd/
  102. sdext/
  103. setup_native/
  104. sfx2/
  105. shell/
  106. slideshow/
  107. smoketest/
  108. solenv/
  109. soltools/
  110. sot/
  111. starmath/
  112. static/
  113. stoc/
  114. store/
  115. svgio/
  116. svl/
  117. svtools/
  118. svx/
  119. sw/
  120. swext/
  121. sysui/
  122. test/
  123. testtools/
  124. toolkit/
  125. tools/
  126. ucb/
  127. ucbhelper/
  128. udkapi/
  129. uitest/
  130. UnoControls/
  131. unodevtools/
  132. unoidl/
  133. unoil/
  134. unotest/
  135. unotools/
  136. unoxml/
  137. ure/
  138. uui/
  139. vbahelper/
  140. vcl/
  141. winaccessibility/
  142. wizards/
  143. writerperfect/
  144. xmerge/
  145. xmlhelp/
  146. xmloff/
  147. xmlreader/
  148. xmlscript/
  149. xmlsecurity/
  150. dictionaries
  151. helpcontent2
  152. translations
  153. .buckconfig
  154. .buckversion
  155. .clang-format
  156. .editorconfig
  157. .git-blame-ignore-revs
  158. .gitattributes
  159. .gitignore
  160. .gitmodules
  161. .gitpod.dockerfile
  162. .gitpod.yml
  163. .gitreview
  164. antivirusDetection.vbs
  165. autogen.sh
  166. BUCK
  167. config.guess
  168. config.sub
  169. config_host.mk.in
  170. config_host_lang.mk.in
  171. configure.ac
  172. COPYING
  173. COPYING.LGPL
  174. COPYING.MPL
  175. cpp.hint
  176. download.lst
  177. g
  178. install-sh
  179. install_deps.sh
  180. leak-suppress.txt
  181. Library_merged.mk
  182. logerrit
  183. Makefile.fetch
  184. Makefile.gbuild
  185. Makefile.in
  186. README.cross
  187. README.help.md
  188. README.md
  189. README.Solaris
  190. Repository.mk
  191. RepositoryExternal.mk
  192. RepositoryFixes.mk
  193. RepositoryModule_build.mk
  194. RepositoryModule_host.mk
  195. sanitize-ubsan-excludelist
  196. setup.cfg
  197. TEMPLATE.SOURCECODE.HEADER
  198. tsan-suppress.txt
README.md

LibreOffice

Coverity Scan Build Status CII Best Practices Translation status

LibreOffice is an integrated office suite based on copyleft licenses and compatible with most document formats and standards. Libreoffice is backed by The Document Foundation, which represents a large independent community of enterprises, developers and other volunteers moved by the common goal of bringing to the market the best software for personal productivity. LibreOffice is open source, and free to download, use and distribute.

A quick overview of the LibreOffice code structure.

Overview

You can develop for LibreOffice in one of two ways, one recommended and one much less so. First the somewhat less recommended way: it is possible to use the SDK to develop an extension, for which you can read the API docs and Developers Guide. This re-uses the (extremely generic) UNO APIs that are also used by macro scripting in StarBasic.

The best way to add a generally useful feature to LibreOffice is to work on the code base however. Overall this way makes it easier to compile and build your code, it avoids any arbitrary limitations of our scripting APIs, and in general is far more simple and intuitive - if you are a reasonably able C++ programmer.

The Build Chain and Runtime Baselines

These are the current minimal operating system and compiler versions to run and compile LibreOffice, also used by the TDF builds:

  • Windows:
    • Runtime: Windows 7
    • Build: Cygwin + Visual Studio 2019 version 16.10
  • macOS:
    • Runtime: 10.15
    • Build: 12 (13 for aarch64) + Xcode 14
  • Linux:
    • Runtime: RHEL 8 or CentOS 8 and comparable
    • Build: either GCC 12; or Clang 12 with libstdc++ 10
  • iOS (only for LibreOfficeKit):
    • Runtime: 11.4 (only support for newer i devices == 64 bit)
    • Build: Xcode 9.3 and iPhone SDK 11.4
  • Android:
    • Build: NDK r23 and SDK 30.0.3
  • Emscripten / WASM:
    • Runtime: a browser with SharedMemory support (threads + atomics)
    • Build: Qt 5.15 with Qt supported Emscripten 1.39.8
    • See README.wasm

Java is required for building many parts of LibreOffice. In TDF Wiki article Development/Java, the exact modules that depend on Java are listed.

The baseline for Java is Java Development Kit (JDK) Version 17 or later.

If you want to use Clang with the LibreOffice compiler plugins, the minimal version of Clang is 12.0.1. Since Xcode doesn't provide the compiler plugin headers, you have to compile your own Clang to use them on macOS.

You can find the TDF configure switches in the distro-configs/ directory.

To setup your initial build environment on Windows and macOS, we provide the LibreOffice Development Environment (LODE) scripts.

For more information see the build instructions for your platform in the TDF wiki.

The Important Bits of Code

Each module should have a README.md file inside it which has some degree of documentation for that module; patches are most welcome to improve those. We have those turned into a web page here:

https://docs.libreoffice.org/

However, there are two hundred modules, many of them of only peripheral interest for a specialist audience. So - where is the good stuff, the code that is most useful. Here is a quick overview of the most important ones:

ModuleDescription
sal/this provides a simple System Abstraction Layer
tools/this provides basic internal types: Rectangle, Color etc.
vcl/this is the widget toolkit library and one rendering abstraction
framework/UNO framework, responsible for building toolbars, menus, status bars, and the chrome around the document using widgets from VCL, and XML descriptions from /uiconfig/ files
sfx2/legacy core framework used by Writer/Calc/Draw: document model / load/save / signals for actions etc.
svx/drawing model related helper code, including much of Draw/Impress

Then applications

ModuleDescription
desktop/this is where the main() for the application lives, init / bootstrap. the name dates back to an ancient StarOffice that also drew a desktop
sw/Writer
sc/Calc
sd/Draw / Impress

There are several other libraries that are helpful from a graphical perspective:

ModuleDescription
basegfx/algorithms and data-types for graphics as used in the canvas
canvas/new (UNO) canvas rendering model with various backends
cppcanvas/C++ helper classes for using the UNO canvas
drawinglayer/View code to render drawable objects and break them down into primitives we can render more easily.

Rules for #include Directives (C/C++)

Use the "..." form if and only if the included file is found next to the including file. Otherwise, use the <...> form. (For further details, see the mail Re: C[++]: Normalizing include syntax ("" vs <>).)

The UNO API include files should consistently use double quotes, for the benefit of external users of this API.

loplugin:includeform (compilerplugins/clang/includeform.cxx) enforces these rules.

Finding Out More

Beyond this, you can read the README.md files, send us patches, ask on the mailing list libreoffice@lists.freedesktop.org (no subscription required) or poke people on IRC #libreoffice-dev on irc.libera.chat - we're a friendly and generally helpful mob. We know the code can be hard to get into at first, and so there are no silly questions.