From: Giuseppe Di Guglielmo <giuseppe.diguglielmo@gmail.com>
To: yocto@yoctoproject.org
Subject: Creating a new recipe
Date: Fri, 5 May 2017 10:40:23 -0400 [thread overview]
Message-ID: <CAOiuDAXJjtK37Zx-7WmoUW9PUXQPdBLorcx7d17=s3gEwaqutg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1033 bytes --]
Hi all,
I am trying to create a new recipe for Bazel (from Google):
https://bazel.build/versions/master/docs/install-compile-source.html
The standard compilation flow is relatively simple: "Unzip the archive and
call bash ./compile.sh; this will create a bazel binary in output/bazel.
This binary is self-contained, so it can be copied to a directory on the
PATH (such as /usr/local/bin) or used in-place."
I need some support on how to debug the recipe file that I attach.
In do_compile(), I run bash ./compile.sh. This requires the JAVA_HOME
variable that I export hard-coded because at the moment I do not know how
to fetch that path in a recipe. At this point the compile.sh fails and I do
not know how to debug. Please, can you have a look at it and provide me
some comments?
do_compile () {
export
JAVA_HOME=/home/giuseppe/research/projects/zynq/yocto/build/tmp/work/zc702_zynq7-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs/usr/lib/jvm/openjdk-8
bash ./compile.sh
}
Giuseppe
[-- Attachment #1.2: Type: text/html, Size: 3048 bytes --]
[-- Attachment #2: bazel.bb --]
[-- Type: application/octet-stream, Size: 791 bytes --]
SUMMARY = "Bazel: Correct, reproducible, and fast builds for everyone."
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=3b83ef96387f14655fc854ddc3c6bd57"
SRC_URI = "https://github.com/bazelbuild/bazel/releases/download/0.4.5/bazel-0.4.5-dist.zip"
SRC_URI[md5sum] = "e45ff9b31bc3c811167ab85930bd6378"
SRC_URI[sha256sum] = "2b737be42678900470ae9e48c975ac5b2296d9ae23c007bf118350dbe7c0552b"
DEPENDS = "openjdk-8"
inherit java-library
do_unpack () {
unzip ${PN}-0.4.5-dist.zip
echo ${libdir}
}
do_configure () {
:
}
do_compile () {
export JAVA_HOME=/home/giuseppe/research/projects/zynq/yocto/build/tmp/work/zc702_zynq7-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs/usr/lib/jvm/openjdk-8
bash ./compile.sh
}
do_install () {
:
}
next reply other threads:[~2017-05-05 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 14:40 Giuseppe Di Guglielmo [this message]
2017-05-05 17:04 ` Creating a new recipe Andrea Galbusera
2017-05-05 17:24 ` Giuseppe Di Guglielmo
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='CAOiuDAXJjtK37Zx-7WmoUW9PUXQPdBLorcx7d17=s3gEwaqutg@mail.gmail.com' \
--to=giuseppe.diguglielmo@gmail.com \
--cc=yocto@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.