/vcl/inc/skia/quartz/

shed>2024-06-12T15:11:50+00:00 994834e07234c7cae90b509adad54f767d612934 Downloaded from https://github.com/unicode-org/icu/releases/tag/release-75-1 Change-Id: I882c57bf5ab613dc71f7ae1c31305596e1ca791f Reviewed-on: https://gerrit.libreoffice.org/c/core/+/168750 Reviewed-by: Xisco Fauli <xiscofauli@libreoffice.org> Tested-by: Jenkins Tested-by: Xisco Fauli <xiscofauli@libreoffice.org> 
Downloaded from https://github.com/unicode-org/icu/releases/tag/release-75-1

Change-Id: I882c57bf5ab613dc71f7ae1c31305596e1ca791f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/168750
Reviewed-by: Xisco Fauli <xiscofauli@libreoffice.org>
Tested-by: Jenkins
Tested-by: Xisco Fauli <xiscofauli@libreoffice.org>
external/icu: Drop hidden dependency on Python 2024-04-23T09:32:51+00:00 Stephan Bergmann stephan.bergmann@allotropia.de 2024-04-22T20:02:28+00:00 5d8e29c94edeed564df4b68aed01f695d5ece070 ...which was always satisfied directly from the system, regardless of our --enable-python=... setting. (And which was a problem for my Git Bash and WSL based Windows build attempt, where it happened to find a dysfunctional Python wrapper at C:/Users/steph/AppData/Local/Microsoft/WindowsApps/python3 which caused a [...] > Not rebuilding data/rules.mk, assuming prebuilt data in data/in > Spawning Python to generate test/testdata/rules.mk... > Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases. > configure: error: Python failed to run; see above error. error when building ExternalProject_icu.) There are three uses of that PYTHON setting across workdir/UnpackedTarget/icu: 1 In source/configure.ac to generate source/data/rules.mk if source/data/locales/root.txt would exist---but which doesn't, so we don't actually need PYTHON there. 2 In source/configure.ac to generate source/test/testdata/rules.mk, but which our (non-check) build apparently doesn't need anyway. 3 In source/data/Makefile.in for target check-local, which is a sub-target of check (which we don't build). Change-Id: I7455cc91fc67f36582bf54851c07030830cd3b8d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166500 Reviewed-by: Stephan Bergmann <stephan.bergmann@allotropia.de> Tested-by: Jenkins 
...which was always satisfied directly from the system, regardless of our
--enable-python=... setting.  (And which was a problem for my Git Bash and WSL
based Windows build attempt, where it happened to find a dysfunctional Python
wrapper at C:/Users/steph/AppData/Local/Microsoft/WindowsApps/python3 which
caused a

[...]
> Not rebuilding data/rules.mk, assuming prebuilt data in data/in
> Spawning Python to generate test/testdata/rules.mk...
> Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases.
> configure: error: Python failed to run; see above error.

error when building ExternalProject_icu.)

There are three uses of that PYTHON setting across workdir/UnpackedTarget/icu:

1  In source/configure.ac to generate source/data/rules.mk if
source/data/locales/root.txt would exist---but which doesn't, so we don't
actually need PYTHON there.

2  In source/configure.ac to generate source/test/testdata/rules.mk, but which
our (non-check) build apparently doesn't need anyway.

3  In source/data/Makefile.in for target check-local, which is a sub-target of
check (which we don't build).

Change-Id: I7455cc91fc67f36582bf54851c07030830cd3b8d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166500
Reviewed-by: Stephan Bergmann <stephan.bergmann@allotropia.de>
Tested-by: Jenkins