You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Pe...@apache.org on 2026/08/21 14:52:07 UTC
compile trunk with modern windows build tools
Hello all,
I could build trunk today with MSVC 2019. Anything older that compiles
C++11 should work too.
- I removed the throw(x) declarations we have talked about.
- fixed the gawk issue bothering us all the years. There is no need to
temper cygwin any longer.
- bumbed coinMP to the latest Version 1.8.4 - this impacts all
platforms, and i sadly can only build Windows at the moment.
- python 3.11 is integrated and builds.
- configure detection is updated to the new needs.
- still using the old sdkv7 goal was to be able to build again.
Everything else was not important to me.
i hacked the update script:
#!/usr/bin/env bash
set-eopipefail
#
# Parse options
#
AOO_SKIP_CONFIG=
AOO_JUST_CONFIG=
AOO_VERBOSE_BUILD=
AOO_BUILD_TYPE=
AOO_BUILD_VERSION=
AOO_BUILD_BETA=
AOO_BUILD_DEV=
AOO_BUILD_SRC=
AOO_DEBUG=
#AOO_LANGS="ast bg ca ca-XR ca-XV cs da de el en-GB en-US es et eu fi fr
gd gl he hi hu hy it ja kab km ko lt nb nl om pl pt pt-BR ru sk sl sr sv
ta th tr uk vi zh-CN zh-TW"
AOO_LANGS="en-US"
AOO_PATH="/cygdrive/c/workspace/openoffice/main"
AOO_ANT_HOME="/cygdrive/c//workspace/apache-ant-1.10.13"
AOO_JDK_HOME="/cygdrive/c/Program Files (x86)/Eclipse
Adoptium/jdk-8.0.452.9-hotspot"
AOO_CSC_PATH="/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5"
AOO_CL_HOME="/cygdrive/c/Program Files (x86)/Microsoft Visual
Studio/2019/BuildTools/VC/Tools/MSVC/14.29.30133"
AOO_ASM_HOME="/cygdrive/c/Program Files (x86)/Microsoft Visual
Studio/2019/BuildTools/VC/Tools/MSVC/14.29.30133"
AOO_SDK_PATH="/cygdrive/c/Microsoft_SDKs/Windows/v7.0/v7.0"
AOO_WDK_HOME="/cygdrive/c/WinDDK/7600.16385.1"
AOO_DIRECTX_HOME="/cygdrive/c/Microsoft_DirectX_SDK_June_2010"# original
path
#AOO_DIRECTX_HOME="/cygdrive/c/Program Files (x86)/Microsoft DirectX SDK
(June 2010)"
AOO_NASM_HOME="/cygdrive/c/nasm"#todo search path
# AOO_NASM_HOME="/cygdrive/c/Program Files (x86)/NASM" # todo search path
AOO_JUNIT="/cygdrive/c/junit/junit-4.13.2.jar"
AOO_HAMCREST="/cygdrive/c/hamcrest/hamcrest-core-1.3.jar"
AOO_MOZBUILD="/cygdrive/c/mozilla-build"# only 3.4 works
AOO_NSIS_HOME="/cygdrive/c/NSIS"# todo search path
whiletrue; do
case"$1"in
"--verbose")AOO_VERBOSE_BUILD="--enable-verbose"; shift;;
"--skip-config")AOO_SKIP_CONFIG="yes"; shift;;
"--just-config")AOO_JUST_CONFIG="yes"; shift;;
"--build-src")AOO_BUILD_SRC="yes"; shift;;
"--dev")AOO_BUILD_TYPE="Apache OpenOffice Test Development Build";
AOO_BUILD_VERSION=" [${AOO_BUILD_TYPE}]"; AOO_BUILD_DEV="yes";
AOO_BUILD_BETA=""; shift;;
"--beta")AOO_BUILD_TYPE="Apache OpenOffice Beta Build";
AOO_BUILD_VERSION=" [${AOO_BUILD_TYPE}]"; AOO_BUILD_BETA="yes";
AOO_BUILD_DEV=""; shift;;
"--langs")shift; AOO_LANGS="$1"; shift;;
"--symbols")AOO_DEBUG="$AOO_DEBUG--enable-symbols=yes"; shift;;
"--debug")AOO_DEBUG="$AOO_DEBUG--enable-debug"; shift;;
"--")shift; break;;
"")break;;
* )echo"unknown option: $1"; shift;;
esac
done
if[ !-d../main -o!-dsal ] ; then
cd"$AOO_PATH"
fi
AOO_ATL_INCLUDE="$AOO_WDK_HOME/inc/atl71"
AOO_ATL_LIB="$AOO_WDK_HOME/lib/atl/i386"
AOO_MFC_INCLUDE="$AOO_WDK_HOME/inc/mfc42"
AOO_MFC_LIB="$AOO_WDK_HOME/lib/mfc/i386"
# It is possible that missing directories are detected after hours of
# compilation. We try to avoid problems by checking them in advance.
fordin"$AOO_ANT_HOME""$AOO_JDK_HOME""$AOO_CSC_PATH""$AOO_CL_HOME"\
"$AOO_ASM_HOME""$AOO_SDK_PATH""$AOO_ATL_INCLUDE""$AOO_ATL_LIB"\
"$AOO_MFC_INCLUDE""$AOO_MFC_LIB""$AOO_DIRECTX_HOME"\
"$AOO_MOZBUILD""$AOO_NASM_HOME""$AOO_NSIS_HOME"; do
if[ !-d"$d"]; then
echo"Directory $ddoes not exist!"
exit1
fi
done
rm-fsolenv/inc/reporevision.lst
if[ -econfigure.in ]; then
AOO_CONF_T="configure.in"
else
AOO_CONF_T="configure.ac"
fi
if[ !-econfigure -o$AOO_CONF_T-ntconfigure ] ; then
echo"Running autoconf..."
autoconf||exit1
fi
if[ "$AOO_SKIP_CONFIG"!="yes"]; then
(./configure\
--with-build-version="$(date+"%Y-%m-%d %H:%M")"\
--with-frame-home="$AOO_SDK_PATH"\
--with-ant-home="$AOO_ANT_HOME"\
--with-jdk-home="$AOO_JDK_HOME"\
--with-csc-path="$AOO_CSC_PATH"\
--with-cl-home="$AOO_CL_HOME"\
--with-windows-sdk-version=10.0.19041.0\
--with-asm-home="$AOO_CL_HOME"\
--with-atl-include-dir="$AOO_ATL_INCLUDE"\
--with-atl-lib-dir="$AOO_ATL_LIB"\
--with-mfc-include-dir="$AOO_MFC_INCLUDE"\
--with-mfc-lib-dir="$AOO_MFC_LIB"\
--with-dmake-url="https://github.com/jimjag/dmake/archive/v4.13.1/dmake-4.13.1.tar.gz"\
--with-directx-home="$AOO_DIRECTX_HOME"\
--with-nasm-home="$AOO_NASM_HOME"\
--enable-win-x64-shellext\
--enable-wiki-publisher\
--with-junit="$AOO_JUNIT"\
--with-hamcrest-core="$AOO_HAMCREST"\
--without-stlport\
--with-mozilla-build="$AOO_MOZBUILD"\
--enable-category-b\
--enable-beanshell\
--with-lang="${AOO_LANGS}"\
--enable-bundled-dictionaries\
--with-packager-list=/cygdrive/c/Source/Pack.lst\
--with-nsis-path="$AOO_NSIS_HOME"\
$AOO_DEBUG\
|teeconfig.out) ||exit1
fi
source./winenv.set.sh||exit1
./bootstrap||exit1
rm-fsolenv/inc/reporevision.lst
cdinstsetoo_native
cpus=`nproc`||cpus=1
if[ $cpus-ge8]; then
p1=$(( $cpus/4))
p2=4
elif[ $cpus-ge2]; then
p1=$(( $cpus/2))
p2=2
else
p1=1
p2=2
fi
timeperl "$SOLARENV/bin/build.pl"--all -P${p1} -- -P${p2} ||exit1
cdutil
if[ "$AOO_BUILD_BETA"="yes"]; then
dmake-P${cpus}openofficebeta||exit1
dmake-P${cpus}sdkoobeta_en-US||exit1
dmake-P${cpus}ooobetalanguagepack||exit1
elif[ "$AOO_BUILD_DEV"="yes"]; then
dmake-P${cpus}openofficedev||exit1
dmake-P${cpus}sdkoodev_en-US||exit1
dmake-P${cpus}ooodevlanguagepack||exit1
else
dmake-P${cpus}ooolanguagepack||exit1
dmake-P${cpus}sdkoo_en-US||exit1
fi
if[ "$AOO_BUILD_SRC"="yes"]; then
dmakeaoo_srcrelease||exit1
fi
date"+Build ended at %H:%M:%S"
.net integration has still issues. and it is deactivated. I am close to
fix that one too.
The changes are substantial. so we need to test all platforms. 5k files
have ben touched and changed. lol
And currently i am 61 commits behind, that why i have removed the branch
again. will publish when i could rebase to head. Currently there are
merge confilcts.
I will command claude remotly to push to origin. I am busy atm, dont
have that much time to have a deep look. But i can confirm AOO starts,
but maybe there is still something broken.
I can upload my AOO45 installer if testers want to check out (only
english language compiled sorry, i can compile other languages available
as sdfs.)
All the best
Peter
Re: compile trunk with modern windows build tools
Posted by Pe...@apache.org.
okay was faster then expected. there are some caveats :
If you build please have an eye on:
Yes — five things, and I've fixed the two that would have bitten silently.
Already fixed:
1. Duplicate cpython delivery. Upstream independently landed the same
fix I made (0bab7b5332 vs my b7565a6c6e). Both survived the rebase
because they sit in different parts of d.lst, leaving two mkdir and two
copy lines for one directory. De-duplicated and committed.
2. Two throw specifications upstream added outside the conflict region —
swept, as covered earlier.
Must do before building:
3. main/configure is stale. Both upstream and I changed configure.ac
(they added --with-system-icu plumbing, I added
DISABLE_CLI/HOST_PYTHON/the AWK fix). The generated configure is
timestamped 12:06 against a configure.ac from 16:50, so it contains
neither. It needs autoconf and then a full configure run — which also
regenerates set_soenv and winenv.set.sh. Skipping this is the single
most likely way to get baffling failures.
Worth watching, merged clean but unverified by a build:
4. solenv/gbuild/platform/windows.mk. My COMEX 14 block and
gb_MakeDepend_FILTEROUT are intact, but upstream changed the same file
twice — adding gbuild targets for Configuration, and adding version as a
Windows library. The second is a link-input change on Windows specifically.
5. The officecfg → gbuild shift. Upstream added
solenv/gbuild/Configuration.mk and deleted the
officecfg/registry/schema/.../makefile.mk files, moving .xcs/.xcu
generation into gbuild. That's a real build-system change interacting
with a tree that has stale officecfg output from the old mechanism — a
strong candidate for dmake clean_misc in officecfg if it misbehaves.
pushing now.
All the best
Peter
Am 21.08.2026 um 16:52 schrieb Petko@apache.org:
> Hello all,
>
> I could build trunk today with MSVC 2019. Anything older that compiles
> C++11 should work too.
>
> - I removed the throw(x) declarations we have talked about.
>
> - fixed the gawk issue bothering us all the years. There is no need to
> temper cygwin any longer.
>
> - bumbed coinMP to the latest Version 1.8.4 - this impacts all
> platforms, and i sadly can only build Windows at the moment.
>
> - python 3.11 is integrated and builds.
>
> - configure detection is updated to the new needs.
>
> - still using the old sdkv7 goal was to be able to build again.
> Everything else was not important to me.
>
> i hacked the update script:
>
> #!/usr/bin/env bash
> set-eopipefail
> #
> # Parse options
> #
> AOO_SKIP_CONFIG=
> AOO_JUST_CONFIG=
> AOO_VERBOSE_BUILD=
> AOO_BUILD_TYPE=
> AOO_BUILD_VERSION=
> AOO_BUILD_BETA=
> AOO_BUILD_DEV=
> AOO_BUILD_SRC=
> AOO_DEBUG=
> #AOO_LANGS="ast bg ca ca-XR ca-XV cs da de el en-GB en-US es et eu fi
> fr gd gl he hi hu hy it ja kab km ko lt nb nl om pl pt pt-BR ru sk sl
> sr sv ta th tr uk vi zh-CN zh-TW"
> AOO_LANGS="en-US"
> AOO_PATH="/cygdrive/c/workspace/openoffice/main"
> AOO_ANT_HOME="/cygdrive/c//workspace/apache-ant-1.10.13"
> AOO_JDK_HOME="/cygdrive/c/Program Files (x86)/Eclipse
> Adoptium/jdk-8.0.452.9-hotspot"
> AOO_CSC_PATH="/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5"
> AOO_CL_HOME="/cygdrive/c/Program Files (x86)/Microsoft Visual
> Studio/2019/BuildTools/VC/Tools/MSVC/14.29.30133"
> AOO_ASM_HOME="/cygdrive/c/Program Files (x86)/Microsoft Visual
> Studio/2019/BuildTools/VC/Tools/MSVC/14.29.30133"
> AOO_SDK_PATH="/cygdrive/c/Microsoft_SDKs/Windows/v7.0/v7.0"
> AOO_WDK_HOME="/cygdrive/c/WinDDK/7600.16385.1"
> AOO_DIRECTX_HOME="/cygdrive/c/Microsoft_DirectX_SDK_June_2010"#
> original path
> #AOO_DIRECTX_HOME="/cygdrive/c/Program Files (x86)/Microsoft DirectX
> SDK (June 2010)"
> AOO_NASM_HOME="/cygdrive/c/nasm"#todo search path
> # AOO_NASM_HOME="/cygdrive/c/Program Files (x86)/NASM" # todo search path
> AOO_JUNIT="/cygdrive/c/junit/junit-4.13.2.jar"
> AOO_HAMCREST="/cygdrive/c/hamcrest/hamcrest-core-1.3.jar"
> AOO_MOZBUILD="/cygdrive/c/mozilla-build"# only 3.4 works
> AOO_NSIS_HOME="/cygdrive/c/NSIS"# todo search path
> whiletrue; do
> case"$1"in
> "--verbose")AOO_VERBOSE_BUILD="--enable-verbose"; shift;;
> "--skip-config")AOO_SKIP_CONFIG="yes"; shift;;
> "--just-config")AOO_JUST_CONFIG="yes"; shift;;
> "--build-src")AOO_BUILD_SRC="yes"; shift;;
> "--dev")AOO_BUILD_TYPE="Apache OpenOffice Test Development Build";
> AOO_BUILD_VERSION=" [${AOO_BUILD_TYPE}]"; AOO_BUILD_DEV="yes";
> AOO_BUILD_BETA=""; shift;;
> "--beta")AOO_BUILD_TYPE="Apache OpenOffice Beta Build";
> AOO_BUILD_VERSION=" [${AOO_BUILD_TYPE}]"; AOO_BUILD_BETA="yes";
> AOO_BUILD_DEV=""; shift;;
> "--langs")shift; AOO_LANGS="$1"; shift;;
> "--symbols")AOO_DEBUG="$AOO_DEBUG--enable-symbols=yes"; shift;;
> "--debug")AOO_DEBUG="$AOO_DEBUG--enable-debug"; shift;;
> "--")shift; break;;
> "")break;;
> * )echo"unknown option: $1"; shift;;
> esac
> done
> if[ !-d../main -o!-dsal ] ; then
> cd"$AOO_PATH"
> fi
> AOO_ATL_INCLUDE="$AOO_WDK_HOME/inc/atl71"
> AOO_ATL_LIB="$AOO_WDK_HOME/lib/atl/i386"
> AOO_MFC_INCLUDE="$AOO_WDK_HOME/inc/mfc42"
> AOO_MFC_LIB="$AOO_WDK_HOME/lib/mfc/i386"
> # It is possible that missing directories are detected after hours of
> # compilation. We try to avoid problems by checking them in advance.
> fordin"$AOO_ANT_HOME""$AOO_JDK_HOME""$AOO_CSC_PATH""$AOO_CL_HOME"\
> "$AOO_ASM_HOME""$AOO_SDK_PATH""$AOO_ATL_INCLUDE""$AOO_ATL_LIB"\
> "$AOO_MFC_INCLUDE""$AOO_MFC_LIB""$AOO_DIRECTX_HOME"\
> "$AOO_MOZBUILD""$AOO_NASM_HOME""$AOO_NSIS_HOME"; do
> if[ !-d"$d"]; then
> echo"Directory $ddoes not exist!"
> exit1
> fi
> done
> rm-fsolenv/inc/reporevision.lst
> if[ -econfigure.in ]; then
> AOO_CONF_T="configure.in"
> else
> AOO_CONF_T="configure.ac"
> fi
> if[ !-econfigure -o$AOO_CONF_T-ntconfigure ] ; then
> echo"Running autoconf..."
> autoconf||exit1
> fi
> if[ "$AOO_SKIP_CONFIG"!="yes"]; then
> (./configure\
> --with-build-version="$(date+"%Y-%m-%d %H:%M")"\
> --with-frame-home="$AOO_SDK_PATH"\
> --with-ant-home="$AOO_ANT_HOME"\
> --with-jdk-home="$AOO_JDK_HOME"\
> --with-csc-path="$AOO_CSC_PATH"\
> --with-cl-home="$AOO_CL_HOME"\
> --with-windows-sdk-version=10.0.19041.0\
> --with-asm-home="$AOO_CL_HOME"\
> --with-atl-include-dir="$AOO_ATL_INCLUDE"\
> --with-atl-lib-dir="$AOO_ATL_LIB"\
> --with-mfc-include-dir="$AOO_MFC_INCLUDE"\
> --with-mfc-lib-dir="$AOO_MFC_LIB"\
> --with-dmake-url="https://github.com/jimjag/dmake/archive/v4.13.1/dmake-4.13.1.tar.gz"\
>
> --with-directx-home="$AOO_DIRECTX_HOME"\
> --with-nasm-home="$AOO_NASM_HOME"\
> --enable-win-x64-shellext\
> --enable-wiki-publisher\
> --with-junit="$AOO_JUNIT"\
> --with-hamcrest-core="$AOO_HAMCREST"\
> --without-stlport\
> --with-mozilla-build="$AOO_MOZBUILD"\
> --enable-category-b\
> --enable-beanshell\
> --with-lang="${AOO_LANGS}"\
> --enable-bundled-dictionaries\
> --with-packager-list=/cygdrive/c/Source/Pack.lst\
> --with-nsis-path="$AOO_NSIS_HOME"\
> $AOO_DEBUG\
> |teeconfig.out) ||exit1
> fi
> source./winenv.set.sh||exit1
> ./bootstrap||exit1
> rm-fsolenv/inc/reporevision.lst
> cdinstsetoo_native
> cpus=`nproc`||cpus=1
> if[ $cpus-ge8]; then
> p1=$(( $cpus/4))
> p2=4
> elif[ $cpus-ge2]; then
> p1=$(( $cpus/2))
> p2=2
> else
> p1=1
> p2=2
> fi
> timeperl "$SOLARENV/bin/build.pl"--all -P${p1} -- -P${p2} ||exit1
> cdutil
> if[ "$AOO_BUILD_BETA"="yes"]; then
> dmake-P${cpus}openofficebeta||exit1
> dmake-P${cpus}sdkoobeta_en-US||exit1
> dmake-P${cpus}ooobetalanguagepack||exit1
> elif[ "$AOO_BUILD_DEV"="yes"]; then
> dmake-P${cpus}openofficedev||exit1
> dmake-P${cpus}sdkoodev_en-US||exit1
> dmake-P${cpus}ooodevlanguagepack||exit1
> else
> dmake-P${cpus}ooolanguagepack||exit1
> dmake-P${cpus}sdkoo_en-US||exit1
> fi
> if[ "$AOO_BUILD_SRC"="yes"]; then
> dmakeaoo_srcrelease||exit1
> fi
> date"+Build ended at %H:%M:%S"
>
> .net integration has still issues. and it is deactivated. I am close
> to fix that one too.
>
> The changes are substantial. so we need to test all platforms. 5k
> files have ben touched and changed. lol
>
> And currently i am 61 commits behind, that why i have removed the
> branch again. will publish when i could rebase to head. Currently
> there are merge confilcts.
>
> I will command claude remotly to push to origin. I am busy atm, dont
> have that much time to have a deep look. But i can confirm AOO starts,
> but maybe there is still something broken.
>
>
> I can upload my AOO45 installer if testers want to check out (only
> english language compiled sorry, i can compile other languages
> available as sdfs.)
>
> All the best
>
> Peter
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Czesław Wolański <cw...@apache.org>.
Hi Pedro, Peter
Right-clicking the Quick-starter icon in the system tray should open a context menu. In reality, it triggers the recovery dialog.
Regards,
Czesław
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Czesław Wolański <cw...@apache.org>.
Hi all,
1.
It is not possible to add object to the Gallery or insert object from it using the mouse. The mouse pointer changes to "Unavailable".
2.
In Draw insert an object from the Gallery (via context menu: Insert ⟶ Copy) and
delete/cut the object. Result: crash
Regards,
Czesław
On 2026/08/26 21:30:20 Petko@apache.org wrote:
>
> Am 26.08.2026 um 01:10 schrieb Pedro Lino via dev:
> > Hi Peter
> >
> > Excellent progress. As expected new features and new bugs ;)
> >
> >> On 08/25/2026 7:53 PM WESTpetko@apache.org wrote:
> >> 1) now the OfficeDialogs are used if the option is ticked
> > Confirmed fixed
> >
> >> 2) java is now detected automatically
> > Confirmed fixed
> >
> >> 4) AOO installs now in program files and not in program files (x86)
> > Confirmed fixed
> >
> >> I think that is all. What i have for now.
> > Some new problems as a consequence of switching to 64bit:
> >
> > 1) "The scripting language Python is not supported"
> ok, Identified the issue, fix is ready.
> >
> > 2) Can not install x86 extensions (obviously)
> > e.g.
> > https://www.arielch.org/aoo/aoo-pdf-import/
> this is the reason I opted for AOO5 instead of AOO42.
> We can look into this later.
> >
> > 3) Some other files cause crashes (odg, odp in addition to ppt)
> My odp, odg files open fine. Can you send me the file that fail on your
> end?
> >
> > It seems to be faster when loading the program and heavy spreadsheets but maybe it is just my imagination :)
> >
> > All the best,
> > Pedro
> No, fresh dev build pushed for testing.
>
> All the best
>
> Peter
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Czesław Wolański <cw...@apache.org>.
Hi Peter, all
On 2026/08/28 14:46:46 Petko@apache.org wrote:
> Hello all,
>
> I have uploaded a new testversion.
>
> https://drive.google.com/file/d/1Ual6x5omeiIKPjhflhQWOUe492wRQ_kn/view?usp=sharing
>
Thanks!
> > 1.
> > It is not possible to add object to the Gallery or insert object from it using the mouse. The mouse pointer changes to "Unavailable".
> fixed, the win API switched to v6, we support in the code 5.2. For now
> we went back on 5.2.
>
> Renewal to newer API is still open in total.
>
I confirm: FIXED
> >
> > 2.
> > In Draw insert an object from the Gallery (via context menu: Insert ⟶ Copy) and
> > delete/cut the object. Result: crash
> fixed, pointer were only 32bit long.
I confirm: FIXED
Sample Python macros are finally displayed in the "Python macros" dialog box.
All the best,
Czesław
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Windows x86 and Windows x64 (WAS Re: compile trunk with modern windows build tools)
Posted by Marcus <ma...@wtnet.de>.
Am 29.08.26 um 16:12 schrieb Pedro Lino via dev:
> Thank you for kicking off the discussion.
>
>> Full Focus:
>> Windows 10 and 11. This should be our main goal to fully support.
>
> Agreed.
> The x64 build is already the most complete and stable release.
> Updating from 4.1.16 x86 to 4.5 (or whatever future name) x64 is straightforward without any loss of extensions or settings in the profile.
> The only exception would be those extensions that are specifically compiled for x86 (such as the Hybrid PDF importer) which seems to be a very marginal problem.
>
>> Windows 8.1, and windows 7 with latest service packs.
>> Here the approach would be best to have a best effort.
even when the new AOO 64-bit is working fine also on Windows 7 and 8.1,
but the newest (or any Python) cannot be used, I would ship it. Better
this AOO version as no version.
> Agreed (since there are no statistics for the number of AOO users on Win7)
> But if the x64 installer is updated to work on Win7 all problems (except Python?) are possibly already solved?
>
>> No support:
>> Windows Vista, Windows XP
>> These are definitly eol.
Yeah, even when it's a bit sad (as we have supported these Win versions
much longer than even Microsoft) but some day the time will come where
this is ending.
As a little reminder how long ago this is already: ;-)
https://support.microsoft.com/en-US/windows/deployment/updates-lifecycle/what-does-it-mean-if-windows-isn-t-supported
> Agreed. But a message should be added in the Download page warning users that for Windows Vista/XP the final version available was 4.1.xx
>
>> Currently the installer is win10, I dont think it is a big deal to
>> downgrade it to win7.
>> AOO itself is currently still winxp/2k API. I have code to push to
>> win10, but not for win7.
>
> These two really need to match to Win7 (if Win7 is this group's decision)
If technically possible and sensible I would draw the line at Windows 7
as minimal version.
> Regarding the 32bit (aka x86) installer and office suite, I have no idea how useful this really is. Microsoft does have a 32bit version of Windows 10 (but not of Windows 11). But where is it used? What proportion of OpenOffice users really need a 32bit Office?
>
>> What i dont know is how to deal with our Languages. Should i check if we
>> could pimp the installer?
>
> That would be fantastic.
>
>> You download one multilanguage installer, AOO version is always us-en.
>> And the installer offers a language picker, which downloads the language
>> file and installs the selected ones.
>> would save us a lot of release space.
>
> That would be perfect.
>
> And as an additional touch of improvement: the language installer/pack would include the latest version of the Spell Checker/Thesaurus for the selected language (as currently does the full installer for supported languages)
Even when this topic also deserves its own thread, I would second it
when we have estimated the effort to support this way of upgrading software.
Migration from 32-bit to 64-bit is a thing of mostly changing existing
lines of code - plus addition here and there, but a changed installation
would need new lines of code incl. new translation of new dialogs.
Of course, I don't stop anyone from developing this. But just would to
point out that it is not easy.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Windows x86 and Windows x64 (WAS Re: compile trunk with modern windows build tools)
Posted by Pedro Lino via dev <de...@openoffice.apache.org>.
Hi Peter, Marcus, all
Thank you for kicking off the discussion.
> Full Focus:
> Windows 10 and 11. This should be our main goal to fully support.
Agreed.
The x64 build is already the most complete and stable release.
Updating from 4.1.16 x86 to 4.5 (or whatever future name) x64 is straightforward without any loss of extensions or settings in the profile.
The only exception would be those extensions that are specifically compiled for x86 (such as the Hybrid PDF importer) which seems to be a very marginal problem.
> Windows 8.1, and windows 7 with latest service packs.
> Here the approach would be best to have a best effort.
Agreed (since there are no statistics for the number of AOO users on Win7)
But if the x64 installer is updated to work on Win7 all problems (except Python?) are possibly already solved?
> No support:
> Windows Vista, Windows XP
> These are definitly eol.
Agreed. But a message should be added in the Download page warning users that for Windows Vista/XP the final version available was 4.1.xx
> Currently the installer is win10, I dont think it is a big deal to
> downgrade it to win7.
> AOO itself is currently still winxp/2k API. I have code to push to
> win10, but not for win7.
These two really need to match to Win7 (if Win7 is this group's decision)
Regarding the 32bit (aka x86) installer and office suite, I have no idea how useful this really is. Microsoft does have a 32bit version of Windows 10 (but not of Windows 11). But where is it used? What proportion of OpenOffice users really need a 32bit Office?
> What i dont know is how to deal with our Languages. Should i check if we
> could pimp the installer?
That would be fantastic.
> You download one multilanguage installer, AOO version is always us-en.
> And the installer offers a language picker, which downloads the language
> file and installs the selected ones.
> would save us a lot of release space.
That would be perfect.
And as an additional touch of improvement: the language installer/pack would include the latest version of the Spell Checker/Thesaurus for the selected language (as currently does the full installer for supported languages)
Finally, about the Extensions: the extensions available on the LO website are compatible with AOO (at least dictionaries and all that I am using) and work correctly on AOO x64 too.
All the best,
Pedro
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Windows x86 and Windows x64 (WAS Re: compile trunk with modern windows build tools)
Posted by Pe...@apache.org.
Am 29.08.2026 um 11:11 schrieb Petko@apache.org:
>
> Am 29.08.2026 um 10:05 schrieb Marcus:
>> Am 29.08.26 um 09:54 schrieb Petko@apache.org:
>>> I would then merge this into trunk. we have some substantial gains.
>>>
>>> Am 29.08.2026 um 00:48 schrieb Pedro Lino via dev:
>>>>> On 08/28/2026 3:46 PM WEST petko@apache.org wrote:
>>>>>> 1) The x64 build will not install on Windows 7 (asks for 10 or
>>>>>> later)
>>>>> yes sorry my error. floor has been set on win10.
>>>>>> Do we know users that want win7?
>>>> I would expect that quite a few OpenOffice users are still on
>>>> Windows 7. According to estimates there are still around 1-2% of
>>>> Windows users on Windows 7 (more than on 8 and 8.1 combined) which
>>>> converts to around 12-24 million Win 7 users worldwide.
>>>> But the honest answer is, I don't know anyone who still uses
>>>> Windows 7...
>>> I would like to discuss this in a different discussion. So its not
>>> hidden in test builds, but a popper discussion.
>>
>> I hope you don't mind when I start. ;-)
> You are welcome.
>>
>> We are on the way the switch from 32-bit to 64-bit on the Windows
>> platform. Therefore it is the normal way to provide both versions for
>> a - yes, still to be discussed - time frame.
>>
>> Or in other words it would not be a smart idea to make a big bang
>> switch to 64-bit without an alternative. It is still the most used
>> platform for AOO by far.
>>
>> My 2 ct.
> I discussed a bit with perplexity about Release strategy.
> I gave the AI the Frame that it should not look at our developer
> community, and that we want to support the max of our users.
>
> It supported Marcus in the approach, to provide Win64 as the future
> path, but still offer the 32bit in parallel. The limit is technical
> and organisatorical constraints. EOL for 32bit by download numbers
> Balanced against our effort in developing and testing.
>
> For Windows Versions:
>
> Full Focus:
>
> Windows 10 and 11. This should be our main goal to fully support.
>
> Limited support / Legacy Version
>
> Windows 8.1, and windows 7 with latest service packs.
>
> Here the approach would be best to have a best effort.
one thing to note. A windows 7 Version is bound to python 3.9.X. Already
beyond what we have bumbed to.
Can only be done on bazel, which is easier configured to pull in
different versions.
>
> No support:
>
> Windows Vista, Windows XP
>
> These are definitly eol.
>
> Currently the installer is win10, I dont think it is a big deal to
> downgrade it to win7.
>
> AOO itself is currently still winxp/2k API. I have code to push to
> win10, but not for win7.
>
> What i dont know is how to deal with our Languages. Should i check if
> we could pimp the installer?
>
> You download one multilanguage installer, AOO version is always us-en.
> And the installer offers a language picker, which downloads the
> language file and installs the selected ones.
> would save us a lot of release space.
>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Windows x86 and Windows x64 (WAS Re: compile trunk with modern windows build tools)
Posted by Pe...@apache.org.
Am 29.08.2026 um 10:05 schrieb Marcus:
> Am 29.08.26 um 09:54 schrieb Petko@apache.org:
>> I would then merge this into trunk. we have some substantial gains.
>>
>> Am 29.08.2026 um 00:48 schrieb Pedro Lino via dev:
>>>> On 08/28/2026 3:46 PM WEST petko@apache.org wrote:
>>>>> 1) The x64 build will not install on Windows 7 (asks for 10 or later)
>>>> yes sorry my error. floor has been set on win10.
>>>>> Do we know users that want win7?
>>> I would expect that quite a few OpenOffice users are still on
>>> Windows 7. According to estimates there are still around 1-2% of
>>> Windows users on Windows 7 (more than on 8 and 8.1 combined) which
>>> converts to around 12-24 million Win 7 users worldwide.
>>> But the honest answer is, I don't know anyone who still uses Windows
>>> 7...
>> I would like to discuss this in a different discussion. So its not
>> hidden in test builds, but a popper discussion.
>
> I hope you don't mind when I start. ;-)
You are welcome.
>
> We are on the way the switch from 32-bit to 64-bit on the Windows
> platform. Therefore it is the normal way to provide both versions for
> a - yes, still to be discussed - time frame.
>
> Or in other words it would not be a smart idea to make a big bang
> switch to 64-bit without an alternative. It is still the most used
> platform for AOO by far.
>
> My 2 ct.
I discussed a bit with perplexity about Release strategy.
I gave the AI the Frame that it should not look at our developer
community, and that we want to support the max of our users.
It supported Marcus in the approach, to provide Win64 as the future
path, but still offer the 32bit in parallel. The limit is technical and
organisatorical constraints. EOL for 32bit by download numbers Balanced
against our effort in developing and testing.
For Windows Versions:
Full Focus:
Windows 10 and 11. This should be our main goal to fully support.
Limited support / Legacy Version
Windows 8.1, and windows 7 with latest service packs.
Here the approach would be best to have a best effort.
No support:
Windows Vista, Windows XP
These are definitly eol.
Currently the installer is win10, I dont think it is a big deal to
downgrade it to win7.
AOO itself is currently still winxp/2k API. I have code to push to
win10, but not for win7.
What i dont know is how to deal with our Languages. Should i check if we
could pimp the installer?
You download one multilanguage installer, AOO version is always us-en.
And the installer offers a language picker, which downloads the language
file and installs the selected ones.
would save us a lot of release space.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Windows x86 and Windows x64 (WAS Re: compile trunk with modern windows build tools)
Posted by Marcus <ma...@wtnet.de>.
Am 29.08.26 um 09:54 schrieb Petko@apache.org:
> I would then merge this into trunk. we have some substantial gains.
>
> Am 29.08.2026 um 00:48 schrieb Pedro Lino via dev:
>>> On 08/28/2026 3:46 PM WEST petko@apache.org wrote:
>>>> 1) The x64 build will not install on Windows 7 (asks for 10 or later)
>>> yes sorry my error. floor has been set on win10.
>>>> Do we know users that want win7?
>> I would expect that quite a few OpenOffice users are still on Windows
>> 7. According to estimates there are still around 1-2% of Windows users
>> on Windows 7 (more than on 8 and 8.1 combined) which converts to
>> around 12-24 million Win 7 users worldwide.
>> But the honest answer is, I don't know anyone who still uses Windows 7...
> I would like to discuss this in a different discussion. So its not
> hidden in test builds, but a popper discussion.
I hope you don't mind when I start. ;-)
We are on the way the switch from 32-bit to 64-bit on the Windows
platform. Therefore it is the normal way to provide both versions for a
- yes, still to be discussed - time frame.
Or in other words it would not be a smart idea to make a big bang switch
to 64-bit without an alternative. It is still the most used platform for
AOO by far.
My 2 ct.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pe...@apache.org.
Thanks Czeslaw, Pedro,
I would then merge this into trunk. we have some substantial gains.
Am 29.08.2026 um 00:48 schrieb Pedro Lino via dev:
> Hi Peter
>
>> On 08/28/2026 3:46 PM WEST petko@apache.org wrote:
>>> 1) The x64 build will not install on Windows 7 (asks for 10 or later)
>> yes sorry my error. floor has been set on win10.
>>> Do we know users that want win7?
> I would expect that quite a few OpenOffice users are still on Windows 7. According to estimates there are still around 1-2% of Windows users on Windows 7 (more than on 8 and 8.1 combined) which converts to around 12-24 million Win 7 users worldwide.
> But the honest answer is, I don't know anyone who still uses Windows 7...
I would like to discuss this in a different discussion. So its not
hidden in test builds, but a popper discussion.
>
>>> 2) The x86 runs on Windows 7 but the python script fails with
>>> OpenOffice 4.5.0 - Fatal Error
>>> ProviderCache::createProvider() Error creating provider from
>>> factory!!!loading component library failed:
>>> file//C:/Program?%20Files%20(86)/OpenOfice%:204/program/../progr
>>> am/pythonloader.uno.dll
> Maybe this one is fixed too? Can you please compile a newer x86 installer?
>
> All the best,
> Pedro
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pedro Lino via dev <de...@openoffice.apache.org>.
Hi Peter
> On 08/28/2026 3:46 PM WEST petko@apache.org wrote:
> I have uploaded a new test version.
Thank you!
> > 3) "The scripting language Python is not supported"
> fixed, in python 3 packages packages were added. Python uno handler run
> on error, and
Confirmed fixed. At least for the example file I used it is working without issues.
> > 4) Can not install x86 extensions (obviously)
> we could add something that works for 32bit file load or backend porcesses.
> But it will not work for gui- not sure if we should support this.
> Maybe it would be more strategic to be compatible to LO?
Yes, that would make a lot of sense.
> > 5) Some other files cause crashes (odg, odp in addition to ppt)
> still open.
Actually all crashes are now fixed. Even the long standing PPT problem.
> > 1) The x64 build will not install on Windows 7 (asks for 10 or later)
> yes sorry my error. floor has been set on win10.
>> Do we know users that want win7?
I would expect that quite a few OpenOffice users are still on Windows 7. According to estimates there are still around 1-2% of Windows users on Windows 7 (more than on 8 and 8.1 combined) which converts to around 12-24 million Win 7 users worldwide.
But the honest answer is, I don't know anyone who still uses Windows 7...
> > 2) The x86 runs on Windows 7 but the python script fails with
> > OpenOffice 4.5.0 - Fatal Error
> > ProviderCache::createProvider() Error creating provider from
> > factory!!!loading component library failed:
> > file//C:/Program?%20Files%20(86)/OpenOfice%:204/program/../progr
> > am/pythonloader.uno.dll
Maybe this one is fixed too? Can you please compile a newer x86 installer?
All the best,
Pedro
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pe...@apache.org.
Hello all,
I have uploaded a new testversion.
https://drive.google.com/file/d/1Ual6x5omeiIKPjhflhQWOUe492wRQ_kn/view?usp=sharing
> 1.
> It is not possible to add object to the Gallery or insert object from it using the mouse. The mouse pointer changes to "Unavailable".
fixed, the win API switched to v6, we support in the code 5.2. For now
we went back on 5.2.
Renewal to newer API is still open in total.
>
> 2.
> In Draw insert an object from the Gallery (via context menu: Insert ⟶ Copy) and
> delete/cut the object. Result: crash
fixed, pointer were only 32bit long.
> 3) "The scripting language Python is not supported"
fixed, in python 3 packages packages were added. Python uno handler run
on error, and
reported not supported. All packages that the uno handler expects are
added now.
following packages are missing:
- _ctypes → import ctypes fails. Needs libffi. Biggest practical gap for
macro authors — ctypes is how Python macros reach Win32.
- _ssl (and _hashlib) → import ssl fails; hashlib works but only with
the built-in md5/sha implementations, no OpenSSL algorithms. Needs OpenSSL.
- _sqlite3 → import sqlite3 fails.
- _bz2, _lzma → those compressors unavailable. zlib is statically in
python311.dll, so zipfile/gzip are fine.
- _curses → n/a on Windows.
- _tkinter → needs tcl/tk.
The d.lst comment currently claims only _ssl, _ctypes and _testcapi are
absent on purpose; _sqlite3, _bz2 and _lzma are absent too and unmentioned.
- msilib — a real inconsistency: _msi.pyd is delivered, the package
wrapping it is not.
- venv (+ venv/scripts/{common,nt,posix}) and ensurepip (+ _bundled,
holding the pip 24.0 and setuptools 79.0.1 wheels) — no pip / python -m
venv in the office Python. Deliberate or not, it's undocumented.
- tkinter, turtledemo — moot, _tkinter isn't built.
- __phello__ — frozen-import test fixture, irrelevant.
The following are missing too. And can simply be added:
┌─────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ module │ consequence │
├─────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ _overlapped.pyd │ import asyncio fails outright — asyncio/__init__.py
→ windows_events → import _overlapped, unconditional on Windows. The │
│ │ asyncio package is delivered, so this is exactly the
collections failure again, one release later. │
├─────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ _decimal.pyd │ decimal silently falls back to _pydecimal — works,
~100× slower │
├─────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ _asyncio.pyd │ C Task/Future accelerator; optional (try/except in
tasks.py) │
├─────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ _queue.pyd │ SimpleQueue accelerator; optional │
├─────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ _uuid.pyd │ uuid falls back to the pure path │
├─────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ _zoneinfo.pyd │ zoneinfo falls back to zoneinfo._zoneinfo
│
└─────────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
> 4) Can not install x86 extensions (obviously)
we could add something that works for 32bit file load or backend porcesses.
But it will not work for gui- not sure if we should support this.
Maybe it would be more strategic to be compatible to LO?
> 5) Some other files cause crashes (odg, odp in addition to ppt)
still open.
Am 28.08.2026 um 12:09 schrieb Pedro Lino via dev:
> Hi Peter
>
> Some new results from your modern builds
>
> 1) The x64 build will not install on Windows 7 (asks for 10 or later)
yes sorry my error. floor has been set on win10. Do we know users that
want win7?
>
> 2) The x86 runs on Windows 7 but the python script fails with
> OpenOffice 4.5.0 - Fatal Error
> ProviderCache::createProvider() Error creating provider from
> factory!!!loading component library failed:
> file//C:/Program?%20Files%20(86)/OpenOfice%:204/program/../progr
> am/pythonloader.uno.dll
>
> All the best,
> Pedro
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pedro Lino via dev <de...@openoffice.apache.org>.
Hi Peter
Some new results from your modern builds
1) The x64 build will not install on Windows 7 (asks for 10 or later)
2) The x86 runs on Windows 7 but the python script fails with
OpenOffice 4.5.0 - Fatal Error
ProviderCache::createProvider() Error creating provider from
factory!!!loading component library failed:
file//C:/Program?%20Files%20(86)/OpenOfice%:204/program/../progr
am/pythonloader.uno.dll
All the best,
Pedro
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pe...@apache.org.
Am 26.08.2026 um 01:10 schrieb Pedro Lino via dev:
> Hi Peter
>
> Excellent progress. As expected new features and new bugs ;)
>
>> On 08/25/2026 7:53 PM WESTpetko@apache.org wrote:
>> 1) now the OfficeDialogs are used if the option is ticked
> Confirmed fixed
>
>> 2) java is now detected automatically
> Confirmed fixed
>
>> 4) AOO installs now in program files and not in program files (x86)
> Confirmed fixed
>
>> I think that is all. What i have for now.
> Some new problems as a consequence of switching to 64bit:
>
> 1) "The scripting language Python is not supported"
ok, Identified the issue, fix is ready.
>
> 2) Can not install x86 extensions (obviously)
> e.g.
> https://www.arielch.org/aoo/aoo-pdf-import/
this is the reason I opted for AOO5 instead of AOO42.
We can look into this later.
>
> 3) Some other files cause crashes (odg, odp in addition to ppt)
My odp, odg files open fine. Can you send me the file that fail on your
end?
>
> It seems to be faster when loading the program and heavy spreadsheets but maybe it is just my imagination :)
>
> All the best,
> Pedro
No, fresh dev build pushed for testing.
All the best
Peter
Re: compile trunk with modern windows build tools
Posted by Pedro Lino via dev <de...@openoffice.apache.org>.
Hi Peter
Excellent progress. As expected new features and new bugs ;)
> On 08/25/2026 7:53 PM WEST petko@apache.org wrote:
> 1) now the OfficeDialogs are used if the option is ticked
Confirmed fixed
> 2) java is now detected automatically
Confirmed fixed
> 4) AOO installs now in program files and not in program files (x86)
Confirmed fixed
> I think that is all. What i have for now.
Some new problems as a consequence of switching to 64bit:
1) "The scripting language Python is not supported"
2) Can not install x86 extensions (obviously)
e.g.
https://www.arielch.org/aoo/aoo-pdf-import/
3) Some other files cause crashes (odg, odp in addition to ppt)
It seems to be faster when loading the program and heavy spreadsheets but maybe it is just my imagination :)
All the best,
Pedro
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pe...@apache.org.
Hi all,
uploaded a new testbuild of win64.
1) now the OfficeDialogs are used if the option is ticked
2) java is now detected automatically
3) meta.xml adjusted
4) AOO installs now in program files and not in program files (x86)
5) setup.exe is now x64 too.
6) If the machine is a clean windows, install does not fail anymore
since the installer expected some old libs.
7) removed the custom 32 bit gdiplus.dll we added. The windows x64 has
been used before. so this is more a cleanup. Thus the installer is a
little smaler.
I think that is all. What i have for now.
Link for testing:
https://drive.google.com/drive/folders/0B0-to9zwOIz0X2J4VUtIN2g4MWc?resourcekey=0-qgDodWaeltkAJTPJN9Jfbw&usp=sharing
Am 23.08.2026 um 17:59 schrieb Czesław Wolański:
> Hi Peter, all
>
> Thanks for your 64-bit build.
> I ran it on Windows 11 and so far, I haven't experienced any crashes / data loss
> (it might be the calm before the storm…).
>
> Worth noting (?):
>
> 1.
> OpenOffice dialogs are used, even though "Use OpenOffice dialogs"
> (under Tools ⟶ Options ⟶ OpenOffice ⟶ General) is not selected.
>
> 2.
> The build doesn't automatically detect Java
> (Tools ⟶ Options ⟶ OpenOffice ⟶ Java).
>
> 3.
> The entry in meta.xml file says:
> "OpenOffice/4.5.0$Win32 OpenOffice.org_project/450m1$Build-9900"
>
> Should it be "Win32"?
>
>
> Best regards,
> Czesław
>
> On 2026/08/22 21:58:56 Petko@apache.org wrote:
>> hello all
>>
>> here is the test result for the 64 bit run. (untested on my side.)
>>
>> https://drive.google.com/file/d/13kdOdTrWSjqVgiw3653EAHNCMdNro6bf/view?usp=sharing
>>
>> i updated the permissions. You should now need only the link to download
>> the installer.
>> Again this is a test build, don't use it in your day to day work.
>>
>> If you test please test files with macros, or other uno components
>> (setup a database maybe?)
>>
>> for completeness if one wants to test the 32bit:
>>
>> https://drive.google.com/file/d/17tVA-bySthjLvJr4HmfW3ys9ALOotrTG/view?usp=sharing
>>
>> both will not install in parallel. (if you bild the filename will be
>> wrong. but i need to checkin and push.
>>
>> all the best
>>
>> peter
>>
>> Am 22.08.2026 um 09:04 schrieb Petko@apache.org:
>>> Hi all,
>>>
>>> Am 21.08.2026 um 18:12 schrieb Pedro Lino via dev:
>>>>> sorry the spam. its 32bit -.- forgot to change the switch.
>>>> Please feel free to upload the 64bit build to the same folder when it
>>>> is finished!
>>>> (I'm particularly curious to run a Win x64 build of AOO!)
>>> Win64 has bugs, need fixing. All are done on bazel differenly so the
>>> port is of little help.
>>>
>>> All the best
>>>
>>> Peter
>>>
>>>> Thank you in advance!
>>>>
>>>> All the best,
>>>> Pedro
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail:dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail:dev-help@openoffice.apache.org
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Peter Kovacs <le...@posteo.de>.
Hi Czeslaw,
Am 23. August 2026 17:59:23 MESZ schrieb "Czesław Wolański" <cw...@apache.org>:
>Hi Peter, all
>
>Thanks for your 64-bit build.
Thanks for your testing work!
>I ran it on Windows 11 and so far, I haven't experienced any crashes / data loss
>(it might be the calm before the storm…).
The data loss bug is still there.
The issue is if you write a large file.
( Really large) Then AOO will report that the file is saved while the OS is still busy.
And if you close AOO this result in the data loss.
You can do this of course with small amount of data and limit the write speed to disk somehow
>
>Worth noting (?):
Ahh thanks. This are good hints to check them.
I am already on the naming topic, since the installer I renamed by hand.
>
>1.
>OpenOffice dialogs are used, even though "Use OpenOffice dialogs"
>(under Tools ⟶ Options ⟶ OpenOffice ⟶ General) is not selected.
>
>2.
>The build doesn't automatically detect Java
>(Tools ⟶ Options ⟶ OpenOffice ⟶ Java).
>
>3.
>The entry in meta.xml file says:
>"OpenOffice/4.5.0$Win32 OpenOffice.org_project/450m1$Build-9900"
>
>Should it be "Win32"?
>
>
>Best regards,
>Czesław
Great that it works too.
All the best
Peter
>
>On 2026/08/22 21:58:56 Petko@apache.org wrote:
>> hello all
>>
>> here is the test result for the 64 bit run. (untested on my side.)
>>
>> https://drive.google.com/file/d/13kdOdTrWSjqVgiw3653EAHNCMdNro6bf/view?usp=sharing
>>
>> i updated the permissions. You should now need only the link to download
>> the installer.
>> Again this is a test build, don't use it in your day to day work.
>>
>> If you test please test files with macros, or other uno components
>> (setup a database maybe?)
>>
>> for completeness if one wants to test the 32bit:
>>
>> https://drive.google.com/file/d/17tVA-bySthjLvJr4HmfW3ys9ALOotrTG/view?usp=sharing
>>
>> both will not install in parallel. (if you bild the filename will be
>> wrong. but i need to checkin and push.
>>
>> all the best
>>
>> peter
>>
>> Am 22.08.2026 um 09:04 schrieb Petko@apache.org:
>> > Hi all,
>> >
>> > Am 21.08.2026 um 18:12 schrieb Pedro Lino via dev:
>> >>> sorry the spam. its 32bit -.- forgot to change the switch.
>> >> Please feel free to upload the 64bit build to the same folder when it
>> >> is finished!
>> >> (I'm particularly curious to run a Win x64 build of AOO!)
>> > Win64 has bugs, need fixing. All are done on bazel differenly so the
>> > port is of little help.
>> >
>> > All the best
>> >
>> > Peter
>> >
>> >>
>> >> Thank you in advance!
>> >>
>> >> All the best,
>> >> Pedro
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail:dev-unsubscribe@openoffice.apache.org
>> >> For additional commands, e-mail:dev-help@openoffice.apache.org
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Czesław Wolański <cw...@apache.org>.
Hi Peter, all
Thanks for your 64-bit build.
I ran it on Windows 11 and so far, I haven't experienced any crashes / data loss
(it might be the calm before the storm…).
Worth noting (?):
1.
OpenOffice dialogs are used, even though "Use OpenOffice dialogs"
(under Tools ⟶ Options ⟶ OpenOffice ⟶ General) is not selected.
2.
The build doesn't automatically detect Java
(Tools ⟶ Options ⟶ OpenOffice ⟶ Java).
3.
The entry in meta.xml file says:
"OpenOffice/4.5.0$Win32 OpenOffice.org_project/450m1$Build-9900"
Should it be "Win32"?
Best regards,
Czesław
On 2026/08/22 21:58:56 Petko@apache.org wrote:
> hello all
>
> here is the test result for the 64 bit run. (untested on my side.)
>
> https://drive.google.com/file/d/13kdOdTrWSjqVgiw3653EAHNCMdNro6bf/view?usp=sharing
>
> i updated the permissions. You should now need only the link to download
> the installer.
> Again this is a test build, don't use it in your day to day work.
>
> If you test please test files with macros, or other uno components
> (setup a database maybe?)
>
> for completeness if one wants to test the 32bit:
>
> https://drive.google.com/file/d/17tVA-bySthjLvJr4HmfW3ys9ALOotrTG/view?usp=sharing
>
> both will not install in parallel. (if you bild the filename will be
> wrong. but i need to checkin and push.
>
> all the best
>
> peter
>
> Am 22.08.2026 um 09:04 schrieb Petko@apache.org:
> > Hi all,
> >
> > Am 21.08.2026 um 18:12 schrieb Pedro Lino via dev:
> >>> sorry the spam. its 32bit -.- forgot to change the switch.
> >> Please feel free to upload the 64bit build to the same folder when it
> >> is finished!
> >> (I'm particularly curious to run a Win x64 build of AOO!)
> > Win64 has bugs, need fixing. All are done on bazel differenly so the
> > port is of little help.
> >
> > All the best
> >
> > Peter
> >
> >>
> >> Thank you in advance!
> >>
> >> All the best,
> >> Pedro
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail:dev-unsubscribe@openoffice.apache.org
> >> For additional commands, e-mail:dev-help@openoffice.apache.org
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pe...@apache.org.
hello all
here is the test result for the 64 bit run. (untested on my side.)
https://drive.google.com/file/d/13kdOdTrWSjqVgiw3653EAHNCMdNro6bf/view?usp=sharing
i updated the permissions. You should now need only the link to download
the installer.
Again this is a test build, don't use it in your day to day work.
If you test please test files with macros, or other uno components
(setup a database maybe?)
for completeness if one wants to test the 32bit:
https://drive.google.com/file/d/17tVA-bySthjLvJr4HmfW3ys9ALOotrTG/view?usp=sharing
both will not install in parallel. (if you bild the filename will be
wrong. but i need to checkin and push.
all the best
peter
Am 22.08.2026 um 09:04 schrieb Petko@apache.org:
> Hi all,
>
> Am 21.08.2026 um 18:12 schrieb Pedro Lino via dev:
>>> sorry the spam. its 32bit -.- forgot to change the switch.
>> Please feel free to upload the 64bit build to the same folder when it
>> is finished!
>> (I'm particularly curious to run a Win x64 build of AOO!)
> Win64 has bugs, need fixing. All are done on bazel differenly so the
> port is of little help.
>
> All the best
>
> Peter
>
>>
>> Thank you in advance!
>>
>> All the best,
>> Pedro
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail:dev-help@openoffice.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pedro Lino via dev <de...@openoffice.apache.org>.
Hi Peter
> On 08/22/2026 8:04 AM WEST petko@apache.org wrote:
> Win64 has bugs, need fixing. All are done on bazel differenly so the
> port is of little help.
Thank you for the update!
I ran your 32bit build under Windows 10 Pro and did my usual tests (opening all file types, files on shared drives, Webdav, creating new documents, etc) and everything worked smoothly!
The only blocker/regression (I am aware of) is the old https://bz.apache.org/ooo/show_bug.cgi?id=127783
Thank you for your efforts!
All the best,
Pedro
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pe...@apache.org.
Hi all,
Am 21.08.2026 um 18:12 schrieb Pedro Lino via dev:
>> sorry the spam. its 32bit -.- forgot to change the switch.
> Please feel free to upload the 64bit build to the same folder when it is finished!
> (I'm particularly curious to run a Win x64 build of AOO!)
Win64 has bugs, need fixing. All are done on bazel differenly so the
port is of little help.
All the best
Peter
>
> Thank you in advance!
>
> All the best,
> Pedro
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail:dev-help@openoffice.apache.org
>
Re: compile trunk with modern windows build tools
Posted by Pedro Lino via dev <de...@openoffice.apache.org>.
Hi again
> On 08/21/2026 4:26 PM WEST petko@apache.org wrote:
> > this is for testing only. High risk something is wrong.
Thank you for the warning :)
> >>> I assume this is still the 32bit version, right?
> sorry the spam. its 32bit -.- forgot to change the switch.
Please feel free to upload the 64bit build to the same folder when it is finished!
(I'm particularly curious to run a Win x64 build of AOO!)
Thank you in advance!
All the best,
Pedro
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pe...@apache.org.
Am 21.08.2026 um 17:24 schrieb Petko@apache.org:
> https://drive.google.com/file/d/17tVA-bySthjLvJr4HmfW3ys9ALOotrTG/view?usp=drive_link
>
>
> this is for testing only. High risk something is wrong.
>
> Am 21.08.2026 um 17:21 schrieb Petko@apache.org:
>>
>> Am 21.08.2026 um 17:19 schrieb Pedro Lino via dev:
>>> Hi Peter
>>>
>>> Thank you for your persistence and for sharing your results!
>>>
>>>> On 08/21/2026 3:52 PM WEST petko@apache.org wrote:
>>>> I can upload my AOO45 installer if testers want to check out (only
>>>> english language compiled sorry, i can compile other languages
>>>> available
>>>> as sdfs.)
>>> Please do share the installer. I will give it a spin under Windows
>>> 10 Pro
>>> I assume this is still the 32bit version, right?
>> no 64 bit.
sorry the spam. its 32bit -.- forgot to change the switch.
>>> Thank you!
>>>
>>> All the best,
>>> Pedro
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pe...@apache.org.
https://drive.google.com/file/d/17tVA-bySthjLvJr4HmfW3ys9ALOotrTG/view?usp=drive_link
this is for testing only. High risk something is wrong.
Am 21.08.2026 um 17:21 schrieb Petko@apache.org:
>
> Am 21.08.2026 um 17:19 schrieb Pedro Lino via dev:
>> Hi Peter
>>
>> Thank you for your persistence and for sharing your results!
>>
>>> On 08/21/2026 3:52 PM WEST petko@apache.org wrote:
>>> I can upload my AOO45 installer if testers want to check out (only
>>> english language compiled sorry, i can compile other languages
>>> available
>>> as sdfs.)
>> Please do share the installer. I will give it a spin under Windows 10
>> Pro
>> I assume this is still the 32bit version, right?
> no 64 bit.
>> Thank you!
>>
>> All the best,
>> Pedro
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pe...@apache.org.
Am 21.08.2026 um 17:19 schrieb Pedro Lino via dev:
> Hi Peter
>
> Thank you for your persistence and for sharing your results!
>
>> On 08/21/2026 3:52 PM WEST petko@apache.org wrote:
>> I can upload my AOO45 installer if testers want to check out (only
>> english language compiled sorry, i can compile other languages available
>> as sdfs.)
> Please do share the installer. I will give it a spin under Windows 10 Pro
> I assume this is still the 32bit version, right?
no 64 bit.
> Thank you!
>
> All the best,
> Pedro
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: compile trunk with modern windows build tools
Posted by Pedro Lino via dev <de...@openoffice.apache.org>.
Hi Peter
Thank you for your persistence and for sharing your results!
> On 08/21/2026 3:52 PM WEST petko@apache.org wrote:
> I can upload my AOO45 installer if testers want to check out (only
> english language compiled sorry, i can compile other languages available
> as sdfs.)
Please do share the installer. I will give it a spin under Windows 10 Pro
I assume this is still the 32bit version, right?
Thank you!
All the best,
Pedro
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org