sometimes the xml security tests will leave these lying around,
and we don't want them committed
Change-Id: I703aee4cb5b3e5c41449f744f1628c09be70d077
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162070
Tested-by: Jenkins
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
Some VS Code extensions create directories with this prefix.
Change-Id: Ie4a96a276970327d8da39bffd51eaf137e4163bf
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146728
Tested-by: Ilmari Lauhakangas <ilmari.lauhakangas@libreoffice.org>
Reviewed-by: Ilmari Lauhakangas <ilmari.lauhakangas@libreoffice.org>
(recently introduced in c78b49ec13 "don't specify
entitlements that are not used (sdremote w/o bluetooth)")
Change-Id: Ied7db52d891e92224bc2be0ad1277f40e5d80b3c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/136752
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
Qt Creator 7 switched to using Clangd as the
default backend for the code model. [1]
After upgrading, `.qtc_clangd/compile_command.json`
started showing up.
[1] https://www.qt.io/blog/qt-creator-7-released
Change-Id: I3cf30f1ef2873523d76c15c39d2d24c6227f8017
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/132290
Tested-by: Jenkins
Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
This is a hack, because make has no way to serialize processing
of a target (just .NOTPARALLEL for the whole Makefile).
It uses the lockfile tool / liblockfile 1.17. Since that polls
the file, I adjusted the poll timeout to 5s max, because I found
the 60s wait much too long. Guess even 1s would be ok...
Since it's just a small build tool, I simply copied and patched
its source, instead of creating an external project. And there
is --with-system-lockfile=... to use an external binary instead.
Change-Id: I16bc4579a273dcf1aac811ae4723ca325a0b9eba
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126152
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
Re-cat's the build / cross-toolset warnings file at the end of
the host configure run and keeps them.
Change-Id: If46fa3660dbd04cd5a23a4d9cd79fd19067dcfbe
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/116437
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
Generating *.pro.user files is not ideal; they're
supposed to hold user-specific settings for a project,
and thus also to persist manual changes made by the user
after initial import of the project.
Generate *.pro.shared files instead which are
meant to be used to share project settings. [1]
This just changes the file name of the generated
file for now, but leaves the content the same.
The result for the initial loading of the project from
a '*.pro' file is basically still the same from a user
perspective:
A new kit 'Replacement for "Desktop"' is generated on
the fly which contains the build and run settings
specified in the corresponding '*.pro.shared' file.
By using the '*.pro.shared' files, user-specific settings
made after initial import will no longer
be overwritten by running 'make qtcreator-ide-integration'
again, since the '*.pro.user' files are left as they are.
The '*.pro.shared' files generated here still contain
information specific to the local setup (like file paths).
For some more background on LO's Qt Creator IDE integration,
s. dev mailing list thread "Added some information about
Qt Creator IDE integration to the wiki" [2].
[1] https://doc.qt.io/qtcreator/creator-sharing-project-settings.html
[2] https://lists.freedesktop.org/archives/libreoffice/2021-February/thread.html#86800
Change-Id: Ia187bcbffe5297a1cdf6bfeaaabf7867003195e0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/111474
Tested-by: Jenkins
Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
...that had been added with ea9915a550 "hush more
kinds of file types" for unclear reason
Change-Id: I3fef3df57480c0d2de384d0a60986d83b6a3e3c4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/108453
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
...and expand it to precisely match the three .dwo files, like had already been
done for the corresponding .o files. (Those .dwo files are generated when
-gsplit-dwarf is added to CLANGCXXFLAGS when manually overriding CLANGDEBUG=1.)
Change-Id: Ib6f1c505c754d54201273f08f987a9451af75bc4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/100855
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
...generated since 88453fd13a "Enable debugging of
a hardened process on macOS"
Change-Id: I061b3673855d6e44f0fbf805f8cda1a9ee6f2196
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/93431
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
Change-Id: If00a4eed997acf2eb7783915e41c61c7651232d6
Reviewed-on: https://gerrit.libreoffice.org/73698
Tested-by: Jenkins
Reviewed-by: Muhammet Kara <muhammet.kara@collabora.com>
...after fd34a19b4d "Seems that we don't need the
com.apple.application-identifier after all" dropped the last @...@ replacement
there
Change-Id: Id6f4d1065b28be12e5d727bab553daa17fc4dfcb
Reviewed-on: https://gerrit.libreoffice.org/65275
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
This file is generated by "make vim-ide-integration"
Change-Id: I9355bc36b2a654efd6183b268662b10b224f2117
Reviewed-on: https://gerrit.libreoffice.org/39108
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
these files are generated by make vs2015-ide-integration.
Change-Id: Iaae5931289bd2f27415c401b6ac253d43dc39007
Reviewed-on: https://gerrit.libreoffice.org/36073
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>
Moved common macros to CustomTarget_Lo_Xcconfig.mk
to simplify each real target
added link to workdir/ios (needed by xcodeproj)
moved creation of configuration files to LO_Xcconfig, since
they are identical for all ios projects
central part of moving non git files to workdir completed
changed relative path in project.pbxproj to be <project> instead of <group>
Change-Id: I6be51f4d8a07ea7da08c0e5f1458fccfc3831a1e
Reviewed-on: https://gerrit.libreoffice.org/34223
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: jan iversen <jani@libreoffice.org>
Rule for ctags: Sublime generated(or otherwise) ctags look like
sc/abc/xyz/tags. The present rule cannot look after tags which
are more than 1 directory deep. Hence this change.
Other rules added : Jetbrains Clion, cscope, sublime text specific
Change-Id: I1dbbe4904f3d15bbf198cd372591b464efb3896a
Reviewed-on: https://gerrit.libreoffice.org/31874
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Jaskaran singh <jvsg1303@gmail.com>
officeotron is a OOXML documents validator which can be used for
verification of export files in tests. Previously it was possible
to use it only from external repository with extra build steps.
Change-Id: Iae6ec3695fdfaf738d180405047ff04b2024c906
Reviewed-on: https://gerrit.libreoffice.org/27388
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
Run bffvalidator also from Linux, reportedly works from wine 1.9
upwards. Wraps stuff in a shell for path name conversion.
Change-Id: I3093b10bbbf89aaff97f63485b8ccadb417b3561
Reviewed-on: https://gerrit.libreoffice.org/26784
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
Tested-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
Set up the toolchain to create sources and javadocs artifacts in
addition to JARs created during the build. Use Buck build tool for
that: [1]. This is a fork of Google's build tool Blaze, created by
Xooglers at Facebook. This build tool (like Blaze itself) uses
Python to write build files.
Add needed tools and build files to install LibreOffice API artifacts
to local Maven repository or deploy them to Maven Central.
To build all needed artifacts LibreOffice must be built regularly
with GNU make first. To build the rest of the API (sources and
javadocs):
$> buck build api
To replace version number with upcoming release version:
$> solenv/bin/version.py 5.1.0
To install the API to local Maven repository:
$> buck build api_install
To deploy the API to Maven Central:
$> buck build api_deploy
Detailed documentation is added to document the prerequisites and
the workflow to upload LibreOffice API to Maven Central.
* [1] https://buckbuild.com
Change-Id: Ibdd552a01110836703bc069abe829b9921491cac
Reviewed-on: https://gerrit.libreoffice.org/20343
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
Tested-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
This patch generated a setting file for per module. When imported the
eclipsesettingfile.xml, underlined include lines are clearing up.
Setting file includes included file paths for per module and provides
correct build. .project file generator deleted because eclipse
is creating .project file and overriding it.
This adds a new property to the parser that stores each module.
Change-Id: Ia10bb37c7c3fdb444a5b79ddf502b962e8ee5736
Signed-off-by: Gulsah Kose <gulsah.1004@gmail.com>
With `make vs2013-ide-integration` dozens of VS specific
project and solution files are generated. These add noise
and time to `git status` and make it harder to locate
new files.
Restored the exclusion of .vcxproj and .sln files and
added windows/ directory to the ignore list.
Change-Id: I64abe395824503a5eda25d70d7467ba3fa4e4aa8
Reviewed-on: https://gerrit.libreoffice.org/19972
Reviewed-by: Tor Lillqvist <tml@collabora.com>
Tested-by: Tor Lillqvist <tml@collabora.com>
The intent is not that this will grow to anything that one could build
LibreOffice in. Some source files that one often needs to set
breakpoints in might be added.
This is in no way related to the "make vs2013-ide-integration" thing.
Change-Id: I9cb3007af1dd9bff653584ad3f82f917649ce8c0
tools/rtti.hxx removed
completed the interface of some Sdr.* Items
and removed pseudo items
Change-Id: I0cdcd01494be35b97a27d5985aa908affa96048a
Reviewed-on: https://gerrit.libreoffice.org/19837
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Oliver Specht <oliver.specht@cib.de>
move preparation tasks (creating assets/processing files) from the
makefile into the gradle script
This allows much easier integration into android-studio (just open
android/source with android studio after running make to compile the
native library)
Change-Id: I9a9d6832797c24a7e195a1c7954cd6d20f5a8496
...this is a follow-up to efad388f75 "Clean up
Make SHELL handling," which broke out-of-tree builds.
There appears to be no good reason at all to fiddle with Make's own behavior of
determining its SHELL variable (which defaults to /bin/sh and can be overridden
via a SHELL=... command line argument when invoking Make). The SHELL_BASH
fiddling in configure.ac and Makefile.in was probably cargo cult carried along
ever since 815f157c05 "CWS-TOOLING: integrate CWS
configuretoplevel," in a time when the OOo build system still defaulted to tcsh.
Change-Id: If906164abb6aae649ce8088d945a40213deed361
Reviewed-on: https://gerrit.libreoffice.org/19093
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
Tested-by: Stephan Bergmann <sbergman@redhat.com>
* In configure.ac, honour a preset SHELL_BASH when determining SHELL_BASH (so it
can be passed in via autogen.input).
* For both toplevel "make" and per-module "cd $module && make", consistenly use
the SHELL_BASH determined in configure.ac as the Make SHELL. (By moving the
setting to a new, common soleng/gbuild/shell.mk. This also exports SHELL as
an environment variable to sub-processes now; this exporting can probably be
reverted if it is not what is actually wanted---but note that this exporting
of an environment variable to sub-processes is unrelated to how nested
invocations of $(MAKE) obtain their Make SHELL setting, see below.)
* Remove the gb_SHELL override feature from solenv/gbuild/gbuild.mk; for one, it
is unclear how it was intended to interact with setting SHELL=@SHELL_BASH@ in
the toplevel Makefile; for another, overriding SHELL can be done globally via
setting SHELL_BASH in autogen.input now.
* Make treats SHELL specially, in that it never uses the SHELL environment
variable to determine the Make SHELL variable. Instead, if this Make
invocation, or any outer Make invocation it is nested in via calls of $(MAKE),
was called with a SHELL=... command line argument, then that value is used
(and otherwise the default is hardwired as /bin/sh). So, when calling nested
invocations of $(MAKE) from the toplevel Makefile, pass down the current SHELL
value via a SHELL=... command line argument via GMAKE_OPTIONS. (And further
nested invocations of $(MAKE) will then automatically inherit the SHELL value
given on the outer invocation's command line.)
Change-Id: I67fa1b88e4e90d09456c1fcad2d082fdce3c019b
Added more Xcode specific files to .gitignore.
Made some properties common in gbuil-to-ide to avoid code duplication/bugs.
Xcode projects are broken for now.
Change-Id: I9530435ffe54158ae68ddae0581ac68f968af235
Reviewed-on: https://gerrit.libreoffice.org/15694
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Stahl <mstahl@redhat.com>
