All of lore.kernel.org
 help / color / mirror / Atom feed
From: "mar.krzeminski" <mar.krzeminski@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Perl usage in recipe
Date: Wed, 05 Aug 2015 20:38:22 +0200	[thread overview]
Message-ID: <55C2581E.2000108@gmail.com> (raw)
In-Reply-To: <CAMKF1srMrRrcdMCK95vxQGThc_JP25wKtK3z70sb3fyUdfAR4g@mail.gmail.com>



W dniu 05.08.2015 o 20:08, Khem Raj pisze:
> On Wed, Aug 5, 2015 at 10:23 AM, mar.krzeminski
> <mar.krzeminski@gmail.com> wrote:
>> Hello,
>>
>> In my recipe I want to call perl script that will create image.
>> How should I do that to be absolutely sure that perl will be used from yocto
>> not from my system?
>> Maybe is there any example somewhere that I can check how this should be
>> done?
> inherit perlnative
Ok, thanks. And one more question.
How about scrip call after this inherit?
Can I use simple perl MY_SCRIPT or should I consider to use something 
like this (from perf recipe)

inherit perlnative
# Env var which tells perl if it should use host (no) or target (yes) settings
export PERLCONFIGTARGET = "${@is_target(d)}"
export PERL_INC = "${STAGING_LIBDIR}${PERL_OWN_DIR}/perl/${@get_perl_version(d)}/CORE"
export PERL_LIB = "${STAGING_LIBDIR}${PERL_OWN_DIR}/perl/${@get_perl_version(d)}"
export PERL_ARCHLIB = "${STAGING_LIBDIR}${PERL_OWN_DIR}/perl/${@get_perl_version(d)}"

Regards,
Marcin
>> Regards,
>> Marcin
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto



      reply	other threads:[~2015-08-05 18:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 17:23 Perl usage in recipe mar.krzeminski
2015-08-05 18:08 ` Khem Raj
2015-08-05 18:38   ` mar.krzeminski [this message]

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=55C2581E.2000108@gmail.com \
    --to=mar.krzeminski@gmail.com \
    --cc=raj.khem@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.