Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] xinput-calibrator: Add a dummy calibration file for qemu
Date: Thu, 17 Sep 2015 17:09:09 +0200	[thread overview]
Message-ID: <20150917150909.GA2380@jama> (raw)
In-Reply-To: <f0b5037b3efdd8498a6499690009aed1c1273315.1442494048.git.jussi.kukkonen@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2202 bytes --]

On Thu, Sep 17, 2015 at 04:00:38PM +0300, Jussi Kukkonen wrote:
> This prevents xinput_calibrator from popping up on every boot in qemu.
> 
> Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
> ---
>  .../xinput-calibrator/pointercal-xinput/pointercal-qemu.xinput      | 2 ++
>  meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb    | 6 ++++++
>  2 files changed, 8 insertions(+)
>  create mode 100644 meta/recipes-graphics/xinput-calibrator/pointercal-xinput/pointercal-qemu.xinput
> 
> diff --git a/meta/recipes-graphics/xinput-calibrator/pointercal-xinput/pointercal-qemu.xinput b/meta/recipes-graphics/xinput-calibrator/pointercal-xinput/pointercal-qemu.xinput
> new file mode 100644
> index 0000000..a816d6d
> --- /dev/null
> +++ b/meta/recipes-graphics/xinput-calibrator/pointercal-xinput/pointercal-qemu.xinput
> @@ -0,0 +1,2 @@
> +# Dummy pointercal.xinput file to prevent xinput_calibrator
> +# from running on qemu startup

NAK

Just put this in qemuall subdirectory and don't change the recipe.

> diff --git a/meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb b/meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb
> index 65348c3..cab3d14 100644
> --- a/meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb
> +++ b/meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb
> @@ -5,8 +5,14 @@ LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384
>  PR = "r7"
>  
>  SRC_URI = "file://pointercal.xinput"
> +SRC_URI_append_qemuall = " file://pointercal-qemu.xinput"
>  S = "${WORKDIR}"
>  
> +do_install_prepend_qemuall () {
> +    install -d ${D}${sysconfdir}/
> +    install -m 0644 ${S}/pointercal-qemu.xinput ${D}${sysconfdir}/pointercal.xinput
> +}
> +
>  do_install() {
>      # Only install file if it has a contents
>      if [ -s ${S}/pointercal.xinput ] &&\
> -- 
> 2.1.4
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      parent reply	other threads:[~2015-09-17 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 13:00 [PATCH 0/1] Add a dummy pointercal calibration for qemu Jussi Kukkonen
2015-09-17 13:00 ` [PATCH 1/1] xinput-calibrator: Add a dummy calibration file " Jussi Kukkonen
2015-09-17 13:23   ` Otavio Salvador
2015-09-17 13:36     ` Jussi Kukkonen
2015-09-17 13:50       ` Otavio Salvador
2015-09-17 15:09   ` Martin Jansa [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=20150917150909.GA2380@jama \
    --to=martin.jansa@gmail.com \
    --cc=jussi.kukkonen@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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