Build sdk failed for libraries not found

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Build sdk failed for libraries not found

ソリューションへジャンプ
1,313件の閲覧回数
Mingheng
Contributor I

Hi

    I couldn'd found the old topic with the same name. So I setup this again.

    I tried to build sdk for imx8mm-evk, using command `bitbake -c populate_sdk imx-image-full`. But there is an error about qtpdf as follow picture

    

Mingheng_0-1724314873236.png

    Hope could get someone help again here.

Best regards

Mingheng

 

0 件の賞賛
返信
1 解決策
1,263件の閲覧回数
Harvey021
NXP TechSupport
NXP TechSupport
0 件の賞賛
返信
4 返答(返信)
1,264件の閲覧回数
Harvey021
NXP TechSupport
NXP TechSupport
0 件の賞賛
返信
1,287件の閲覧回数
clay_miller
NXP Employee
NXP Employee

Looks like you might be either missing some QT packages or having some versioning conflicts.

If the goal is to just generate the SDK. Try building a smaller option without all the QT and machine learning. It'll build much quicker as well. 

bitbake core-image-minimal -c populate_sdk

 

Also is this a fresh yocto setup? Are you using a shared state cache?

 

Regards,

Clay

0 件の賞賛
返信
1,270件の閲覧回数
Mingheng
Contributor I
Thanks for your reply

It's a fresh yocto setup.
OTOH, there is a folder named "sstate-cache", did you mean that? The configuration is in default.

BTW, this issue was been repeated by another NXP employee and solved by adding some command in `local.conf` and `bblayers.conf` few days ago. But I forgot to markdown the modification and now I can not find that topic any more.
0 件の賞賛
返信
1,203件の閲覧回数
clay_miller
NXP Employee
NXP Employee

The sstate-cache is just a spot for yocto to consolidate packages that it checks before looking at mirrors. One way to speed up yocto builds with different configurations is to use a locally defined sstated-cache, but sometimes when doing so across several builds you can end up with multiple package versions that cause a similar problem. Fortunately, that is not the issue here. 

Did Harley's link solve your issue?

Regards,

Clay

0 件の賞賛
返信