path: root/configmgr/
AgeCommit message (Collapse)AuthorFilesLines
2017-04-21gbuild: Remove MSVC 2013 legacy codeDavid Ostrovsky1-1/+0
Uwinapi is discontinued. Change-Id: I063b4d0d8fab2d60de168e960a63b8181158ac01 Reviewed-on: Reviewed-by: David Ostrovsky <> Tested-by: David Ostrovsky <>
2015-09-01Rename stuff, in preparation of dconf::writeModificationsStephan Bergmann1-1/+1
Change-Id: Icd472e91b222907e2cdcbdba1b78b33c44eff566
2015-07-08configmgr: support reading from a dconf layer (WIP)Stephan Bergmann1-2/+6
Work in progress to allow integration of LO with <>. During configuration, dconf support is implicitly enabled when available on the host (which is presumably only available on Linux). It is explicitly disabled for TDF Linux builds for now, though, to avoid accidental dependencies of the distributed installation sets on system dconf libraries. A dconf layer is represented in the CONFIGURATION_LAYERS bootstrap variable with type "dconf" and an empty URL. See the comment at the top of configmgr/source/readdconflayer.cxx for the encoding of component-data in dconf. All of this is still subject to change. Change-Id: I2d08d81c8ea43ba4a99040a8882ae75b91bcfdb9 Reviewed-on: Tested-by: Jenkins <> Reviewed-by: Stephan Bergmann <>
2015-02-16restore dependenciesCaolán McNamara1-0/+2
Change-Id: I20645122bc80d729093dff8d1a8094c6fbf7d68a
2015-02-16boost::noncopyable->'= delete'Caolán McNamara1-2/+0
Change-Id: If0f898a1e912fcd2095d8ba88b2b8046596e16ea
2014-05-22update_pch: add configmgrThomas Arnhold1-0/+2
Change-Id: I74f1a032ebce8e4fa13d4afd7f520bbb367b2df5
2013-09-10Windows registry configuration backendJanos Farago1-2/+3
The goal is to manage LibreOffice configuration centrally in the enterprise. In Windows Server environment using Group Policies is a common solution for configuration management. Therefore it is required that LibreOffice can read configuration data from Windows registry, too. Windows registry is another configuration layer on the top of normal xml based configuration. For example the following registry setting: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\LibreOffice\org.openoffice.UserProfile\Data\o] "Value"="Example Corp." "Final"=dword:00000001 becomes the following in configuration: <item oor:path="/org.openoffice.UserProfile/Data"> <prop oor:name="o" oor:finalized="true"> <value>Example Corp.</value> </prop> </item> Change-Id: I2cdd83fc93922bf2806417bfd1b83f85cc926d4c Signed-off-by: Stephan Bergmann <>
2013-04-30Move to MPLv2 license headers, with ESC decision and author's permission.Michael Meeks1-27/+7
2013-04-05new module i18nlangtagEike Rathke1-1/+1
Moved portions from module i18npool, all of former i18nisolang1 library that now is i18nlangtag. Included are languagetag, isolang and mslangid. This i18nlangtag code is now even used by module comphelper, so disentangling i18npool and making this an own module was needed to not create circular module dependencies. Change-Id: Ib887c3d6dde667403fd22d382310ba5f1a9b0015
2013-03-28use LanguageTag instead of comphelper::LocaleEike Rathke1-0/+1
Change-Id: I98cac783ff1db94d1d7135dd0db8ee0d809b3457
2013-01-26gbuild: do not copy boost headers aroundMichael Stahl1-0/+2
- do not use gb_UnpackedTarball_copy_header_files for boost - adapt the optimization in concat-deps.c for new path - use boost_headers in all LinkTargets that require it - add explicit include paths to mysqlc, mysqlcppconn, libvisio, liborcus Change-Id: I0c43e73ed43cc9d2e6bce8faf55e992d655a0bb9
2012-09-28gbuild: invert handling of standard system libraries:Michael Stahl1-2/+0
Always link in gb_STDLIBS, except when the library explicitly opts out with gb_LinkTarget_disable_standard_system_libs. Change-Id: I489a99114fbfa46d0421a27cf6c7b899dc268a4a
2012-09-28gbuild: replace direct gb_STDLIBS use with ...Michael Stahl1-1/+2
... new gb_LinkTarget_add_standard_system_libs Change-Id: Ib2bc843098db3d8c6822b45a3d21724e67f57d69
2012-09-28gbuild: split uwinapi out of gb_STDLIBSMichael Stahl1-0/+1
Change-Id: I53316e0b9369d806197bccb42cf22d3497af43e7
2012-07-02targetted improvement of UNO API includes / usageMichael Meeks1-4/+1
2012-04-08gbuild: "use" vs. "add":Michael Stahl1-2/+2
Naming convention for gbuild methods: - "add" is used for stuff that is logically a part of the target (i.e. not registered at the Module, but defined in the target's makefile) - "use" is used for stuff that is logically a different target (i.e. it is registered at the Module, has it's own makefile, may be in a different module than the target)
2011-12-14Ported configmgr to gbuild.Stephan Bergmann1-0/+81