[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 0/2] Update libslirp & make it a subproject
From: |
Philippe Mathieu-Daudé |
Subject: |
Re: [PATCH v2 0/2] Update libslirp & make it a subproject |
Date: |
Mon, 8 Mar 2021 11:02:12 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 |
Hi Marc-André,
On 1/25/21 8:34 AM, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Hi,
>
> Here is a few patches to update libslirp to git upstream.
> Since it now supports meson subproject(), adapt the build
> system to use it, and related fixes.
>
> v2:
> - fix unused variables on macos
> - fork_exec_child_setup: improve signal handling
>
> Marc-André Lureau (2):
> slirp: update to git master
> build-sys: make libslirp a meson subproject
>
> configure | 2 +-
> meson.build | 62 +++-----------------------------------------
> .gitmodules | 4 +--
> slirp | 1 -
> subprojects/libslirp | 1 +
> 5 files changed, 8 insertions(+), 62 deletions(-)
> delete mode 160000 slirp
> create mode 160000 subprojects/libslirp
Just out of curiosity, why "subprojects"? Should we move
other submodules there (meson, dtc, keycodemapdb)?
- Re: [PATCH v2 0/2] Update libslirp & make it a subproject,
Philippe Mathieu-Daudé <=