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

#yocto #sdk

Perhaps extensible SDK is a better fit for you when you are building custom rootfs with SDK.

#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.

#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 ?

#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

#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

#yocto #sdk

Does Yocto support drm & drm_intel ?, If so at what Yocto version was support added ? Thanks, Steve

#yocto #sdk

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

#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:

#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:

#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

#sdk #yocto

I can see that libclang is being included...so, not sure why when linking an executable these references are missing...

#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

#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,

#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

#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

#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

#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

#sdk #yocto

Leon: Thank you for responding, however I am already doing these steps and environment appears to be setting up correctly... my problem seems to when running make after config. I too am using gcc curr

#sdk #yocto

Hello Steven, you mention you use CMake with the Yocto (standard) SDK. After you sourced the SDK environment script, what is the output of "which cmake" ? Do you use the cmake toolchain configuration

#sdk #yocto