Re: [PATCH 04/10] meson: option to build as shared library

2020-10-14 Thread Joelle van Dyne
Since there seems to be some more push back on this one, I will remove this patch from the v2 submission and submit it as a separate patch -j On Tue, Oct 13, 2020 at 9:40 AM BALATON Zoltan wrote: > > On Tue, 13 Oct 2020, Daniel P. Berrangé wrote: > > On Tue, Oct 13, 2020 at 08:16:46AM -0700,

Re: [PATCH 04/10] meson: option to build as shared library

2020-10-13 Thread BALATON Zoltan via
On Tue, 13 Oct 2020, Daniel P. Berrangé wrote: On Tue, Oct 13, 2020 at 08:16:46AM -0700, Joelle van Dyne wrote: I will start a separate conversation of UTM's license compatibility. Regarding the patch, would some sort of warning message in configure (if building as a shared library) regarding

Re: [PATCH 04/10] meson: option to build as shared library

2020-10-13 Thread Daniel P . Berrangé
On Tue, Oct 13, 2020 at 08:16:46AM -0700, Joelle van Dyne wrote: > I will start a separate conversation of UTM's license compatibility. > > Regarding the patch, would some sort of warning message in configure > (if building as a shared library) regarding the license be wise? Or > would it pollute

Re: [PATCH 04/10] meson: option to build as shared library

2020-10-13 Thread BALATON Zoltan via
On Tue, 13 Oct 2020, Daniel P. Berrangé wrote: On Tue, Oct 13, 2020 at 04:41:06PM +0200, BALATON Zoltan wrote: On Tue, 13 Oct 2020, Daniel P. Berrangé wrote: On Mon, Oct 12, 2020 at 04:29:33PM -0700, Joelle van Dyne wrote: From: osy On iOS, we cannot fork() new processes, so the best way to

Re: [PATCH 04/10] meson: option to build as shared library

2020-10-13 Thread Joelle van Dyne
I will start a separate conversation of UTM's license compatibility. Regarding the patch, would some sort of warning message in configure (if building as a shared library) regarding the license be wise? Or would it pollute the output logs? -j On Tue, Oct 13, 2020 at 7:46 AM Daniel P. Berrangé

Re: [PATCH 04/10] meson: option to build as shared library

2020-10-13 Thread Daniel P . Berrangé
On Tue, Oct 13, 2020 at 04:41:06PM +0200, BALATON Zoltan wrote: > On Tue, 13 Oct 2020, Daniel P. Berrangé wrote: > > On Mon, Oct 12, 2020 at 04:29:33PM -0700, Joelle van Dyne wrote: > > > From: osy > > > > > > On iOS, we cannot fork() new processes, so the best way to load QEMU into > > > an >

Re: [PATCH 04/10] meson: option to build as shared library

2020-10-13 Thread BALATON Zoltan via
On Tue, 13 Oct 2020, Daniel P. Berrangé wrote: On Mon, Oct 12, 2020 at 04:29:33PM -0700, Joelle van Dyne wrote: From: osy On iOS, we cannot fork() new processes, so the best way to load QEMU into an app is through a shared library. We add a new configure option `--enable-shared-lib` that will

Re: [PATCH 04/10] meson: option to build as shared library

2020-10-13 Thread Daniel P . Berrangé
On Mon, Oct 12, 2020 at 04:29:33PM -0700, Joelle van Dyne wrote: > From: osy > > On iOS, we cannot fork() new processes, so the best way to load QEMU into an > app is through a shared library. We add a new configure option > `--enable-shared-lib` that will build the bulk of QEMU into a shared

[PATCH 04/10] meson: option to build as shared library

2020-10-12 Thread Joelle van Dyne
From: osy On iOS, we cannot fork() new processes, so the best way to load QEMU into an app is through a shared library. We add a new configure option `--enable-shared-lib` that will build the bulk of QEMU into a shared lib. The usual executables will then link to the library. Signed-off-by: