The whole idea of having two paths to look for schemas (one local, for
module, and one global, in $(OUTDIR)) is bad anyway, because there is no
way to do it in XSLT without warning if the checked schema does not
exist in the first path. I see two ways out of that:
1. rewrite schema_val.xsl in a decent language
2. split the node reference check in schema_val.xsl into two phases: the
first phase returns a list of subpaths to check, a helper script
processes that, finds the real paths and feeds it to the second phase
XSL, which does the internal check.
Change-Id: Icfe3f9ec0960cfd3423c1223ad8f495d7634b25a
Else, operator>>= flat out refuses to extract it, even though the particular value in this particular call would fit.
Also OSL_VERIFY the result of >>= (instead of ignoring it) to facilitate future detection of similar problem
Change-Id: I859c38c3589dc9e9ef5bdd882663aa3386a43237
Follow-up of 7fff98724b. Buffer only cell formula values via
setCellFormulaValue. Otherwise we get crash in
FormulaBuffer::applyCellFormulaValues() as array/shared/datatable
formulas are treated differently
Change-Id: Ie344b273ec662e8af1bf9fa54e79614393634974
...now that fa140733ee "fix dep on internal ucpp"
moved things around, so use "=" instead of ":=" here. (And I'm not sure the
other places need ":=" either.)
Change-Id: Id71570c4a55ab08ca339801dec78ef06cfd80ef0
The following tools are considered to be obsolete and are discontinued:
ldump, giparser, testhxx and support.
Change-Id: I70813c046edb30546463cda9eb8a1b96c3e840a3
which was removed in fde638b3ac
Change-Id: I57caf615f0ca49d0b90cb4c68b8ce8edf8f72a97
Reviewed-on: https://gerrit.libreoffice.org/723
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Tested-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
also add the support for the convention that a patch filename
encode the -p value if it end with .[0-9]
for instance foo.patch.2 indicate a -p2 patch
usage:
generate a 'reference' copy of the expanded and patched file structure
$> make clucene.clean
$> patches=t make clucene
go to the module
$> cd clucene
edit files in $WORKDIR/UnpackedTarball/clucene
force a rebuild of things that depend on that UnpackedTarball
$> make clucene.rebuild
create a -p1 patch named clucene.new.patch.1 in the module's directory
$> make clucene.genpatch
you can then rename it, place it where appropriate in the module
hierarchy, update the UnpackedTarball_lucene.mk to apply it.
rinse and repeat from the top (yes the make lucene.clean is needed
to regenerate a 'reference' expanded and patched tarball)
Change-Id: I419c54a5981cffa385521596ba5016d2ca7ef52a
Reviewed-on: https://gerrit.libreoffice.org/712
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>
Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
