Re: [yocto] [bitbake] OECORE_TARGET_SYSROOT and OECORE_NATIVE_SYSROOT variables not availables ?

[Khem Raj]

STAGING_DIR_HOST and STAGING_DIR_NATIVE are OE variables that can be
used in recipes to point to target and build host sysroots
respectively.

On Tue, Jan 10, 2017 at 11:22 PM, Karim ATIKI <karim_at...@hotmail.com> wrote:
> Khem,
>
>
> Ok.
>
> How are they specified using Yocto build system ?
>
> Is there any doc link ?
>
>
>
> K.
>
>
> 
> De : Khem Raj <raj.k...@gmail.com>
> Envoyé : mardi 10 janvier 2017 20:39
> À : Karim ATIKI; yocto
> Objet : Re: [yocto] [bitbake] OECORE_TARGET_SYSROOT and
> OECORE_NATIVE_SYSROOT variables not availables ?
>
> These are specified differently when using the Yocto build system you should
> not be using these variables in your makefiles
> On Tue, Jan 10, 2017 at 8:11 AM Karim ATIKI <karim_at...@hotmail.com> wrote:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Hi,
>>
>>
>>
>>
>>
>>
>>
>>
>> I'm using generated Poky SDK to cross-compile our program source-codes,
>> which works fine.
>>
>>
>>
>>
>>
>>
>>
>>
>> Now I wish to integrate the build of the project into Yocto recipes using
>> our makefiles.
>>
>>
>>
>>
>>
>>
>>
>>
>> However, some custom parameters in the makefiles are using the variables
>> OECORE_TARGET_SYSROOT  and OECORE_NATIVE_SYSROOT to manage paths.
>>
>>
>>
>>
>> But it appears that these 2 variables do not exists when the makefiles are
>> called in a do_compile() function of a recipe.
>>
>>
>>
>>
>>
>>
>>
>>
>> Is it normal ? Did I did something wrong ?
>>
>>
>>
>> Should my recipe inherit something specific?
>>
>>
>>
>>
>>
>>
>>
>>
>> Or should I "source" my
>> "environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi" from the SDK into
>> my recipe file ? (=> not portable)
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks.
>>
>>
>>
>>
>>
>>
>>
>>
>> Z.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> ___
>>
>> yocto mailing list
>>
>> yocto@yoctoproject.org
>>
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [bitbake] OECORE_TARGET_SYSROOT and OECORE_NATIVE_SYSROOT variables not availables ?

[Karim ATIKI]

Khem,


Ok.

How are they specified using Yocto build system ?

Is there any doc link ?



K.


De : Khem Raj <raj.k...@gmail.com>
Envoyé : mardi 10 janvier 2017 20:39
À : Karim ATIKI; yocto
Objet : Re: [yocto] [bitbake] OECORE_TARGET_SYSROOT and OECORE_NATIVE_SYSROOT 
variables not availables ?

These are specified differently when using the Yocto build system you should 
not be using these variables in your makefiles
On Tue, Jan 10, 2017 at 8:11 AM Karim ATIKI 
<karim_at...@hotmail.com<mailto:karim_at...@hotmail.com>> wrote:















Hi,








I'm using generated Poky SDK to cross-compile our program source-codes, which 
works fine.








Now I wish to integrate the build of the project into Yocto recipes using our 
makefiles.








However, some custom parameters in the makefiles are using the variables 
OECORE_TARGET_SYSROOT  and OECORE_NATIVE_SYSROOT to manage paths.




But it appears that these 2 variables do not exists when the makefiles are 
called in a do_compile() function of a recipe.








Is it normal ? Did I did something wrong ?



Should my recipe inherit something specific?








Or should I "source" my 
"environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi" from the SDK into my 
recipe file ? (=> not portable)








Thanks.








Z.



























--

___

yocto mailing list

yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>

https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [bitbake] OECORE_TARGET_SYSROOT and OECORE_NATIVE_SYSROOT variables not availables ?

[Khem Raj]

These are specified differently when using the Yocto build system you
should not be using these variables in your makefiles
On Tue, Jan 10, 2017 at 8:11 AM Karim ATIKI  wrote:

>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi,
>
>
>
>
>
>
>
> I'm using generated Poky SDK to cross-compile our program source-codes,
> which works fine.
>
>
>
>
>
>
>
> Now I wish to integrate the build of the project into Yocto recipes using
> our makefiles.
>
>
>
>
>
>
>
> However, some custom parameters in the makefiles are using the variables 
> OECORE_TARGET_SYSROOT
>  and OECORE_NATIVE_SYSROOT to manage paths.
>
>
>
> But it appears that these 2 variables do not exists when the makefiles are
> called in a do_compile() function of a recipe.
>
>
>
>
>
>
>
> Is it normal ? Did I did something wrong ?
>
>
> Should my recipe inherit something specific?
>
>
>
>
>
>
>
> Or should I "source" my 
> "environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi"
> from the SDK into my recipe file ? (=> not portable)
>
>
>
>
>
>
>
> Thanks.
>
>
>
>
>
>
>
> Z.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> ___
>
> yocto mailing list
>
> yocto@yoctoproject.org
>
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [bitbake] OECORE_TARGET_SYSROOT and OECORE_NATIVE_SYSROOT variables not availables ?

[Karim ATIKI]

Hi,


I'm using generated Poky SDK to cross-compile our program source-codes, which 
works fine.


Now I wish to integrate the build of the project into Yocto recipes using our 
makefiles.


However, some custom parameters in the makefiles are using the variables 
OECORE_TARGET_SYSROOT  and OECORE_NATIVE_SYSROOT to manage paths.

But it appears that these 2 variables do not exists when the makefiles are 
called in a do_compile() function of a recipe.


Is it normal ? Did I did something wrong ?

Should my recipe inherit something specific?


Or should I "source" my 
"environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi" from the SDK into my 
recipe file ? (=> not portable)


Thanks.


Z.



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto