From: Daniel Vetter <daniel@ffwll.ch>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: daniel.stone@collabora.com, tomeu.vizoso@collabora.com,
Daniel Vetter <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [RFC i-g-t v3 08/13] lib/stubs: Add stubs for intel_bufmgr.
Date: Wed, 22 Jun 2016 10:12:22 +0200 [thread overview]
Message-ID: <20160622081222.GM23520@phenom.ffwll.local> (raw)
In-Reply-To: <CACvgo53Rg6ZqTCY9Q4JHJAFeg65FLSEdF2MEd6bxBqycoKXtoA@mail.gmail.com>
On Tue, Jun 21, 2016 at 02:41:29PM +0100, Emil Velikov wrote:
> On 21 June 2016 at 13:50, Marius Vlad <marius.c.vlad@intel.com> wrote:
> > On Mon, Jun 20, 2016 at 03:52:35PM +0100, Emil Velikov wrote:
> >> Hi Rob,
> >>
> >> A couple of nitpicks and a case of missing git add :-)
> >>
> >> On 15 June 2016 at 10:51, <robert.foss@collabora.com> wrote:
> >>
> >> > +if HAVE_LIBDRM_INTEL
> >> > +else
> >> > + libintel_tools_la_SOURCES += \
> >> > + stubs/drm/intel_bufmgr.c \
> >> > + stubs/drm/intel_bufmgr.h
> >> > +endif
> >> > +
> >> I believe I mentioned if before - please use the following construct
> >>
> >> if !HAVE_LIBDRM_INTEL
> >> libintel_tools_la_SOURCES += \
> >> stubs/drm/intel_bufmgr.c \
> >> stubs/drm/intel_bufmgr.h
> >> endif
> >>
> >> > AM_CPPFLAGS = -I$(top_srcdir)
> >> > AM_CFLAGS = $(CWARNFLAGS) $(DRM_CFLAGS) $(PCIACCESS_CFLAGS) $(LIBUNWIND_CFLAGS) $(DEBUG_CFLAGS) \
> >> > -DIGT_SRCDIR=\""$(abs_top_srcdir)/tests"\" \
> >> > diff --git a/lib/stubs/drm/README b/lib/stubs/drm/README
> >> > new file mode 100644
> >> > index 0000000..dec6a1d
> >> > --- /dev/null
> >> > +++ b/lib/stubs/drm/README
> >> > @@ -0,0 +1,4 @@
> >> > +intel_bufmgr.h is a copy the file provided in libdrm (intel/intel_bufmgr.h).
> >> > +
> >> s/copy the file provided in/local copy of the file provided by/
> >>
> >> Sadly that's not the case atm. There's a fair few changes in the local 'copy'.
> >> Perhaps you forgot to git add ?
> >>
> >> > +Before releasing i-g-t a current copy of intel_bufmgr.h should be copied into
> >> > +this directory of i-g-t.
> >
> > Auch, but synchronizing this wouldn't be a nightmare? I mean stubs
> > might be added/removed in the future.
> >
> Maybe slightly annoying, but definitely not nightmare. As with any
> other library one _cannot_ remove API without bumping major (and/or
> changing the library name), so things should be fine on that regard.
> Guess one should stress that intel_bufmgr.h should be copied from the
> latest libdrm release and
>
> >>
> >> Thinking about it... I'm not sure that the release manager will find
> >> this note here :-\
> >>
> >> Daniel V, Marius, do you guys have a tick-off list somewhere where
> >> this could be added ?
> >
> > README and NEWS. Don't know of any other.
> >
> Can I ask that you/Daniel can update those ? I'm afraid
Instead of documenting, can't we enforce this with an autobuilder which
runs with the stubbed-out libdrm always? Collabora has such a thing I
heard ;-)
Imo trying to fix up the build for releases is way too late, we should
never have a broken build. Or at least not for long.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-22 8:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 9:50 [RFC i-g-t v3 00/13] Remove compile time depencencies on libdrm_intel robert.foss
2016-06-15 9:50 ` [RFC i-g-t v3 01/13] configure.ac: Test for libdrm_intel and build for it if present robert.foss
2016-06-15 9:50 ` [RFC i-g-t v3 02/13] configure.ac: Harmonize HAVE_XXX flag for all drm platforms to HAVE_LIBDRM_XXX robert.foss
2016-06-15 9:51 ` [RFC i-g-t v3 03/13] Enable HAVE_LIBDRM_INTEL unconditionally for Android robert.foss
2016-06-15 9:51 ` [RFC i-g-t v3 04/13] benchmarks/Makefile: Don't build benchmarks that depend on libdrm_intel robert.foss
2016-06-15 9:51 ` [RFC i-g-t v3 05/13] tools/Makefile: Don't build tools " robert.foss
2016-06-15 9:51 ` [RFC i-g-t v3 06/13] tools/Makefile: Format whitespace robert.foss
2016-06-15 9:51 ` [RFC i-g-t v3 07/13] demos/Makefile: Don't build tools that depend on libdrm_intel robert.foss
2016-06-15 9:51 ` [RFC i-g-t v3 08/13] lib/stubs: Add stubs for intel_bufmgr robert.foss
2016-06-20 14:52 ` Emil Velikov
2016-06-21 12:50 ` Marius Vlad
2016-06-21 13:41 ` Emil Velikov
2016-06-21 13:43 ` Emil Velikov
2016-06-22 8:12 ` Daniel Vetter [this message]
2016-06-22 10:40 ` Tomeu Vizoso
2016-06-22 11:41 ` Daniel Vetter
2016-06-22 12:46 ` Tomeu Vizoso
2016-06-23 0:39 ` Emil Velikov
2016-06-15 9:51 ` [RFC i-g-t v3 09/13] demos/Makefile: Replace automake specific name of listing in Makfile.sources robert.foss
2016-06-15 9:51 ` [RFC i-g-t v3 10/13] benchmarks/Makefile: " robert.foss
2016-06-15 9:51 ` [RFC i-g-t v3 11/13] tools/Makefile: Replace automake specific name of listings " robert.foss
2016-06-15 9:51 ` [RFC i-g-t v3 12/13] lib/tests/Makefile: Replace automake specific names of listings in Makefile.sources robert.foss
2016-06-15 9:51 ` [RFC i-g-t v3 13/13] lib/Makefile: " robert.foss
2016-06-15 13:12 ` [RFC i-g-t v3 00/13] Remove compile time depencencies on libdrm_intel Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160622081222.GM23520@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.stone@collabora.com \
--cc=daniel.vetter@ffwll.ch \
--cc=emil.l.velikov@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tomeu.vizoso@collabora.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox