Hi Arrigo, All,

Am 14.12.24 um 09:58 schrieb Arrigo Marchiori:
Dear All,

On Tue, Dec 10, 2024 at 12:08:50PM -0800, Dave Fisher wrote:

On Dec 10, 2024, at 4:44 AM, Jim Jagielski <j...@jagunet.com> wrote:



On Dec 10, 2024, at 3:42 AM, Gavin McDonald <gmcdon...@apache.org> wrote:

Hi

On Tue, Dec 10, 2024 at 2:47 AM Keith McKenna
<keith.mcke...@comcast.net.invalid <mailto:keith.mcke...@comcast.net.invalid>> 
wrote:
Marcus wrote:
Am 09.12.24 um 13:02 schrieb Jim Jagielski:
I'm upgrading my home system which means that the environment that we
use for our community builds for macOS and Linux will be changing.
Since it's been awhile since we've done any test releases, should we
check that we all can still do them as well as maybe see what still is
holding us up for any official releases?
for me it makes sense to test if building is still possible and that the
results are the same than before. Otherwise it has to be adjusted to get
the same results compared to the previous setup.

Marcus
I agree.

I think you are both missing the point, if not, then I am.

Jim is changing *his* environment. Yours should not change, so
certainly it should still build
as before one would hope.

Jim would like to clarify that everyone who builds, can still build
now, so that Jim has a reference
point to expect on his new environment,

as I said, I may have read it wrong ...

Nope. You got it 100% right.
I am long on macOS laptops and have two where I’d like to see if I can 
configure OpenOffice Mac builds. Both are 2020 vintage with more modern macOS. 
One is intel and the other has an M1 chip.

If you would carefully track your re-configuration steps then I’ll repeat.
We have a shared Mac Mini instance on which I can build AOO41X.
Trunk does not build there, due to different XCode etc.

$ uname -a
Darwin administrators-Mac-mini.local 19.6.0 Darwin Kernel Version 19.6.0: Tue 
Jun 21 21:18:39 PDT 2022; root:xnu-6153.141.66~1/RELEASE_X86_64 x86_64

That corresponds to macOS 10.15.6 beta 2 (Catalina).

In addition to the steps in the building guide, I have to set certain
environment variables in order to get XCode working properly: PATH,
SDKROOT, CFLAGS, etc.

I am not sure we can consider builds from that computer good for
general public. It is newer than our "reference build system" at [1]
and for this reason its output may not be compatible with older macOS
versions.

WRT Linux: I have a VM configured same as our reference system [2] and
I can share it with anyone interested.
(Getting such a VM ready today is challenging due to TLS protocol
obsolescence)

WRT Windows: Matthias and I both have VM's that should be able to
build both AOO41X and trunk.

Yes, I do Windows builds for AOO41X and AOO42X on a regular base. [1]

So +1 for doing test builds to ensure we are also able to build for macOS and Linux. This is most important for AOO41X, which is the only branch we can release.

Personally, I don't see a use for another *Dev Build*, because there is really not much difference to see and we are still not able to update our translation files.

Matthias

[1] https://drive.google.com/drive/folders/1ZVxRW0xIoXEnRQqB40-9zAmMy8ooOcQI


1: 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_MacOsX#Reference_Build_System

2: 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step_Linux#CentOS_5_for_AOO_4.1.x

Attachment: smime.p7s
Description: Kryptografische S/MIME-Signatur

Reply via email to