From: "Martin Ertsås" <mertsas@cisco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: jni.h included
Date: Wed, 10 Oct 2012 08:51:07 +0200 [thread overview]
Message-ID: <50751ADB.7060007@cisco.com> (raw)
In-Reply-To: <50751849.9070501@nedap.com>
Assuming you use meta-java, it seems like what you are looking for is:
DEPENDS += "openjdk-6-jdk"
as that at least contains the include, lib and bin directory.
- Martin
On 10/10/12 08:40, Jaap de Jong wrote:
>
> On 10/09/2012 07:51 AM, Martin Ertsås wrote:
>> As you are using icedtea6, I guess DEPENDS += "icedtea6" should do it.
>>
>> - Martin
> I thought that might do the trick, but...
> ERROR: Nothing PROVIDES 'icedtea6'
> So I tried
> DEPENDS += "icedtea6-native"
> and that ends with
> jni.h: No such file or directory
>
> Any other ideas?
>
>> On 10/08/12 16:49, Jaap de Jong wrote:
>>> On 10/08/2012 04:05 PM, Khem Raj wrote:
>>>> On Mon, Oct 8, 2012 at 4:18 AM, Jaap de Jong <jaap.dejong@nedap.com>
>>>> wrote:
>>>>> Hi All!
>>>>> probably a stupid question... my apologies!
>>>>> If a source I'm working on #include jni.h what do I need to add in a
>>>>> recipe
>>>>> to get it translated?
>>>> DEPENDS += "openjdk" or something like that which denotes jdk
>>>>
>>> Tried
>>> DEPENDS += "openjdk"
>>> unfortunately errors out with
>>> ERROR: Nothing PROVIDES 'openjdk'
>>>
>>> Tried with
>>> DEPENDS += "openjdk-6"
>>> but that errors out with
>>> fatal error: jni.h: No such file or directory
>>>
>>> So finally I ended up adding this:
>>> CFLAGS += "-I${STAGING_LIBDIR_NATIVE}/jvm/icedtea6-native/include
>>> -I${STAGING_LIBDIR_NATIVE}/jvm/icedtea6-native/include/linux"
>>> But that just looks so ugly...
>>>
>>>
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2012-10-10 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 11:18 jni.h included Jaap de Jong
2012-10-08 14:05 ` Khem Raj
2012-10-08 14:49 ` Jaap de Jong
2012-10-09 5:51 ` Martin Ertsås
2012-10-10 6:40 ` Jaap de Jong
2012-10-10 6:51 ` Martin Ertsås [this message]
2012-10-10 8:59 ` Jaap de Jong
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=50751ADB.7060007@cisco.com \
--to=mertsas@cisco.com \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox