From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe] [PATCH] nodejs needs python-native
Date: Tue, 20 May 2014 13:56:55 -0600 [thread overview]
Message-ID: <537BB387.6090507@mlbassoc.com> (raw)
In-Reply-To: <CAMKF1soVNe6OpNDX3C74awa1=vzP=wQpvcGYZ9y3=8FJVbzM3Q@mail.gmail.com>
On 2014-05-20 13:28, Khem Raj wrote:
> On Tue, May 20, 2014 at 12:03 PM, Amy Fong <amy.fong@windriver.com> wrote:
>> -DEPENDS = "openssl"
>> +DEPENDS = "openssl python-native"
>>
>
> may be it should inherit pythonnative
>
>> SRC_URI = "http://nodejs.org/dist/v${PV}/node-v${PV}.tar.gz \
>> file://0001-gcc-has-a-builtin-define-to-denote-hard-abi-when-in-.patch \
>> @@ -28,6 +28,7 @@ do_configure () {
>>
>> do_compile () {
>> export LD="${CXX}"
>> + export PATH=${STAGING_BINDIR_NATIVE}/python-native:$PATH
If you inherit pythonnative, this 'export PATH...' is also not necessary
>> make BUILDTYPE=Release
>> }
>>
>> @@ -40,3 +41,5 @@ RDEPENDS_${PN}_class-native = ""
>>
>> FILES_${PN} += "${libdir}/node/wafadmin ${libdir}/node_modules ${libdir}/dtrace"
>> BBCLASSEXTEND = "native"
>> +
>> +FILES_${PN} += "/usr/lib/*"
>
> make it ${libdir}/* here
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-05-20 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 19:03 [meta-oe] [PATCH] nodejs needs python-native Amy Fong
2014-05-20 19:28 ` Khem Raj
2014-05-20 19:56 ` Gary Thomas [this message]
2014-05-27 16:54 ` [meta-oe] [PATCH] [v2] nodejs needs python-native (Was: Re: [meta-oe] [PATCH] nodejs needs python-native) Amy Fong
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=537BB387.6090507@mlbassoc.com \
--to=gary@mlbassoc.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 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.