Message ID | 1525376963-79623-24-git-send-email-mst@redhat.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Hello,
Michael S. Tsirkin, le jeu. 03 mai 2018 22:51:01 +0300, a ecrit:
> +#include_next "../slirp/ip6.h"
Mmm, this is the first time #include_next would be used in qemu, and I
don't think this is a standard thing...
Samuel
On Thu, May 31, 2018 at 08:50:32PM +0200, Samuel Thibault wrote: > Hello, > > Michael S. Tsirkin, le jeu. 03 mai 2018 22:51:01 +0300, a ecrit: > > +#include_next "../slirp/ip6.h" > > Mmm, this is the first time #include_next would be used in qemu, and I > don't think this is a standard thing... > > Samuel Well we don't support arbitrary compilers, and gcc and clang both have it. It's also a temporary thing, then intent is for maintainers to drop these after deciding on either code refactoring or just moving header to include.
diff --git a/include/slirp/ip6.h b/include/slirp/ip6.h new file mode 100644 index 0000000..432cc36 --- /dev/null +++ b/include/slirp/ip6.h @@ -0,0 +1 @@ +#include_next "../slirp/ip6.h" diff --git a/include/slirp/libslirp.h b/include/slirp/libslirp.h new file mode 100644 index 0000000..acab168 --- /dev/null +++ b/include/slirp/libslirp.h @@ -0,0 +1 @@ +#include_next "../slirp/libslirp.h" diff --git a/include/slirp/slirp.h b/include/slirp/slirp.h new file mode 100644 index 0000000..826a97d --- /dev/null +++ b/include/slirp/slirp.h @@ -0,0 +1 @@ +#include_next "../slirp/slirp.h"
This way they are easier to find using standard rules. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> --- include/slirp/ip6.h | 1 + include/slirp/libslirp.h | 1 + include/slirp/slirp.h | 1 + 3 files changed, 3 insertions(+) create mode 100644 include/slirp/ip6.h create mode 100644 include/slirp/libslirp.h create mode 100644 include/slirp/slirp.h