summaryrefslogtreecommitdiff
path: root/solenv
AgeCommit message (Collapse)Author
2020-10-04Add usage message and reading of the RegistryTor Lillqvist
Change-Id: Iddebcaaaeee234321a71569e80f939e8c324513d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103914 Tested-by: Tor Lillqvist <tml@collabora.com> Reviewed-by: Tor Lillqvist <tml@collabora.com>
2020-10-04Add a tool that will be useful for various tasks if/when we build LO on WSLTor Lillqvist
It is a Win32 program, not a Linux (WSL) one. So far just one function: Convert a full Windows pathname to 8.3 format (if present). WSL does not seem to have that functionality built-in, and doing it through some invocations of cmd.exe or a .bat file from WSL seems very complex. Change-Id: I4c29e2382b0230aacbd22ca6ea0814c8c4d01866 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103912 Tested-by: Jenkins Reviewed-by: Tor Lillqvist <tml@collabora.com>
2020-09-30Fix typosAndrea Gelmini
Change-Id: Ie6146de848b7c5bb7a8edc76a0652c9c623b7024 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103723 Reviewed-by: Julien Nabet <serval2412@yahoo.fr> Tested-by: Jenkins
2020-09-30unused suppressionCaolán McNamara
Change-Id: I8dc74964a6199d320873af20ad00cce3c05ce019 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103699 Tested-by: Jenkins Reviewed-by: Caolán McNamara <caolanm@redhat.com>
2020-09-30use -fpch-codegen rather than -fmodules-codegenLuboš Luňák
The -fmodules-codegen flag has been in Clang for quite a while, but it officially works with PCHs only with Clang11+, and even there's it's better to use the properly named -fpch-codegen. This also fixes a problem with Clang9 having only -fmodules-codegen but not the -fno-* variant, causing the build to break. Change-Id: I9a8c979426f95e8c1f77cbeab1df64390d7243b8 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103677 Tested-by: Jenkins Reviewed-by: Luboš Luňák <l.lunak@collabora.com>
2020-09-30Run gdb in gdb-core-bt.sh with PYTHONWARNINGS=default, tooStephan Bergmann
...same as fb06d5b1784cb8b91ea6d286b3f2baa38fed0b4c "Run gdb with PYTHONWARNINGS=default" Change-Id: If6523e4222f7ef9b9ce72df4a1ab3e039e63154b Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103637 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-09-30bridges: add a Windows Arm64 UNO bridgeJan-Marek Glogowski
Since Microsoft follows the general ARM64 ABI calling conventions, and the SEH exception handling is the same, this result is a mixed port of the gcc3_linux_aarch64 bridge and the refactored x86-64 exception handling. I have no idea, if the complicated 32-bit handling in RaiseInfo() is needed, as the ARM64 trampolines definitly use 64-bit code. But since this is the first working version, I currently don't mind much ;-) There is definitly more potential for refactoring in the whole bridges directory... Change-Id: I9782a2e99c0231cdd1286af156ad312229eccf39 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103642 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-28upload libmwaw 0.3.17David Tardon
Change-Id: I24c6c5a5d93a76a9fcc2213cd48beb8e5a5ca479 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103519 Tested-by: Jenkins Reviewed-by: David Tardon <dtardon@redhat.com>
2020-09-27upload libwps 0.4.12David Tardon
Change-Id: Ib787098b98f68185c1b3f6b414efbec36cad02dd Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102332 Tested-by: David Tardon <dtardon@redhat.com> Reviewed-by: David Tardon <dtardon@redhat.com>
2020-09-25Adapt PythonTest on macOS to PRE-/POSTGDBTRACEStephan Bergmann
Change-Id: Ie23f2fc2e588721ab87e35f52f306e342a5ab246 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103368 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-09-25Run gdb with PYTHONWARNINGS=defaultStephan Bergmann
Otherwise, --enable-werror (setting PYTHONWARNINGS=error) would cause Cppunit-/PythonTest with CPPUNITTRACE='gdb --args' on Linux to print lots of messages like > Python Exception <class 'DeprecationWarning'> the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses: > gdb: warning: > Could not load the Python gdb module from `/usr/share/gdb/python'. > Limited Python support is available from the _gdb module. > Suggest passing --data-directory=/path/to/gdb/data-directory. and > Traceback (most recent call last): > File "instdir/program/python.bin-gdb.py", line 48, in <module> > import gdb > File "/usr/share/gdb/python/gdb/__init__.py", line 23, in <module> > from imp import reload > File "/usr/lib64/python3.8/imp.py", line 31, in <module> > warnings.warn("the imp module is deprecated in favour of importlib; " DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses Change-Id: Id85b2ee6d3cfaeaf91659bfb649a3cb78c707447 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103349 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-09-24Use -flto=thin in gb_LTOFLAGS for Apple's Clang (for macOS and iOS)Tor Lillqvist
Don't add any LTO flags into $CC and $CXX as we don't do that for other platforms either. But maybe we should? Currently, with the separate gb_LTOFLAGS, we have to handle each external project separately to make it build with LTO. Change-Id: I9761426585ebdfd976c74168218bd26bcc0e8517 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103351 Tested-by: Jenkins Reviewed-by: Tor Lillqvist <tml@collabora.com>
2020-09-24PythonTest CPPUNITTRACE='gdb --args' needs to tunnel setting LD_LIBRARY_PATHStephan Bergmann
...so that it doesn't affect gdb itself, just like CppunitTest already did. Otherwise, e.g. make PythonTest_sc_python CPPUNITTRACE='gdb --args' in a Linux ASan and --enable-python=fully-internal build on Fedora 32 would fail with > gdb: symbol lookup error: instdir/program/libpython3.8.so.1.0: undefined symbol: __asan_option_detect_stack_use_after_return as /usr/bin/gdb would try to use LO's instdir/program/libpython3.8.so.1.0 instead of /usr/lib64/libpython3.8.so.1.0. So, at least on Linux, the gb_PythonTest_PRECOMMAND settings are now passed into the test process either directly upfront (if gb_PythonTest_GDBTRACE is not set) or tunneled past gdb via gb_PythonTest_GDBTRACE (if it is set). At least on some platforms, gb_PythonTest_PRECOMMAND has a different value than gb_CppunitTest_CPPTESTPRECOMMAND, so gb_CppunitTest_GDBTRACE would reflect the settings from gb_CppunitTest_CPPTESTPRECOMMAND but not from gb_PythonTest_PRECOMMAND, so introduce a new gb_PythonTest_GDBTRACE (which is to gb_PythonTest_PRECOMMAND what gb_CppunitTest_GDBTRACE is to gb_CppunitTest_CPPTESTPRECOMMAND). macOS with its split gb_CppunitTest_{,PRE,POST}GDBTRACE variables will likely need some work to adopt that to PythonTest, but which is rather orthogonal to this change, so just note that as a TODO for now. Change-Id: I7e6681de638095cb58b44de381248ae7326ce412 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103345 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-09-24Implement DEBUGCPPUNIT as a special case of CPPUNITTRACEStephan Bergmann
...so that gb_CppunitTest_GDBTRACE is only defined in a single place now (in solenv/gbuild/CppunitTest.mk), which should make reasoning about the code simpler Change-Id: I275a20c2fe473e68f4bb08a3fe2691a5809f91a7 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103298 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-09-24Move some settings from just DEBUGCPPUNIT to all gdb CPPUNITTRACEStephan Bergmann
For one, it is probably a good idea to always (a) return the tested process' exit code, and (b) help users without a proper .gdbinit by setting auto-load-safe-path. And for another, this change works towards the goal of implementing DEBUGCPPUNIT as a special case of CPPUNITTRACE, ultimately simplifying the setting of gb_CppunitTest_GDBTRACE. Change-Id: I186434fa8645d8b068c69dbcfedf9b7d6374f99c Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103297 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-09-24Expand the Windows CPPUNITTRACE=TRUE abbreviation in placeStephan Bergmann
...as a means towards defining gb_CppunitTest_GDBTRACE only in a single place (in solenv/gbuild/CppunitTest.mk), which should make reasoning about the code simpler Change-Id: I1a587ee08deb4e969e615b2544265b2ba34bd8af Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103296 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-09-24Fix Python deprecation warningsStephan Bergmann
I noticed these "DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.9 it will stop working" now when running tests with CPPUNITTRACE='gdb --args' on Fedora 32. Change-Id: If263dacb9df5c1fffd2be2418e13e69b96070c77 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103294 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-09-24Only read msi database for msi package formatMike Kaganski
Change-Id: I31f1b1aae3b89a58c33f58a76e32bf171f344012 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103293 Tested-by: Jenkins CollaboraOffice <jenkinscollaboraoffice@gmail.com> Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com> (cherry picked from commit 7e610406a2d063ba5efacb0e186524c2a4ed77a9) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103203 Tested-by: Jenkins
2020-09-23Switch from -Oz to -O2 for iOSTor Lillqvist
Change-Id: Ie672543de3b3a4ab090309010aa9dcf637b01df5
2020-09-23WIN merge CWinClipbImpl into CWinClipboardJan-Marek Glogowski
Get rid of the already minimal pImpl. Change-Id: Ida6fedab6e779b649e546bae2cda5f14fd4090d2 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103211 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-22Move MimeContentTypeFactory into vclJan-Marek Glogowski
The code is just used in vcl from LO's POV. This way we can drop the dtrans directory and get rid of yet an other library. Change-Id: Id77568e63a6fef4af30b49e035a9d76211b127a1 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103210 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-22WIN move dtrans code into vcl/win/dtransJan-Marek Glogowski
There is nothing abstract about either the clipboard or data transfer code in that directory and it's just used on Windows. All other backends implement this code in VCL, so this moves almost all code, except for the common MimeContentTypeFactory, into the vcl Windows backend / vclplug_win. This also drops four DLLs: sysdtrans, dnd, dtrans and ftransl. Change-Id: I7018f50768bf221447b40487cc1f8a8586da33c4 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103209 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-21weld infobarsCaolán McNamara
note: "pushed" status listener case dropped. Doesn't seem to be an expectation for it to something in infobars, and there doesn't seem to be a working case anyway. Change-Id: I7869cc05de9918f0dd70e28b0087205db6c9506c Reviewed-on: https://gerrit.libreoffice.org/c/core/+/101945 Tested-by: Jenkins Reviewed-by: Caolán McNamara <caolanm@redhat.com>
2020-09-21drop unused suppressionCaolán McNamara
Change-Id: I3d3d49a47baf76814a6a4cd1483486dc608b035e Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103105 Tested-by: Jenkins Reviewed-by: Caolán McNamara <caolanm@redhat.com>
2020-09-19drop some unused suppressionsCaolán McNamara
Change-Id: I4fc230216cb739f03e20cb6ab4ec2c53c6ad48c9 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103037 Tested-by: Jenkins Reviewed-by: Caolán McNamara <caolanm@redhat.com>
2020-09-19The config.{guess,sub} in $SRCDIR is good for external projects, tooTor Lillqvist
No need for the older second copies in solenv/gbuild. Change-Id: I088f7d06b0727d1b336e3ba314b5c874d8ce3776 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/103027 Tested-by: Jenkins Reviewed-by: Tor Lillqvist <tml@collabora.com>
2020-09-18drop some unused suppressionsCaolán McNamara
Change-Id: Ie11e2ac56fc8a4f1b10f801824764322052bb124 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102975 Tested-by: Caolán McNamara <caolanm@redhat.com> Reviewed-by: Caolán McNamara <caolanm@redhat.com>
2020-09-18xmloff: remove dead com.sun.star.comp.Draw.XMLSettingsExporterMiklos Vajna
And test com.sun.star.comp.Draw.XMLOasisSettingsExporter instead in JunitTest_xmloff_unoapi. Note that the test code is also dead at the moment, because xmloff/qa/unoapi/xmloff.sce disables the xmloff.Draw.XMLSettingsExporter line, but let's not regress even more in that code. Change-Id: I2152f32fd798b7a7df7086b125e77fe804185157 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102973 Tested-by: Jenkins Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
2020-09-18Resolves tdf#97918 - Individual UNO commands for distribution optionsHeiko Tietze
New UNO commands added, SID_DISTRIBUTE_DLG bend to dropdown, ui removed Menus and toolbars adjusted Change-Id: Ic0a3cc299f745a1a0cd18edead1f410ff57a1f1f Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102272 Tested-by: Jenkins Reviewed-by: Maxim Monastirsky <momonasmon@gmail.com>
2020-09-17Report each value of LO_TEST_LOCALE in localized CppunitTestStephan Bergmann
Change-Id: I7ad091ec163f2324f2b8481e4caa6beb12188ea4 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102896 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-09-17WIN bridges: unify exception handlingJan-Marek Glogowski
This is almost just refactoring, but with classes like type_info_ and __type_info, just following the code became tendious. I tried to come up with better names... and in the end included some minor code changes described below. This patch moves the "common" code for MSVC exception handling into msvc_shared/except.cxx. Still it contains a few small ifdefs, so it doesn't feel like clean separation, but a lot of duplicate code is dropped this way. The "major" code change for amd64 is the drop of the duplicate static RTTInfo object originally used by mscx_getRTTI and mscx_getRTTI_len, by merging of both functions into the single, new get() function to use a single std::find call. Change-Id: Ib07d40e2794cde79156be3324c80ccf21a6aa8ed Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102864 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-16configure + gbuild: handle Windows Arm64Jan-Marek Glogowski
Change-Id: Idfc20c1234d693d6b402158b8bc782bd17cd3f4b Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102850 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-16Turn OUStringLiteral into a consteval'ed, static-refcound rtl_uStringStephan Bergmann
...from which an OUString can cheaply be instantiated. This is the OUString equivalent of 4b9e440c51be3e40326bc90c33ae69885bfb51e4 "Turn OStringLiteral into a consteval'ed, static-refcound rtl_String". Most remarks about that commit apply here too (this commit is just substantially bigger and a bit more complicated because there were so much more uses of OUStringLiteral than of OStringLiteral): The one downside is that OUStringLiteral now needs to be a template abstracting over the string length. But any uses for which that is a problem (e.g., as the element type of a container that would no longer be homogeneous, or in the signature of a function that shall not be turned into a template for one reason or another) can be replaced with std::u16string_view, without loss of efficiency compared to the original OUStringLiteral, and without loss of expressivity. The new OUStringLiteral ctor code would probably not be very efficient if it were ever executed at runtime, but it is intended to be only executed at compile time. Where available, C++20 "consteval" is used to statically ensure that. The intended use of the new OUStringLiteral is in all cases where an object that shall itself not be an OUString (e.g., because it shall be a global static variable for which the OUString ctor/dtor would be detrimental at library load/unload) must be converted to an OUString instance in at least one place. Other string literal abstractions could use std::u16string_view (or just plain char16_t const[N]), but interestingly OUStringLiteral might be more efficient than constexpr std::u16string_view even for such cases, as it should not need any relocations at library load time. For now, no existing uses of OUStringLiteral have been changed to some other abstraction (unless technically necessary as discussed above), and no additional places that would benefit from OUStringLiteral have been changed to use it. Global constexpr OUStringLiteral variables defined in an included file would be somewhat suboptimal, as each translation unit that uses them would create its own, unshared instance. The envisioned solution is to turn them into static data members of some class (and there may be a loplugin coming to find and fix affected places). Another approach that has been taken here in a few cases where such variables were only used in one .cxx anyway is to move their definitions from the .hxx into that one .cxx (in turn causing some files to become empty and get removed completely)---which also silenced some GCC -Werror=unused-variable if a variable from a .hxx was not used in some .cxx including it. To keep individual commits reasonably manageable, some consumers of OUStringLiteral in rtl/ustrbuf.hxx and rtl/ustring.hxx are left in a somewhat odd state for now, where they don't take advantage of OUStringLiteral's equivalence to rtl_uString, but just keep extracting its contents and copy it elsewhere. In follow-up commits, those consumers should be changed appropriately, making them treat OUStringLiteral like an rtl_uString or dropping the OUStringLiteral overload in favor of an existing (and cheap to use now) OUString overload, etc. In a similar vein, comparison operators between OUString and std::u16string_view have been added to the existing plethora of comparison operator overloads. It would be nice to eventually consolidate them, esp. with the overloads taking OUStringLiteral and/or char16_t const[N] string literals, but that appears tricky to get right without introducing new ambiguities. Also, a handful of places across the code base use comparisons between OUString and OUStringNumber, which are now ambiguous (converting the OUStringNumber to either OUString or std::u16string_view). For simplicity, those few places have manually been fixed for now by adding explicit conversion to std::u16string_view. Also some compilerplugins code needed to be adapted, and some of the compilerplugins/test cases have become irrelevant (and have been removed), as the tested code would no longer compile in the first place. sal/qa/rtl/strings/test_oustring_concat.cxx documents a workaround for GCC bug <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96878> "Failed class template argument deduction in unevaluated, parenthesized context". That place, as well as uses of OUStringLiteral in extensions/source/abpilot/fieldmappingimpl.cxx and i18npool/source/localedata/localedata.cxx, which have been replaced with OUString::Concat (and which is arguably a better choice, anyway), also caused failures with at least Clang 5.0.2 (but would not have caused failures with at least recent Clang 12 trunk, so appear to be bugs in Clang that have meanwhile been fixed). Change-Id: I34174462a28f2000cfeb2d219ffd533a767920b8 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102222 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-09-16external: update pdfium to 4260Miklos Vajna
Change-Id: I1b6c7e9991b2e35921f7f849380d940c6662b174 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102787 Tested-by: Jenkins Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
2020-09-15Don't use argparse to open control_fileMike Kaganski
Use idiomatic 'with' instead This avoids the warnings: Exception ignored in: <_io.FileIO name='C:/lo/src/core/postprocess/packimages/image-sort.lst' mode='rb' closefd=True> ResourceWarning: unclosed file <_io.TextIOWrapper name='C:/lo/src/core/postprocess/packimages/image-sort.lst' mode='r' encoding='cp1251'> Change-Id: I1cf8248cdab8dd9fd585545c64de2aebcbfe5365 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102647 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2020-09-15WIN add and apply default msbuild platform+configJan-Marek Glogowski
Adds three Windows gb_* variables: - gb_MSBUILD_CONFIG_AND_PLATFORM can be passed as msbuild flags - gb_MSBUILD_PLATFORM maps debug / release settings - gb_MSBUILD_CONFIG maps the CPUTYPE to the default msbuild names and converts the users in external projects. Change-Id: Ie9b817721180d78d104db11c44241e4b3e46bba9 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102701 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-14drop some unused UI suppresionsCaolán McNamara
Change-Id: Ib175531149338cddd27b9959a9c8fc287392d8b0 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102658 Tested-by: Jenkins Reviewed-by: Caolán McNamara <caolanm@redhat.com>
2020-09-14drop some unused UI suppresionsCaolán McNamara
Change-Id: I65d2398d7b5d8011e1f079b6a40dfd5ca579d0e7 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102657 Tested-by: Jenkins Reviewed-by: Caolán McNamara <caolanm@redhat.com>
2020-09-13fix attachnamedialog mnemonicsCaolán McNamara
Change-Id: Ibdc7e7432d7ce48473e16298fdb8eddea5241938 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102541 Tested-by: Jenkins Reviewed-by: Caolán McNamara <caolanm@redhat.com>
2020-09-13fix alreadyexistsdialog mnemonicsCaolán McNamara
Change-Id: Id9c326d28cf7049e692108cdeccef6714c142e2d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102540 Tested-by: Jenkins Reviewed-by: Caolán McNamara <caolanm@redhat.com>
2020-09-12drop some unused suppressionsCaolán McNamara
Change-Id: I44422004b8ad2b6e848f6ed5b7cca649fbfdf5ae Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102522 Tested-by: Jenkins Reviewed-by: Caolán McNamara <caolanm@redhat.com>
2020-09-12Try fix multiple assignments of gidsMike Kaganski
************************************************ WARNING: multiple assignments of gids: ************************************************ GID: gid_Dir_Shlxthdl Assignments: 2 Change-Id: I4c2f53d8b996fc750465219f320fd8538a4d23f4 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102494 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2020-09-12Flatpack: update to liborcus 0.16.0Julien Nabet
Change-Id: I9268a254cf74c3effa7852cd0936399d8c28aa6d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102509 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-09-12Replace remaining uses of sal_CharJulien Nabet
+ remove sal_Char check on compilerplugins Change-Id: I0f7da14e620f0c3d031d038aa8345ba4080fb3e9 Change-Id: Ia6dba4f27b47bc9e0c89159182ad80a5aee17166 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102499 Tested-by: Jenkins Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
2020-09-11cross-build: fix Java NI linkingJan-Marek Glogowski
LibreOffice has a JNI component on Windows and Linux, the officebean. Therefore we need a host JDK for linkage to the jawt, and a build JDK to compile the Java code. Change-Id: I4138628ab3ea2ef5900a5b4e9281050ae84e4eb5 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102483 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-11WIN cross: fix gpg-related library buildsJan-Marek Glogowski
Cross compiling these libraries requires to supply the cross- compiler via the CC_FOR_BUILD environment variable. Since we have to use the gcc-wrappers, we now need two different invocations with different inclues and libraries, but just have fixed environment variables. Also, the CC_FOR_BUILD clashes with LO's own variant, but that is easy to fix. So this change includes: - gcc-wrappers: new option --wrapper-env-prefix to add a prefix to the environment variable names - gcc-wrappers: new option --wrapper-print-cmdline to dump the real command called, when a verbose build is executed - gcc-wrappers: default to exe, if the output has no extension - unify build flags for gpg related libraries Change-Id: I4e6a6ba3c6e09237c8ffefa40ce61131290a3852 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102482 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-11Fix the minimal build-tools targetJan-Marek Glogowski
The revert commits change the build-tools target for a DESKTOP build to build the complete LO. This restores the original, minimal one and also adds a whitelist of allowd build types. OpenCL needs a configure switch, as it's status is also stored in a config header, so preventing the build is not enough. This also reverts: - commit 802161a505272732566210e9ebbd8fe1b23fb86d - commit 02d931a59e2966d0c2736db8dee7be3e3dcd6bae Change-Id: Ibfcb0c54e72da1b7c2e63c082ea6586520a787fa Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102480 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-11WIN drop --enable-64bit to select Windows targetJan-Marek Glogowski
This changes the Windows build to use the default configure switch to select the target / host of the compiled binaries to get the possibility to cross compile on Windows the "default" way. Note that selecting i686-pc-cygwin on x86_64 doesn't do a cross- compilation, as no special build tools are needed, because x86_64 can run x86 binaries just fine. A consequence of the change is the default target host, which is now the same then the build system, instead of the previous x86 default. Change-Id: I5584f34f665573ebac40d5d7753d96addeb84dbb Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102479 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-11image-sort: add --quiet option for build-toolsJan-Marek Glogowski
Otherwise you'll get many warnings for missing images, because the cross-toolset target just builds some small part of LO. This also converts the program to use argparse. Change-Id: I22adda23ab3a25bced871a87d38373543cd5ae72 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102478 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
2020-09-11Use { ... } for grouping that does not need a sub-shellStephan Bergmann
...in case that makes ever so small a difference, esp. on Windows (where spawning processes is known to be expensinve; but note that at least Bash seems to not spawn a sub-shell anyway when what is enclosed in ( ... ) is just a simple single process, which is commonly the case for these cppunittester invocations) Change-Id: Ie9200270743754e02fbfdb2b17239e9873031dab Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102407 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
generated by cgit (git 2.34.1) at 2024-12-29 19:21:28 +0000