Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Add libtool related stuff to task-native-sdk
Date: Tue, 05 Jan 2010 23:21:14 -0500	[thread overview]
Message-ID: <4B440FBA.8060103@balister.org> (raw)

Does anyone object if I push these changes to task-native-sdk? I've been 
talking with some people doing builds on omap3 hardware and it looks 
like this change will make things easier for them.

Philip

diff --git a/recipes/tasks/task-sdk-native.bb 
b/recipes/tasks/task-sdk-native.bb
index 35ddf78..e21384b 100644
--- a/recipes/tasks/task-sdk-native.bb
+++ b/recipes/tasks/task-sdk-native.bb
@@ -1,15 +1,16 @@
  DESCRIPTION = "Packages required for native (on-device) SDK"
  LICENSE = "MIT"
-DEPENDS = "virtual/libc gcc binutils make patch patchutils diffstat 
diffutils automake flex bison gawk sed grep"
+DEPENDS = "virtual/libc gcc binutils make patch patchutils diffstat 
diffutils automake flex bison gawk sed grep libtool pkgconfig"
  RDEPENDS = "gcc-symlinks g++-symlinks cpp cpp-symlinks binutils-symlinks \
             make virtual-libc-dev \
             task-proper-tools perl-modules flex flex-dev bison gawk sed 
grep autoconf automake make \
-           patch patchutils diffstat diffutils libstdc++-dev"
+           patch patchutils diffstat diffutils libstdc++-dev \
+            libtool libtool-dev libltdl-dev pkgconfig"

  RECOMMENDS = " g77-symlinks gfortran-symlinks "
  RPROVIDES_${PN} = "task-native-sdk"

-PR = "r7"
+PR = "r8"

  ALLOW_EMPTY = "1"
  PACKAGES = "${PN}"




             reply	other threads:[~2010-01-06  4:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06  4:21 Philip Balister [this message]
2010-01-24 11:27 ` Add libtool related stuff to task-native-sdk Holger Hans Peter Freyther

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=4B440FBA.8060103@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@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