Age | Commit message (Collapse) | Author |
|
Conflicts:
Repository.mk
RepositoryFixes.mk
connectivity/prj/build.lst
extensions/prj/build.lst
filter/prj/build.lst
fpicker/prj/build.lst
l10ntools/StaticLibrary_transex.mk
saxon/build.xml
shell/prj/build.lst
solenv/gbuild/AllLangResTarget.mk
solenv/gbuild/Configuration.mk
solenv/gbuild/UI.mk
ucb/source/ucp/webdav/webdavcontent.cxx
|
|
Belong to extensions which become
unneeded because of treex
Change-Id: I86ca7494a9022c1e72d64b2ec5cbd41d6e292a00
|
|
Introduce gb_XcuFile_for_extension function to use the right file
depending on WITH_LANG setting.
Change-Id: Ibe4fc4e28fe445fc9391b68d370039528eab7ed8
|
|
Change-Id: Ia07d3fd856578ab6976c02f8a0ec96273db19a2c
|
|
Change-Id: I6d30e96cb9fb0a0800e0b3b0eaa58b98de4d9010
|
|
Change-Id: I9fcddfcdfa2d60860a7b016dbb870a3b6e8f3ea4
|
|
we set the paths here to their runtime values, because in new
build "paradigm" English tree is not updated, just copied. No
problem with that, we'll fix regressions later. Now it works
even in en-US build, but nodes are not localized, because
update_tree.pl does not find localizations due to the changed
paths. update_tree.pl is a hack and must die. It will be killed
in feature/killsdf branch.
Change-Id: Ic16eca538182f5548d4d6c2a23f9bc9764da6b62
|
|
we may want to use syntax highlighter class from svtools later,
which is not available for l10ntools
Change-Id: I5a06b77cb6935e3ef68015fb608aa26ac7c53fac
|
|
Change-Id: Ic668b46872ee0bfd259ca335aed9d68fb545c3a4
|
|
I guess I missed some last time :-)
Change-Id: I164a8baa07850f783b8cdf2e7f3eeaac53a3d29b
|
|
Change-Id: I2decf0178dea2722a752291f21e97cae4aab8074
|
|
Change-Id: I1bb3d359b087421f4acf67955549514fc3c6a236
|
|
...as had been done in the old build system (solenv/inc/extension_helplink.mk).
Especially for bundled extensions, this removes the need to compile the help
data per user on first start.
gb_Extension_add_helpfile(s) replaces gb_Extension_localize_help, and takes care
of all the steps (localization, compilation, inclusion in .oxt), even for the
en-US data (which was handled with additional gb_Extension_add_file calls
before).
Change-Id: Ie4bab66d3cad2b713780a23bf2606ca56cfff37f
|
|
Change-Id: I9f49970e5e06d1afd3fc066a20d1671c93e262fc
|
|
Change-Id: Ib62473d841bc9a66acde6529d3f63e3fd1a00928
|
|
With gb_Jar_add_jar and gb_Jar_add_system_jar adding to the manifest
classpath automatically it is no longer necessary to call
gb_Jar_set_jarclasspath manually except for the URE jars, which
are apparently not supposed to be added automatically.
Change-Id: I1e743e7ecb9cb5651e02005aa09e127bea1b0a29
|
|
|
|
|
|
Change-Id: Ice06e639213aeb6f7f23cbf4634947dd25613db1
|
|
Variables should have module name as prefix to prevent collisions.
|
|
A regression introduced by e7a1e17c4fdea4103e7f921e8cd9c315c1dbe612 "convert
swext to gbuild and add to tail_build."
Change-Id: I29efe28ad6353d725afe9cce6f470c5492aa87a8
|
|
this removes dmake completely out of the build for migrated modules
build.pl now assumes modules to be gbuild, unless there is a
prj/dmake file
Change-Id: I674a036b182ee13c5ec093e83cb3d38133112d3b
|
|
...otherwise, if they are bundled, their per-user data is not regenerated, leading
to inconsitencies.
|
|
Naming convention for gbuild methods:
- "add" is used for stuff that is logically a part of the target
(i.e. not registered at the Module, but defined in the target's makefile)
- "use" is used for stuff that is logically a different target
(i.e. it is registered at the Module, has it's own makefile, may be
in a different module than the target)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This allow to run make in a module wihtout the need to source
Env.Host.sh.
|
|
|
|
|
|
|
|
|
|
|
|
Add a special mode where a Configuration does not deliver to the solver,
and use it in Configuration_mediawiki, preventing the files from
officecfg being overwritten by files from swext.
Should fix the annoying sc_test_filters failure and the smoketest
as well if the mediawiki extension is enabled.
|
|
|
|
|
|
|
|
|