From: Greg Wilson-Lindberg <GWilson@sakuraus.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Having trouble getting recipe to run in proper directory
Date: Thu, 5 Oct 2017 00:16:15 +0000 [thread overview]
Message-ID: <2376f96acc0f4c3db9c3b40a3cfc98f3@sakuraus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1935 bytes --]
I'm trying to create a new recipe for a package that has a version and non-numeric rev in its name (canfestival-3-asc). I've gotten bitbake to unpack the package into a tree that looks ok, but it keeps trying to run the compile at least in the wrong directory. Here is the recipe:
SUMMARY = "Independent CANOpen® stack"
DESCRIPTION = "CanFestival focuses on providing an ANSI-C platform independent \
CANOpen® stack that can be built as master or slave nodes on PCs, \
Real-time IPCs, and Microcontrollers."
HOMEPAGE = "http://www.canfestival.org/"
SRCREV = "895:8973dd8be7e8"
SRC_URI = "hg://bitbucket.org/Mongo;protocol=https;module=canfestival-3-asc"
SRC_URI[md5sum] = ""
SRC_URI[sha256sum] = ""
PN = "canfestival"
PV = '3'
PR = 'asc'
LICENSE = "LGPL-2"
LIC_FILES_CHKSUM = "file://COPYING;md5= \
file://LICENCE;md5="
inherit autotools
# Specify any options you want to pass to the configure script using EXTRA_OECONF:
EXTRA_OECONF = "-can=socket -timers=unix -SDO_MAX_SIMULTANEOUS_TRANSFERS=25 \
-SDO_MAX_LENGTH_TRANSFER=4096 -MAX_NB_TIMER=128 -SDO_TIMEOUT_MS=1000"
PROVIDES = "canfestival"
The directory structure that bitbake builds is:
canfestival
3-asc
build
canfestival-3 # directory that bitbake is trying to compile in
canfestival-3-asc # directory that code was extracted to
temp
I'm not getting any errors from the configure task, but the log file looks like it is trying to run from the canfestival-3 directory, not the canfestival-3-asc. What can I do to the recipe to get the build to run in the canfestival-3-asc directory? Or, i guess, get bitbake to unpack the source into the canfestival-3, or a different directory that it will actually run the tasks in.
Regards,
Greg
[-- Attachment #2: Type: text/html, Size: 6134 bytes --]
next reply other threads:[~2017-10-05 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 0:16 Greg Wilson-Lindberg [this message]
2017-10-05 2:01 ` Having trouble getting recipe to run in proper directory Paul Eggleton
2017-10-05 17:51 ` Greg Wilson-Lindberg
2017-10-05 19:18 ` Burton, Ross
2017-10-05 20:13 ` Greg Wilson-Lindberg
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=2376f96acc0f4c3db9c3b40a3cfc98f3@sakuraus.com \
--to=gwilson@sakuraus.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.