Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9596] New: KODI: --enable-lirc needs "HAVE_LIRC" compiler definition to use the lirc subsystem
Date: Wed, 18 Jan 2017 03:48:03 +0000	[thread overview]
Message-ID: <bug-9596-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=9596

            Bug ID: 9596
           Summary: KODI: --enable-lirc needs "HAVE_LIRC" compiler
                    definition to use the lirc subsystem
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: lipkegu at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

When compiling kodi, with option --enable-lirc, the Lirc subsystem doesnt get
initialized when "-DHAVE_LIRC isnt set. normaly --enable-lirc should set it but
it doesnt.

Reproduce case:
https://github.com/xbmc/xbmc/blob/8d4a5bba55638dfd0bdc5e7de34f3e5293f99933/xbmc/input/ButtonTranslator.cpp#L601

I removed the "HAVE_LIRC" definition from the code and the result was clear:

01:00:26.239 T:3016212480    INFO: Loading special://xbmc/system/Lircmap.xml
01:00:26.263 T:3016212480    INFO: * Adding remote mapping for device 'mceusb'
01:00:26.265 T:3016212480    INFO: * Adding remote mapping for device
'XboxDVDDongle'
01:00:26.265 T:3016212480    INFO: * Adding remote mapping for device
'Microsoft_Xbox'
01:00:26.266 T:3016212480    INFO: * Adding remote mapping for device
'PinnacleSysPCTVRemote'
01:00:26.266 T:3016212480    INFO: * Adding remote mapping for device 'anysee'
01:00:26.267 T:3016212480    INFO: * Adding remote mapping for device
'iMON-PAD'
01:00:26.267 T:3016212480    INFO: * Adding remote mapping for device
'Antec_Veris_RM200'
01:00:26.268 T:3016212480    INFO: * Adding remote mapping for device
'MCE_via_iMON'
01:00:26.268 T:3016212480    INFO: * Adding remote mapping for device
'TwinHanRemote'
01:00:26.269 T:3016212480    INFO: * Adding remote mapping for device
'linux-input-layer'
01:00:26.270 T:3016212480    INFO: * Linking remote mapping for
'linux-input-layer' to 'cx23885_remote'
01:00:26.270 T:3016212480    INFO: * Adding remote mapping for device
'mediacenter'
01:00:26.271 T:3016212480    INFO: * Adding remote mapping for device
'devinput'
01:00:26.276 T:3016212480    INFO: Loading special://profile/Lircmap.xml
01:00:26.282 T:3016212480    INFO: * Adding remote mapping for device 'mceusb'
01:00:26.283 T:3016212480    INFO: * Adding remote mapping for device
'devinput'

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-01-18  3:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18  3:48 bugzilla at busybox.net [this message]
2017-01-18  3:59 ` [Buildroot] [Bug 9596] KODI: --enable-lirc needs "HAVE_LIRC" compiler definition to use the lirc subsystem bugzilla at busybox.net
2017-01-20  5:46 ` bugzilla at busybox.net
2017-02-26 14:28 ` bugzilla at busybox.net
2017-02-26 15:56 ` bugzilla at busybox.net
2017-05-07 12:11 ` bugzilla at busybox.net
2017-05-07 14:07 ` bugzilla at busybox.net

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=bug-9596-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.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