On Fri, 8 Feb 2019 at 20:58, <marcandre.lur...@redhat.com> wrote: > As discussed earlier in "[PATCH for-3.2 00/41] RFC: slirp: make it > again a standalone project" and other threads, it would be useful to > make slirp a separate project (the submodule approach was discarded) > for various projects to share.
> The following patches add meson build system (if necessary for older > distros, autotools could be added - however I believe python & ninja > are generally available on the QEMU supported platforms) Do you really need to make QEMU add an extra build dependency just to use a different build system? From my end that seems like just unnecessary pain for us (we're going to need to ship libslirp as a submodule for a while until it's been around long enough to be in stable distros, so its build dependencies will get added to QEMU's build deps). Is the standalone project going to provide a shared library or just a .a static library? (ie are you confident enough in the long-term stability of your API and ABI to do the shared library yet? the prudent approach might be to start with just the .a...) thanks -- PMM
