Age | Commit message (Collapse) | Author |
|
And add the missing dependency of Executable_gengal on
Package_svx_gengal, so the actual executable script is
created in instdir_for_build for the cross-toolset.
Change-Id: I98ea1d58273c871f0a3b804a93970eedfb7f8908
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/108108
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
|
|
The check had been introduced with 16c0807d75cfd9ecbca9c703ed0eadda80529aab
"configure: reject Apple JDK", but with 7db048f62929a9d267b63db3a6ea2b58b47ec757
"Manually select JDK outside /Library/Java/JavaVirtualMachines on macOS" it
works fine to configure --with-jdk-home= a (non-Apple) JDK installed outside
/Library/Java/JavaVirtualMachines. If anybody thinks a check to reject Apple
JDK would still be useful, and knows a reliable way to detect it, feel free to
add back a fixed check.
Change-Id: I18910d992e3d1fc6fd8fc4b9d522aec0cce3e652
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/108144
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
|
|
Change-Id: I21b8055fc97d8dfb8429e7dafa1a3982c3b7499b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/108122
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: If642e9ec03a092375acb9b0624e62eec33ebd716
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/108063
Tested-by: Caolán McNamara <caolanm@redhat.com>
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
|
|
testing for existance of config_host.mk is flawed/doesn't catch all kind
of errors and thus gives false "OK" for incremental builds and not even for
builds after make clean
see also d691b46e52d173cf945130df01bd35b5c4c0f539
Change-Id: I153f585c3a7870ef4a87848eccf7abd7d66987e2
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/107970
Tested-by: Jenkins
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
|
|
Build doesn't fail after just a make clean, but do fail with a
completely fresh checkout
regression from https://gerrit.libreoffice.org/c/core/+/107655
Change-Id: Id05f747548729449fbda6306fc27e35377b80569
|
|
Change-Id: I7b13905840616fe84a1b9d23161c4c349d2e7f0c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/107778
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: Ief4322005fb9087c00f767dcd50a59f2ccbc8a82
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/107744
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Not having settings directly stored in .vscode directory in the
repository/having the files ignored there is a problem when you build in
a separate builddirectory and you regularly do a full reset of your
sourcedir using "git clean -fdx" and similar. If you had any
folder-settings, you'd lose them that way.
VS Code doesn't really have a mechanism to include and then extend
repository defaults, but it has three different tiers where settings are
pulled from: folder, workspace and user
For LibreOffice core repository there are no folder settings as our
.vscode is not populated (or at least it is not stable), a user can of
course place a settings.json or other configuration files in their
checkout, just with the "git clean" problem mentioned above.
This patch adds a workspace configuration - that file can be stored
anywhere and instead references the folders to use as configuration
items. If you want to add your own launch configuration or tasks: you
can just store it on your desktop, and can completely wipe out your
builddir as well as prune your srcdir - if you reuse the same paths for
your next build, you can simply reopen that workspace file and have all
your settings applied.
Having it part of the core repository and created by configure from the
template is thus just a convenience thing - it has a launch-in-debugger
rule and settings for code search/browsing that should be all that's
needed/all that's specific to LibreOffice at least.
Change-Id: I8625d83d0c30c2668b99ec672c651c3d35258ca5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/107655
Reviewed-by: Ilmari Lauhakangas <ilmari.lauhakangas@libreoffice.org>
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
Tested-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
|
|
Change-Id: Ib524049405215ac96ad51cbdc7f527f29c4f83f6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/107693
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
|
|
...since <https://github.com/llvm/llvm-project/commit/
6627a3c2873fdf7ccba1a1573371079be48b36e8> "[c++2b] Add option -std=c++2b to
enable support for potential C++2b features."
Change-Id: I56b689c740c4269fa5ee29976ed8b0c17a04e6a1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/107175
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
|
|
The SDK's <https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Java/
Transparent_Use_of_Office_UNO_Components> on all platforms included the Windows-
specific unowinreg.dll in generated jars (so that those jars, when distributed
to a Windows environment, would find a LO installation by inspecting the Windows
registry). That unowinreg.dll was originally built as a 32-bit DLL (though when
building a 64-bit Windows LO, it happened to be built as a 64-bit DLL). For
non-Windows LO builds, it could either be built locally with a MinGW toolchain
(--enable-build-unowinreg) or downloaded from dev-www.libreoffice.org.
However, that had various issues:
For one, unowinreg.dll was not necessarily available in a distributed jar as a
64-bit DLL for use with a 64-bit JRE on Windows. (Theoretically, running such a
jar with a 32-bit JRE to access a 64-bit LO installation's URE jars could have
worked. But practically, those URE jars in turn require native DLLs, which
would then not have been available as 32-bit DLLs for use in the 32-bit JRE.)
For another, at least the unowinreg.dll resulting from --enable-build-unowinreg
on Fedora 33 would have had a dependency on libgcc_s_dw2-1.dll that would
generally not have been available in a target Windows environment.
There appears to be no pure Java way to read the Windows registry, but instead
of using a native code DLL for that, it appears to work just as well to call out
to reg.exe and parse its output.
This removes the --enable-build-unowinreg and --with-mingw-cross-compiler
configuration options. (The sole use of the MinGW toolchain in LO was for
building unowinreg.dll.)
Change-Id: I3283ea38c884d3221a205e5ab6ec99a2691ef474
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/107140
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
Tested-by: Jenkins
|
|
Change-Id: Iab2b984ca3baafd8c975560f9625ead097abcc56
|
|
Change-Id: I342eced74e6e3f264f48ebe508b6931fc718cab2
|
|
For cases where you just want "make test-install" to construct an app
bundle that you will manipulate and then sign separately.
Change-Id: Iad805618f74ec783ebc013a664f928511b388383
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/106185
Tested-by: Jenkins CollaboraOffice <jenkinscollaboraoffice@gmail.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/106260
Tested-by: Jenkins
|
|
The main idea is to get rid of the "unset MAKEFLAGS". AFAI can
see, the whole CPU stuff isn't used anymore. So we can drop the
whole FB_CPU_ARG handling. Since LO doesn't use any of make's
implicit rules, the build breaks, but luckily it just requires a
single rule for the btyacc build - just a Firebuild build tool.
Then there is the whole broken handling of LIBTOMMATH and
LIBATOMIC_OPS already in LO's configure.ac. I don't know if any
internal build of Firebird with these as system libs would work.
I guess people either have a system Firebird or also build with
internal libtommath and libatomic_ops. This fixes just the
obvious errors. I didn't try to build it, so there might still
be typos (TBH I thought hard about just dropping the system
build of these libraries, after seeing the broken configure.ac).
And I'm not sure our / the system boost preprocessor library is
ever used over the Firebird-internal copy. It also looks like
it's also just used in an other build tool and nothing of the
Firebird DB itself depends on it.
Then there is the movement of the install_name_tool / otool
patching on MacOS from the patch into the ExternalProject to
further shrink the patches, as the build doesn't depend on it.
This also introduces a different debug build mode for the
gcc-/g++-wrapper: MSVC_USE_INDIVIDUAL_PDBS.
It uses -Fd to write a separate PDB per output file instead of
using -FS to use sync writes to a single PDB, which might work
around the PDB access failures seen by Jenkins for linking
executables. In theory it's also faster and should work with all
the other wrapper users, but I don't want to open that can of
additional build errors (yet), for eventually marginal gains.
Change-Id: I8d4c5d2f17def9e840a67ef1004787e8baaffa83
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105902
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
|
|
Add glyphs U+F030-U+F039 (in Private Use Area) as references to
U+0030-U+0039 (digits 0-9), because font Symbol.ttf has these glyphs and
they are necessary for compatibility with MS Office file formats.
Change-Id: If66ac3ee6fda9c161b36fd6eb459c99646e87541
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105997
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
Tested-by: Jenkins
|
|
Possibly it didn't work when cross-compiling back when that
hard-coding was added.
Change-Id: I763d26ae1922907265636ba0be0757700bfe2a8b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/106058
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: Icd30133588f3cffb5de41303dc03cb325c20fe83
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105788
Tested-by: Jenkins CollaboraOffice <jenkinscollaboraoffice@gmail.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/106044
Tested-by: Jenkins
|
|
Also made it necessary to adapt two places in libcdr and libebook
that used UBool TRUE which is gone now to use standard true
instead.
Change-Id: I1c1df3030f8b883bec6045756907ee0b78060382
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105964
Tested-by: Jenkins
Reviewed-by: Eike Rathke <erack@redhat.com>
|
|
Autoconf 2.70 beta autoupdate says:
> configure.ac:6540: warning: The preprocessor macro `STDC_HEADERS' is obsolete.
> Except in unusual embedded environments, you can safely include all
> ISO C90 headers unconditionally.
Change-Id: I3d7e96ccd1683f51d47250c013cb0b6ea11d70ab
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105554
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
|
|
The "AC_LINK_FILES" is replaced by "AC_CONFIG_LINKS"
Change-Id: I9c82d3f54cf78f08489453389d4e5070529a4f69
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105423
Tested-by: Jenkins
Reviewed-by: Henry Castro <hcastro@collabora.com>
|
|
Change-Id: Idcea17d2418a2e847a5713293d7a225ed86bd305
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105435
Tested-by: Jenkins
Reviewed-by: Michael Stahl <michael.stahl@cib.de>
|
|
...see <http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commit;
h=cc2c99e90bd58b3d5022581eada72ca10df99bb0> "Move AC_MSG_* into M4sh" stating
> (AC_FD_MSG, AC_FD_LOG): Be AU_ALIAS'es of...
> (AS_MESSAGE_FD, AS_MESSAGE_LOG_FD): new.
and which is present in branch-2.59 matching our AC_PREREQ([2.59]) baseline.
(This change is suggested by running autoupdate from the current Autoconf 2.69
suite.)
Change-Id: If5826489b3416b4029b9c922f9415576978306b9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105393
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
|
|
Change-Id: I319e0b3aefa721f2503494783af6d73470f592a2
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105271
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
I can't think of any reason to use such a pointlessly seemingly
specific value. Let's just use the round number 100, as for source
code (see TEMPLATE.SOURCECODE.HEADER).
Change-Id: If61af553f8142dfcba31e775d050d167f89c010b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105235
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I6e9b61da73509f40575640209082defc34bcbf63
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105230
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Restore the old CFLAGS (etc) as soon as possible. Always use the same
variable names for the saved values.
Change-Id: I523bbf66ec5400d24993b7e11e444bb63d61751e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105130
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I3a05def839c14d59545c4891418577ed36f2b8cb
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105099
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
INCLUDE is not exported from WSL to Win32 programs without including
it in the list of environment variable names in the WSLENV environment
variable, and I think we want to minimize the number that need to be
mentioned there.
Should not affect Cygwin builds.
Change-Id: I0af480873badac446305e396b69eec360eb8a270
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105098
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Originally disabled for the build-tools to get rid of an other
potential build failure while implementing the cross build on
Windows for the Windows Arm64 build.
Change-Id: I720d0812de26ddb1f71a14db708595babbefe84c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105035
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
|
|
So make it more obvious that disabling pdfium is not too secure.
Change-Id: Ie67d2ea76bfbcca928927f974be46ae708472cf8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104809
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
Tested-by: Jenkins
|
|
(Using the Unix form doesn't hurt on Cygwin either.)
Change-Id: I43c6c66feabadd9dec2287e440e5748db264fc6c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104788
Tested-by: Jenkins
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Part of work in progress. Committing in smaller bits to make potential
bisecting easier.
Change-Id: I604bdd993288369051b3365014be54090f987559
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104789
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I9b68eeca92b9ee5722884384a740bfac85a26bed
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104784
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
It is expected that some of the Registry entries that we try to read
do not exist.
Change-Id: I48b40cd6a3cf0961abd7259ad02da18c2ee65601
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104787
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I4a9c2122b8d0511311a6101c2eeda6e86220b1fc
|
|
Change-Id: Ib785ba0b22a555136a64c97c50aa2c17a75f6c03
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104774
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I6ae91b093eaad3b59ca939045ba0d045377f3978
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104773
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: If0f09dab3a7eb0849aeabcb52bfee39c3a71b719
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104769
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I8cb2d6b6170d427c0f622b1377b6fd21e3b90383
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104770
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Handle also Windows pathnames passed to it in mixed format, and Unix
pathnames for Windows files (starting with /mnt/).
Change-Id: I07a01b8680a6ed203e9fe44c37822e0490c3f296
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104771
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: Ie006ed818e91e5cd4869fabb1b8fa9bcf0da943f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104768
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I7ae3c86fc42d5232b168a55d1993ad373075b773
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104765
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Use the PROGRAMFILESX86 environment variable that autogen.sh exports.
Use the $formatted_path_unix return value from PathFormat.
Change-Id: Ifa2c05e57248a9c05d60ebf7b93fbdc1c1e59b1b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104764
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I0f5324528b87ca76c602cb788e9c8648e61188ca
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104763
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
This is just one step towards the goal of being able to build for
Windows on WSL (instead of Cygwin).
Unlike Cygwin, WSL can not use Windows pathnames at all. So to be able
to build for Windows on WSL, we will need to be much more careful in
keeping track of which pathnames are in Windows format and which are
in Unix format. Add a second return value for PathFormat that on WSL
is in Unix format.
Like in c6d8e4b36f9575267244119c0a7e6a2275168625, also add a simple
"unit test" (just for visual inspection) of the new functionality.
Change-Id: Ief4584243227677d0705de2c83e2a0bf54eac0a3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104761
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I095f5169c0e9969531995ff0b533642aeaae9135
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104759
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I093ee0a6cb6483a8891dd9ed4576da0108303c66
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104586
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: If21b074c7a9f5da45101866ee071967bdc668af9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104561
Tested-by: Jenkins
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
|