Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Wrong installation path?
Date: Fri, 31 Jan 2014 09:45:17 +0100	[thread overview]
Message-ID: <52EB629D.2030707@gmail.com> (raw)

Hello,
I'm trying to get lirc works on my buildroot environment. Looking at 
package/lirc/src I see the S70lircd script has a lot of hardcoded paths, 
i.e.:

if [ -f /etc/lirc/hardware.conf ];then
         . /etc/lirc/hardware.conf
fi

if [ ! -f /etc/lirc/lircd.conf ] || grep -q "^#UNCONFIGURED" 
/etc/lirc/lircd.conf; then
         if [ "$1" = "start" ]; then


The lirc.mk instead contains the following:

define LIRC_INSTALL_TARGET_SCRIPTS
         mkdir -p $(TARGET_DIR)/etc/init.d
         $(INSTALL) -m 0755 package/lirc/src/S70lircd 
$(TARGET_DIR)/etc/init.d/
         $(INSTALL) -m 0755 package/lirc/src/hardware.conf 
$(TARGET_DIR)/etc/
         $(INSTALL) -m 0755 package/lirc/src/lircd.conf $(TARGET_DIR)/etc/
endef


In my opinion the destination directory should be $(TARGET_DIR)/etc/lirc/
Is there any reason why /lirc/ is missing? I mean: I am sure that the 
package has worked for those who have uploaded.


The second question is more generic. I can't still understand when I 
have to learn about buildroot and  when about the specific package.
For example, the lirc documentation says I should find a /dev/lirc 
device if I'm using udev.
But on my target (which has udev!) there is no such a device.

Where should I look at? How to know if I missed something in the 
buildroot/kernel configuration or just in the package (lirc) 
configuration files?

Thanks
Marco

             reply	other threads:[~2014-01-31  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31  8:45 Marco Trapanese [this message]
2014-01-31 10:11 ` [Buildroot] Wrong installation path? Thomas Petazzoni
2014-02-02 17:55   ` Arnout Vandecappelle

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=52EB629D.2030707@gmail.com \
    --to=marcotrapanese@gmail.com \
    --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