Hi;
Just to note that if you look at main/stlport/systemstl, you will see that if
everything else fails we would try to use's boost's TR1 as a replacement for a
decent STL. That approach doesn't really work anymore. Indeed FreeBSD's PPC64
AOO port appears broken with this message:
fails to compi
Hello;
FWIW, for those working on that wonderful ICU update, you may want to look at
the old IBM's symphony code as it used ICU extensively and the code should be
usable license-wise to AOO.
Cheers,
Pedro.
ue to inactivity.
In addition to improved ICU support, it also had an enhanced VBA
implementation, otherwise I think most was already in AOO.
Sorry,
Pedro.
On Monday, November 4, 2024 at 10:34:41 AM GMT-5, Pedro F. Giffuni wrote:
Hello;
FWIW, for those working on that wonderful ICU update, you may
people with
an eastern background. It is a lot of work and the chinese IBM team never got
to finish it, but a lot of the hard work is done already within the Symphony
trunk already :).
Cheers,
Pedro.
On Thursday, November 7, 2024 at 07:35:23 PM GMT-5, Pedro F. Giffuni
wrote:
Ugh
(skipping some interesting test descriptions)
Hi guys;
Just thought I'd mention, concerning the python build and newer Windows SDK...
Long ago I changed the naming of the python build patches to clarify that
Python expects to change the build path for newer MS compilers.
In order to build python
Hi;
As a follow up to my comments on python and MSVC versions, I think a starting
point to fix the build problem correctly would be to add something like this in
main/python/makefile.mk (around line 127)
# Requires adapting for according to the MSVC compiler version.# Normally
PCBuild will carry
