Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] libxkbcommon: add support for interactive-wayland test program
Date: Fri, 10 Mar 2017 20:31:59 +0100	[thread overview]
Message-ID: <20170310203159.2c462296@gmx.net> (raw)
In-Reply-To: <20170309221850.3a6ab20c@free-electrons.com>

Hello Thomas,

On Thu, 9 Mar 2017 22:18:50 +0100, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> Hello,
> 
> On Wed,  8 Mar 2017 22:53:10 +0100, Peter Seiderer wrote:
> 
> > +if BR2_PACKAGE_LIBXKBCOMMON && BR2_PACKAGE_WAYLAND
> > +
> > +config BR2_PACKAGE_LIBXKBCOMMON_INTERACTIVE_WAYLAND
> > +	bool "interactive-wayland"
> > +	select BR2_PACKAGE_WAYLAND_PROTOCOLS
> > +	help
> > +	  interactive-wayland is a wayland test application
> > +	  for libxkbcommon.
> > +
> > +endif
> 
> This looks like a very very specific option. Shouldn't this be instead
> BR2_PACKAGE_LIBXKBCOMMON_INSTALL_TESTS ?

It is specific, did not find a target to build all tests (see below)...

> 
> > +define LIBXKBCOMMON_BUILD_INTERACTIVE_WAYLAND
> > +	$(TARGET_MAKE_ENV) $(MAKE) -C $(@D) test/interactive-wayland
> > +endef
> > +LIBXKBCOMMON_POST_BUILD_HOOKS = LIBXKBCOMMON_BUILD_INTERACTIVE_WAYLAND
> 
> There's already some logic in the build system to build tests. Can't we
> use it instead?

'make test' does nothing, 'make check' builds the tests AND tries (and fails)
to run the test programs...

Regards,
Peter

> 
> Thanks,
> 
> Thomas

      reply	other threads:[~2017-03-10 19:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 21:53 [Buildroot] [PATCH v1] libxkbcommon: add support for interactive-wayland test program Peter Seiderer
2017-03-09 21:18 ` Thomas Petazzoni
2017-03-10 19:31   ` Peter Seiderer [this message]

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=20170310203159.2c462296@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /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