All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Roberts <nathan.roberts@gmail.com>
To: yocto@yoctoproject.org
Subject: Recipe for JNI Wrapper (libusb4java)
Date: Wed, 10 Jan 2018 20:57:50 +0000	[thread overview]
Message-ID: <CAGkqu_uJC_jUYACWfzaSEn4N9a5M6pvxUxA6mhMkM-OxSdEjgA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]

I'm trying to create a recipe for libusb4Java (
https://github.com/usb4java/libusb4java/).

I have the following recipe

SUMMARY = "Native library support for usb4java"
HOMEPAGE = "http://usb4java.org"
BUGTRACKER = "https://github.com/usb4java/libusb4java/issues"
SECTION = "libs"
DEPENDS = "libusb"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE.md;md5=4c49d7fe1fc7a6ebad3b4e6b849a0052"
BBCLASSEXTEND = "native nativesdk"
SRCREV = "396d642a57678a0d9663b062c980fe100cc0ea1e"
SRC_URI = "git://github.com/usb4java/libusb4java.git"

S = "${WORKDIR}/git"
#need to change following ref http://usb4java.org/nativelibs.html
D = "/tmp"
export JAVA_HOME="${STAGING_DIR_NATIVE}/usr/bin/java"
inherit cmake java-library


local.conf has the following added:
BB_ENV_EXTRAWHITE += "JAVA_HOME"


I get the following error:
checking if
/home/ubuntu/yocto/poky/build/tmp/work/x86_64-linux/classpath-native/0.99-r6.0/recipe-sysroot-native/usr/bin/ecj-initial
works... configure: error: The Java compiler
/home/ubuntu/yocto/poky/build/tmp/work/x86_64-linux/classpath-native/0.99-r6.0/recipe-sysroot-native/usr/bin/ecj-initial
failed (see config.log, check the CLASSPATH?)

So I appear to have a classpath problem, but I'm unsure how to resolve this?

Any advice appreciated.

[-- Attachment #2: Type: text/html, Size: 1810 bytes --]

                 reply	other threads:[~2018-01-10 20:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAGkqu_uJC_jUYACWfzaSEn4N9a5M6pvxUxA6mhMkM-OxSdEjgA@mail.gmail.com \
    --to=nathan.roberts@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.