> On 17 Jan 2022, at 18:19, Philippe Mathieu-Daudé wrote:
>
> The consensus was UI should not be addressed within QEMU itself, but
> via an external helper, eventually using D-Bus. D-Bus support has been
> recently merged:
> https://www.qemu.org/docs/master/interop/dbus.html
Thank you for the
> On 17 Jan 2022, at 15:30, Liviu Ionescu wrote:
>
> I will try to rebuild using --with-cocoa on newer systems, to validate the
> rest of the build.
I confirm that after reverting to --with-cocoa, both Intel and Apple Silicon
builds are able to emulate Thomas' vexpress-a9 project.
However
+Markus/Daniel/Marc-Andre
On 17/1/22 17:07, Liviu Ionescu wrote:
On 17 Jan 2022, at 16:06, Peter Maydell wrote:
This is newer versions of macOS being stricter about enforcing that
some operations are only permitted on the correct thread. Older versions
let QEMU/SDL get away with doing them on
> On 17 Jan 2022, at 16:06, Peter Maydell wrote:
>
> This is newer versions of macOS being stricter about enforcing that
> some operations are only permitted on the correct thread. Older versions
> let QEMU/SDL get away with doing them on the "wrong" thread, which
> all happened to work.
Ah,
> On 17 Jan 2022, at 14:51, Liviu Ionescu wrote:
>
> it crashes with ... I can try to investigate, perhaps it is only a small
> mistake somewhere.
I did some new tests, and I confirm that on a macOS 11.6 running on a MacMini
2020 M1 it throws the exception, as shown before, when testing a b
On Mon, 17 Jan 2022 at 12:52, Liviu Ionescu wrote:
>
> Then perhaps it is a misunderstanding from my part, if I try to start the
> vexpress-a9 machine using the line copied from Thomas' presentation, the
> console shows, it prints "Guest has not initialized the display yet" using
> the PC-like
> On 17 Jan 2022, at 13:35, Peter Maydell wrote:
>
> (2) the "use SDL" option seems to have worked for at least
> some people in the past:
SDL worked nicely for me too in the past, qemu-system-gnuarmeclipse was
configured with SDL for all platforms and it worked unchanged in the last 4-5
yea
> On 17 Jan 2022, at 13:35, Peter Maydell wrote:
>
> ... the macOS host support in QEMU is not very well
> maintained, so the default is "it doesn't change"
BTW, my main development platform is macOS, both Intel and Apple Silicon, so if
someone is willing to improve macOS host support in QEM
On Mon, 17 Jan 2022 at 11:21, Liviu Ionescu wrote:
> I did not check the implementation details, but if Cocoa is
> mandatory when building on macOS, why is it even allowed to
> choose SDL during configure?
Because (1) the macOS host support in QEMU is not very well
maintained, so the default is "
> On 17 Jan 2022, at 11:41, Thomas Huth wrote:
>
> On 10/01/2022 11.33, Liviu Ionescu wrote:
>> I now have successful builds on all platforms, including on macOS 11 with
>> Apple Silicon and macOS 10.13 with Intel, but I had to disable Cocoa
>> support, and enable SDL support.
>> The resulti
On 10/01/2022 11.33, Liviu Ionescu wrote:
I now have successful builds on all platforms, including on macOS 11 with Apple
Silicon and macOS 10.13 with Intel, but I had to disable Cocoa support, and
enable SDL support.
The resulting binaries (qemu-system-arm/aarch64/riscv32/riscv64) start, but
> On 10 Jan 2022, at 12:44, Peter Maydell wrote:
>
> ... On Linux this tends to take the form
> of dropping support for older versions of various dependencies
> and compilers.
My build environment uses modern tools (like GCC 11, etc), but compiled from
sources on an older Linux release.
The
On Fri, 7 Jan 2022 at 23:47, Liviu Ionescu wrote:
>
>
>
> > On 8 Jan 2022, at 00:16, Peter Maydell wrote:
> >
> > ... In this
> > specific case, NSPasteboardTypeOwner seems to be part of
> > an API introduced in 10.14 (Mojave).
>
> Thank you for the details, this explains the error.
>
> > So the
I now have successful builds on all platforms, including on macOS 11 with Apple
Silicon and macOS 10.13 with Intel, but I had to disable Cocoa support, and
enable SDL support.
The resulting binaries (qemu-system-arm/aarch64/riscv32/riscv64) start, but I
could not tell if the lack of Cocoa in th
> On 8 Jan 2022, at 00:16, Peter Maydell wrote:
>
> ... In this
> specific case, NSPasteboardTypeOwner seems to be part of
> an API introduced in 10.14 (Mojave).
Thank you for the details, this explains the error.
> So the upstream answer, I'm afraid, is that you should
> upgrade to a newer
On Fri, 7 Jan 2022 at 21:56, Liviu Ionescu wrote:
> I'm building 6.2.0 on macOS, and on a recent macOS 11.6 with
> Apple Silicon the build passes, but on a slightly older macOS
> 10.13, which is my base platform for Intel macOS builds,
> compiling ui/cocoa.m fails
QEMU's supported-hosts policy
ht
Hi,
I'm building 6.2.0 on macOS, and on a recent macOS 11.6 with Apple Silicon the
build passes, but on a slightly older macOS 10.13, which is my base platform
for Intel macOS builds, compiling ui/cocoa.m fails:
```
../../sources/qemu-6.2.0.git/ui/cocoa.m:1766:52: error: unknown type name
'NSP
17 matches
Mail list logo
