Hi Paolo,
I don't know how much of this is
already meant to work, but I run into several issues when compiling the
latest code from the meson-poc-next branch.
However, when I compile the meson-poc-next branch I run into the following error:
hsp@HSP-W10-X64-I7 MINGW64 ~/src/qemu-meson-gitlab/build
$ ../configure --cross-prefix=x86_64-w64-mingw32- --target-list=ppc-softmmu --enable-gtk --enable-sdl
...
Program python3 found: NO
../meson.build:32:0: ERROR: /mingw64/bin/python3 not found
A full log can be found at C:/msys64/home/hsp/src/qemu-meson-gitlab/build/meson-logs/meson-log.txt
ERROR: meson setup failed
2. When cross compiling from Fedora 32 for Windows with
../configure --cross-prefix=x86_64-w64-mingw32- --enable-gtk --enable-sdl --target-list=ppc-softmmu
I get the error below even though the v2 commit message says there is a fix for the absolute path error included:
The Meson build system
Version: 0.55.0
Source dir: /home/hsp/src/qemu-meson-gitlab
Build dir: /home/hsp/src/qemu-meson-gitlab/build
Build type: cross build
../meson.build:1:0: ERROR: prefix value 'c:/Program Files/QEMU' must be an absolute path
A full log can be found at /home/hsp/src/qemu-meson-gitlab/build/meson-logs/meson-log.txt
ERROR: meson setup failed
3. As mentioned earlier here concerning a build on fedora 32 host:
Both SDL and GTK Guis do not seem to work, only the vnc server is started.
4. The v2 patch set seems to not apply cleanly to current qemu-master, I get this error:
patching file docs/devel/build-system.rst (renamed from docs/devel/build-system.txt)
Hunk #2 succeeded at 179 with fuzz 2 (offset 152 lines).
Hunk #3 succeeded at 187 (offset 152 lines).
Hunk #4 FAILED at 53.
Hunk #5 FAILED at 90.
Hunk #6 FAILED at 115.
Hunk #7 FAILED at 183.
Hunk #8 FAILED at 201.
Hunk #9 FAILED at 211.
Hunk #10 FAILED at 222.
Hunk #11 FAILED at 247.
Hunk #12 FAILED at 308.
Hunk #13 FAILED at 356.
Hunk #14 FAILED at 398.
Hunk #15 FAILED at 451.
12 out of 15 hunks FAILED -- saving rejects to file docs/devel/build-system.rst.rej
5:
And one question: Should the compiled binary etc be placed in the build
directory, or should they go into (in my case) the ppc-softmmu folder
as with a default build?
Best,
Howard