Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add libraw1394 to buildroot
Date: Tue, 12 Dec 2006 22:22:27 +0100	[thread overview]
Message-ID: <20061212212227.GF4442@aon.at> (raw)
In-Reply-To: <20061212183109.GA1480@tuxedo.home.lan>

On Tue, Dec 12, 2006 at 07:31:09PM +0100, Lars Munch wrote:
>On Tue, Dec 12, 2006 at 05:59:32PM +0100, Bernhard Fischer wrote:
>> On Tue, Dec 12, 2006 at 05:35:14PM +0100, Lars Munch wrote:
>> >Hi all
>> >
>> >The attached patch adds libraw1394-1.2.1 to buildroot. libraw1394 is a
>> >library for direct access to IEEE 1394 bus.

>> >+$(STAGING_DIR)/lib/libraw1394.so: $(LIBRAW1394_DIR)/.compiled
>> >+	make -C $(LIBRAW1394_DIR)/src install
>> >+
>> >+$(TARGET_DIR)/usr/lib/libraw1394.so: $(STAGING_DIR)/lib/libraw1394.so
>> >+	cp -dpf $(STAGING_DIR)/lib/libraw1394.so* $(TARGET_DIR)/usr/lib/
>> >+
>> >+libraw1394: uclibc $(TARGET_DIR)/usr/lib/libraw1394.so
>> >+
>> >+libraw1394-source: $(DL_DIR)/$(LIBRAW1394_SOURCE)
>> >+
>> >+libraw1394-clean:
>> >+	rm $(TARGET_DIR)/usr/lib/libraw1394.so*
>> >+	-$(MAKE) -C $(LIBRAW1394_DIR) clean
>> 
>> Can we please settle on the convention that
>> foo-clean uninstalls itself from the target-dir?
>
>I am not sure what you mean. It already removes itself from the target-dir?

You're right since you IIRC install into the staging dir and just cp the *.so
for the target. Sorry for my sloppy reading.

That may raise the question if and iff then how we want to allow for
installing .a into the target to ease e.g. debugging. Generally nothing i
want to worry for now, though. :)

Please refresh (the CC_FOR_BUILD) and resend.
TIA and cheers,
Bernhard

  reply	other threads:[~2006-12-12 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 16:35 [Buildroot] [PATCH] Add libraw1394 to buildroot Lars Munch
2006-12-12 16:59 ` Bernhard Fischer
2006-12-12 18:31   ` Lars Munch
2006-12-12 21:22     ` Bernhard Fischer [this message]
2006-12-13  8:55       ` Lars Munch

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=20061212212227.GF4442@aon.at \
    --to=rep.nop@aon.at \
    --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