Build is failing: meson.build:1:0: ERROR: Meson version is 1.0.0 but project requires >= 1.2.0

[Fredyy90]

Hey,

I just cloned the repo and tried to build it, but during building the docker container i run into an error:

38.40 patching file gobject/gtypemodule.c
38.40 patching file gobject/gtypemodule.h
38.69 The Meson build system
38.69 Version: 1.0.0
38.69 Source dir: /src/deps/glib
38.69 Build dir: /src/deps/glib/_build
38.69 Build type: cross build
38.69
38.69 meson.build:1:0: ERROR: Meson version is 1.0.0 but project requires >= 1.2.0
38.69
38.69 A full log can be found at /src/deps/glib/_build/meson-logs/meson-log.txt
------
Dockerfile.base:34
--------------------
  32 |         python3-pip \
  33 |        && pip3 install git+https://github.com/kleisauke/meson@wasm-vips
  34 | >>> RUN chmod +x build.sh; ./build.sh
  35 |
  36 |
--------------------
ERROR: failed to solve: process "/bin/sh -c chmod +x build.sh; ./build.sh" did not complete successfully: exit code: 1
make: *** [Makefile:46: .base-image.make] Error 1```

Is there any simple way to fix this?

[DSchroer]

One thing you could try is in Dockerfile.base replace pip3 install git+https://github.com/kleisauke/meson@wasm-vips with pip3 install git+https://github.com/mesonbuild/meson. It could be that it will work out of the box now.

[MathieuLescure]

Thanks, I experienced the same issue and your suggestion allowed me to go one step further. A new error occurred and I had to also install "packaging" to fix it : pip3 install packaging git+https://github.com/mesonbuild/meson.

Unfortunately, I'm still not able to build on a Mac with an M2 CPU: The first problem is due to an architecture mismatch, and so Docker tries to pull openscad-base from the remote even if the image exists locally (but for AMD64) stackoverflow

It can be solved by adding --platform linux/amd64 to the docker run and docker build commands in the Makefile. But then new errors show. I've tried many things but without success.

[GhostDog98]

Unfortunately, I'm still not able to build on a Mac with an M2 CPU

I've experienced this on a linux desktop, mac, and windows host (WSL2, with intel cpu)... Is there an eta on a fix for this?

[t-paul]

Build process is updated via #20, so this should be solved now.