On 07-11-2013 18:31, br jer wrote:
Daiane,
Thanks for sending my the examples, I am sorry that I am not grasping
the examples.
Looking at the "tiny example" below, it inherits autotools, so that is
good, as I am using autools in my project to generate Makefile as well.
My questions:
- Where in this recipe below points to my project directory?
- Is ${FSL_MIRROR}/${PN} where I place my project? Or
The "source" of your package is on SRC_URI variable. you may point a git
uri, or a mirror to you tarball.
you can have SRC_URI = "file://tarball.tar.gz" if you want
- where in the build/tmp/work/... area should I place my project? In my
case, what environment variables shall I use?
it depends on how you make your recipe PACKAGE_ARCH = "${MACHINE_ARCH}"
says it's a package that only work for that machine, so it will be
placed on tmp/work/machine_name. But, a lot of packages are commom for
any architecture, for example ssh.
How can I skip the SRC_URI checksums? I don't need that as I am placing
trusted source in the the tree.
hum, you cannot. Please, use the checksums :D <3
(imagine that you know the source is trusted, but yocto need to
"download" and "unpack" it, so you added 2 steps of "untrusted" behavior.)
Would BB automatically run ./configure , make and make install ?
yes, but only if you inherit autotools
>
How would this recipe get called ? entry in my conf.local?
bitbake mysweetheartpackage when you're developing should be enough.
If you want it installed on your image, you add it on your image install.
easiest/dirty way is local.conf CORE_IMAGE_EXTRA_INSTALL.
Many Thanks,
Norman
# Copyright (C) 2013 Freescale Semiconductor
# Released under the MIT license (see COPYING.MIT for the terms)
DESCRIPTION = "Freescale Multimedia VPU wrapper"
DEPENDS = "imx-vpu"
LICENSE = "Proprietary"
SECTION = "multimedia"
LIC_FILES_CHKSUM = "file://EULA.txt;md5=93b784b1c11b3fffb1638498a8dde3f6"
# FIXME: Inspecting the source code the content is in fact 1.0.40
SRC_URI = "${FSL_MIRROR}/${PN}-3.10.9-1.0.0
<tel:3.10.9-1.0.0>.bin;fsl-eula=true"
SRC_URI[md5sum] = "25891ef8d92e82d9b2e999a74a327971"
SRC_URI[sha256sum] =
"84d610c478963e7b6a9660a38547b5365ca910159972b3860d7356aee33b9b41"
S = "${WORKDIR}/${PN}-3.10.9-1.0.0 <tel:3.10.9-1.0.0>"
inherit fsl-eula-unpack autotools pkgconfig
do_install_append() {
# FIXME: Drop examples for now
rm -r ${D}${datadir}/imx-mm
}
PACKAGE_ARCH = "${MACHINE_ARCH}"
COMPATIBLE_MACHINE = "(mx6q|mx6dl|mx6s)"
On Thu, Nov 7, 2013 at 4:50 AM, Daiane Angolini
<[email protected] <mailto:[email protected]>>
wrote:
On 07-11-2013 02:16, br jer wrote:
I am using the "master" branch of Yocto. I have a gstreamer
application
that is compiled and tested on Ubuntu. I have a Makefile for this
application. The Yocto build I use fsl-image-test and added a few
plugins in my conf.local. I have tested all the
plugins/pipeline that
is needed for this app with gst-launch.
I just want to run a quick test of the code on the wandboard,
what is
the fastest way to do a make and produce a executable ? I
looked at the
Yocto manual and it seems that it calls for creating a recipe
etc. Is
there a simple template that I can use?
You can try to use your already built binary into any rootfs.
If you decide to try to make the recipe, you can share here your
problems, but, please take care of proprietary stuff.
You can try at first an tiny example:
http://git.yoctoproject.org/__cgit/cgit.cgi/meta-fsl-arm/__tree/recipes-multimedia/__libfslvpuwrap/libfslvpuwrap_1.__0.40.bb?h=master-next&id=__9135a32b50800cac2c3feb0bac1f19__c3d6743add
<http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/recipes-multimedia/libfslvpuwrap/libfslvpuwrap_1.0.40.bb?h=master-next&id=9135a32b50800cac2c3feb0bac1f19c3d6743add>
and then go to a more complex one:
http://git.yoctoproject.org/__cgit/cgit.cgi/meta-fsl-arm/__tree/recipes-multimedia/gst-__plugins/gst-fsl-plugin_3.0.9.__bb?h=master-next&id=__9135a32b50800cac2c3feb0bac1f19__c3d6743add
<http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/recipes-multimedia/gst-plugins/gst-fsl-plugin_3.0.9.bb?h=master-next&id=9135a32b50800cac2c3feb0bac1f19c3d6743add>
Daiane
Thanks,
Norman
_________________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.__org
<mailto:[email protected]>
https://lists.yoctoproject.__org/listinfo/meta-freescale
<https://lists.yoctoproject.org/listinfo/meta-freescale>
--
Daiane
--
Daiane
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale