From: Khem Raj <raj.khem@gmail.com>
To: poky@yoctoproject.org
Subject: Re: problem .so files in my image.
Date: Sat, 12 Mar 2011 00:38:05 -0800 [thread overview]
Message-ID: <4D7B30ED.3020801@gmail.com> (raw)
In-Reply-To: <AANLkTim5QiDttsH40ezchVxLVGQVAtV5iGKbAE7J2edh@mail.gmail.com>
On 3/12/2011 12:29 AM, kubera samrat wrote:
> Hi,
>
> I have added jpeg_6b to my recipe. When I build it It got
> succesful stating " Tasks Summary: Attempted 3879 tasks of which 3863
> didn't need to be rerun and 0 failed."
> But When I mount my image I am unable to see ".so" files. But I can
> see those files created in ".libs" folder. even I tried to copy those
> files from .libs to image folder but I can't see.
you should add the packages to your image one way is
in local.conf add
IMAGE_INSTALL += "jpeg-tools ..."
basically find the package names from deploy directory and use them in
above construct.
> Can you please suggest me the solution. my jpeg_6b.bb file looks like
> as shown below.
>
> ************************************************************************************************************************************************************
> SUMMARY = "library for jpeg"
> DESCRIPTION = "Libraries that allow compression of image files based
> on the Joint Photographic Experts"
> HOMEPAGE = "http://www.ijg.org/"
> SECTION = "libs"
> LICENSE = "jpeg"
> DEPENDS = "libtool-cross"
> DEPENDS_virtclass-native = "libtool-native"
>
> PR = "r0"
> S = "${WORKDIR}/jpeg-${PV}"
>
> SRC_URI = "http://www.ijg.org/files/jpegsrc.v${PV}.tar.gz"
> inherit pkgconfig autotools
> EXTRA_OECONF="--enable-static --enable-shared"
> EXTRA_OEMAKE='"LIBTOOL=${STAGING_BINDIR}/${HOST_SYS}-libtool"'
>
> #CFLAGS_append = " -D_REENTRANT"
> #INSTALL_PREFIX="${D}"
> do_configure_prepend(){
> # rm -f ${D}/ltconfig
> rm -f ${D}/ltmain.sh
> # rm -f ${D}${includedir}/jconfig.h
> }
> do_configure(){
> oe_runconf PREFIX=${D}
> }
> do_compile(){
> oe_runmake "LIBTOOL=$LIBTOOL"
> }
> do_install(){
> install -d ${D}${bindir} ${D}${includedir}\
> ${D}${mandir}/man1 ${D}${libdir}
>
> # install -m 0755 .libs/libjpeg.so ${STAGING_LIBDIR}
> # install -m 0755 .libs/libjpeg.so.62 ${STAGING_LIBDIR}
> # install -m 0755 .libs/libjpeg.so.62.0.0 ${STAGING_LIBDIR}
>
> oe_runmake 'bindir=${D}${bindir}' 'mandir=${D}${mandir}'
> 'libdir=${D}${libdir}'install
> install -m 0755 .libs/libjpeg.so ${D}${libdir}
> install -m 0755 .libs/libjpeg.so.62 ${D}${libdir}
> install -m 0755 .libs/libjpeg.so.62.0.0 ${D}${libdir}
> }
>
> PACKAGES =+ "jpeg-tools "
> DESCRIPTION_jpeg-tools = "The jpeg-tools package includes the client
> programs for access libjpeg functionality. These tools allow for the
> compression, decompression, transformation and display of JPEG files."
> FILES_jpeg-tools = "${bindir}/*"
>
> BBCLASSEXTEND = "native"
>
> ***************************************************************************************************************************************
> Thanks and regards,
> V kubera Samrat
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
next prev parent reply other threads:[~2011-03-12 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 8:29 problem .so files in my image kubera samrat
2011-03-12 8:38 ` Khem Raj [this message]
2011-03-12 8:56 ` Darren Hart
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=4D7B30ED.3020801@gmail.com \
--to=raj.khem@gmail.com \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.