|
How to generate the SDK for RPI3
#dunfell
#raspberrypi
#sdk
Hi Team, I've built OS for rpi3 using dunfell yocto. I've also generated SDK for the same, for that I've added these info in my local.conf file- TOOLCHAIN_TARGET_TASK_append = " python3-dev kernel-dev
Hi Team, I've built OS for rpi3 using dunfell yocto. I've also generated SDK for the same, for that I've added these info in my local.conf file- TOOLCHAIN_TARGET_TASK_append = " python3-dev kernel-dev
|
By
@prashant2314
· #51406
·
|
|
Cmake CROSS COMPILE problem [PLEASE HELP, URGENT]
#sdk
#yocto
#toolchain
Hi All, I'm in serious task here and I need to cross compile a Cmake project. I need to send an SDK to a client with steps to cross compile the project. This project is compiling successfully via a Yo
Hi All, I'm in serious task here and I need to cross compile a Cmake project. I need to send an SDK to a client with steps to cross compile the project. This project is compiling successfully via a Yo
|
By
Bel Hadj Salem Talel
· #51267
·
|
|
#yocto #sdk How to add *-dev packages to sdk installer and not to target rootfs
#yocto
#sdk
Hello Henrik, As far as I known: - The -dev packages do not end up in target rootfs, unless you specify them in your target image. - The -dev packages end up in the standard SDK target sysroot if you
Hello Henrik, As far as I known: - The -dev packages do not end up in target rootfs, unless you specify them in your target image. - The -dev packages end up in the standard SDK target sysroot if you
|
By
Leon Woestenberg
· #50925
·
|
|
#yocto #sdk How to add *-dev packages to sdk installer and not to target rootfs
#yocto
#sdk
Perhaps extensible SDK is a better fit for you when you are building custom rootfs with SDK.
Perhaps extensible SDK is a better fit for you when you are building custom rootfs with SDK.
|
By
Khem Raj
· #50924
·
|
|
#yocto #sdk How to add *-dev packages to sdk installer and not to target rootfs
#yocto
#sdk
The target rootfs is the image which "-c populate_sdk" is build from. I have actually modified the populate_sdk recipe to include the rootfs in the sdk together with the sysroots for target and host.
The target rootfs is the image which "-c populate_sdk" is build from. I have actually modified the populate_sdk recipe to include the rootfs in the sdk together with the sysroots for target and host.
|
By
Henrik Haugaard Jensen
· #50923
·
|
|
#yocto #sdk How to add *-dev packages to sdk installer and not to target rootfs
#yocto
#sdk
standard SDK can only build applications and it has -dev packages included in it per your image ( if you built SDK with -cpopulate_sdk) where does target rootfs come from ?
standard SDK can only build applications and it has -dev packages included in it per your image ( if you built SDK with -cpopulate_sdk) where does target rootfs come from ?
|
By
Khem Raj
· #50921
·
|
|
#yocto #sdk How to add *-dev packages to sdk installer and not to target rootfs
#yocto
#sdk
We use the "standard" SDK to provide a basic linux filesystem including libraries to be used for application development (based on cmake) in the SDK. So we need the *-dev packages for the libraries to
We use the "standard" SDK to provide a basic linux filesystem including libraries to be used for application development (based on cmake) in the SDK. So we need the *-dev packages for the libraries to
|
By
Henrik Haugaard Jensen
· #50918
·
|
|
#yocto #sdk DRM and DRM_INTEL
#yocto
#sdk
On Thu, Oct 1, 2020 at 7:42 AM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote: drm_intel is in upstream kernel isn't it ? So just check
On Thu, Oct 1, 2020 at 7:42 AM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote: drm_intel is in upstream kernel isn't it ? So just check
|
By
Khem Raj
· #50916
·
|
|
#yocto #sdk DRM and DRM_INTEL
#yocto
#sdk
Does Yocto support drm & drm_intel ?, If so at what Yocto version was support added ? Thanks, Steve
Does Yocto support drm & drm_intel ?, If so at what Yocto version was support added ? Thanks, Steve
|
By
Monsees, Steven C (US)
· #50910
·
|
|
#yocto #sdk - meta-clang undefined references
#sdk
#yocto
Yes, I did this... I am currently down to 1 issue: /ede/smonsees/yocto/test/beignet-Release_v1.3/backend/src/llvm/llvm_to_gen.cpp: In function ‘bool gbe::llvmToGen(gbe::ir::Unit&, const void*, int, bo
Yes, I did this... I am currently down to 1 issue: /ede/smonsees/yocto/test/beignet-Release_v1.3/backend/src/llvm/llvm_to_gen.cpp: In function ‘bool gbe::llvmToGen(gbe::ir::Unit&, const void*, int, bo
|
By
Monsees, Steven C (US)
· #50699
·
|
|
#yocto #sdk - meta-clang undefined references
#sdk
#yocto
that means your link step is not linking libclang properly into your app, perhaps change the order so -lclang appears last <steven.monsees@...> wrote:
that means your link step is not linking libclang properly into your app, perhaps change the order so -lclang appears last <steven.monsees@...> wrote:
|
By
Khem Raj
· #50698
·
|
|
#yocto #sdk - meta-clang undefined references
#sdk
#yocto
Can you inspect the clang libs for these symbols? On Wed, Sep 16, 2020 at 7:04 AM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote:
Can you inspect the clang libs for these symbols? On Wed, Sep 16, 2020 at 7:04 AM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote:
|
By
Khem Raj
· #50697
·
|
|
#yocto #sdk - meta-clang undefined references
#sdk
#yocto
Found a cmake issue and fixed almost all of it, down to 1 missing reference: /ede/smonsees/yocto/test/beignet-Release_v1.3/backend/src/llvm/llvm_to_gen.cpp: In function ‘bool gbe::llvmToGen(gbe::ir::U
Found a cmake issue and fixed almost all of it, down to 1 missing reference: /ede/smonsees/yocto/test/beignet-Release_v1.3/backend/src/llvm/llvm_to_gen.cpp: In function ‘bool gbe::llvmToGen(gbe::ir::U
|
By
Monsees, Steven C (US)
· #50696
·
|
|
#yocto #sdk - meta-clang undefined references
#sdk
#yocto
I can see that libclang is being included...so, not sure why when linking an executable these references are missing...
I can see that libclang is being included...so, not sure why when linking an executable these references are missing...
|
By
Monsees, Steven C (US)
· #50694
·
|
|
#yocto #sdk - meta-clang undefined references
#sdk
#yocto
It should be linking in libclang , I will validate... Note performing 'nm' on libclang appear to show the majority present... Question: if I needed to include a library, what/how would I modify a reci
It should be linking in libclang , I will validate... Note performing 'nm' on libclang appear to show the majority present... Question: if I needed to include a library, what/how would I modify a reci
|
By
Monsees, Steven C (US)
· #50693
·
|
|
#yocto #sdk - meta-clang undefined references
#sdk
#yocto
On Tue, Sep 15, 2020 at 12:56 PM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote: are you linking this library with libclang ? secondly,
On Tue, Sep 15, 2020 at 12:56 PM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote: are you linking this library with libclang ? secondly,
|
By
Khem Raj
· #50689
·
|
|
#yocto #sdk - meta-clang undefined references
#sdk
#yocto
I am building meta-clang (sumo based 6.0.1), with cmake (3.8.2), all under a standard SDK “rocko based” (2.4.1)… Are the following routines accessible/supported under meta-clang ? libgbe.so: undefined
I am building meta-clang (sumo based 6.0.1), with cmake (3.8.2), all under a standard SDK “rocko based” (2.4.1)… Are the following routines accessible/supported under meta-clang ? libgbe.so: undefined
|
By
Monsees, Steven C (US)
· #50688
·
|
|
#sdk #yocto Appears SDK searching host for files that are only present on target side
#sdk
#yocto
Khem: Was there a bug between Clang/cmake in setting up "CMAKE_SHARED_LINKER_FLAGS" ? If you notice,when I set the default compiler to clang, it sets the –sysroot to my build area… this should be my t
Khem: Was there a bug between Clang/cmake in setting up "CMAKE_SHARED_LINKER_FLAGS" ? If you notice,when I set the default compiler to clang, it sets the –sysroot to my build area… this should be my t
|
By
Monsees, Steven C (US)
· #50648
·
|
|
#sdk #yocto Appears SDK searching host for files that are only present on target side
#sdk
#yocto
Khem: I setup clang as default compiler under my SDK, and I am seeing the same issue... It appears to be the linker. Is this an environmental setup issue or possibly a problem with the "compiler-rt" c
Khem: I setup clang as default compiler under my SDK, and I am seeing the same issue... It appears to be the linker. Is this an environmental setup issue or possibly a problem with the "compiler-rt" c
|
By
Monsees, Steven C (US)
· #50647
·
|
|
#sdk #yocto Appears SDK searching host for files that are only present on target side
#sdk
#yocto
Khem: Do I need to re-assign CC/CXX/CPP to point to CLANGCC, etc. in my environment-setup-coreI7-64-poky-linux script ? I thought I read somewhere that gcc was always the default compiler under the SD
Khem: Do I need to re-assign CC/CXX/CPP to point to CLANGCC, etc. in my environment-setup-coreI7-64-poky-linux script ? I thought I read somewhere that gcc was always the default compiler under the SD
|
By
Monsees, Steven C (US)
· #50646
·
|