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>
So no need to expand it at configure time in ure/source/unorc, and no need to
handle the related builddir!=srcdir complications.
Change-Id: Ifa34d25fab9ad2da13ed039bf6c5921b0fb58703
The choice of src/ as a place to save those tarballs was unfortunate,
since it is used everywhere else for own source code. After moving all
external modules to external/, it makes sense to put the tarballs there
too and, while at it, use a more appropriate name.
If src exist as a directory, we move it to external/tarballs and leave
a link behind for backward compat for people switching from after to
before the change in the git repo.
Change-Id: I045c4470945f5fadf7760855833ef58e6594ec80
Reviewed-on: https://gerrit.libreoffice.org/6597
Reviewed-by: Björn Michaelsen <bjoern.michaelsen@canonical.com>
Tested-by: Björn Michaelsen <bjoern.michaelsen@canonical.com>
This provides kdevelop integration and generates one project file for each
old-style module (top level dir). This project file has:
- has four build configurations:
- build the module of the project or build all of LibreOffice
- for each of the above a debug and a nondebug build
- has seven launch targets:
- running the unitchecks, the slowchecks and subsequentchecks
- for each of the above once for the module and once for all
- running LibreOffice interactively
- has custom include paths and thus provides full autocompletion
Change-Id: I6dd51133147d019fc403e3bd814bc6103df94cac
Reviewed-on: https://gerrit.libreoffice.org/6694
Reviewed-by: Björn Michaelsen <bjoern.michaelsen@canonical.com>
Tested-by: Björn Michaelsen <bjoern.michaelsen@canonical.com>
... it is an abbreviation of "Solar Version".
Since nobody can remember that:
remove OUTDIR OUTDIR_FOR_BUILD SOLARVER SOLARVERSION solarpath
and any mention thereof.
Change-Id: Idb3031c4f25a76ac05b22ec67e3ca3e1e8e512ad
Reviewed-on: https://gerrit.libreoffice.org/6515
Tested-by: LibreOffice gerrit bot <gerrit@libreoffice.org>
Reviewed-by: Michael Stahl <mstahl@redhat.com>
Extract boostraping code from convwatch.py to unotest.py. Use python builtin
unittest module as unit test framework. Specify the unit test modules in make
file. Another option would be to use discover mode of unittest module.
Add __pycache__ to global .gitignore to keep the source directory clean.
Another option would be to deliver the unit tests to workdir prior to test
execution.
Currently only system python3 is supported.
Change-Id: I2692817673f786e950e1176a17c7675f989755b6
Reviewed-on: https://gerrit.libreoffice.org/3214
Reviewed-by: David Ostrovsky <David.Ostrovsky@gmx.de>
Tested-by: David Ostrovsky <David.Ostrovsky@gmx.de>
We have only been lucky so far that there hasn't been any compilation errors
caused by using the HOST platform config_*.h files also for the BUILD
platform. But as more and more information found out during configury is
stored in config_*.h files, sooner or later it will be a problem.
Move config/* to config_host/*. When not cross-compiling, the config_*.h files
in config_host expanded from config_*.h.in are all there is. When
cross-compiling, the generated config_*.h files for the BUILD platform are
put into a config_build folder.
Then use config_build when building the cross_toolset and config_host
otherwise.
Change-Id: I3c28cc83866bffd696b45d00dfb68e00bc2ae538
the general goal is
1/ to avoid the bloat of pet conviniences rules that
can be managed using other git provided means
2/ to work toward the goal of a read-only-source-tree build
Change-Id: I5ff9836e135507dcc53b37fd1098aa7876612bfc
This patch allows to do
mkdir <build_dir>
cd <build_dir>
<src_root>/autogen.sh
make
Only the remaining dmake modules are poluting the <src_root>...
which will get eventually convererd to gmake...
Change-Id: Iefd64732fa12e096d554cff4eee6b777deb92338
Reviewed-on: https://gerrit.libreoffice.org/1273
Reviewed-by: Luboš Luňák <l.lunak@suse.cz>
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>
Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
