recipes-bsp: libdmabufheap: Add recipe to compile libdmabufheap

[quic-vjitta]

Add recipe to compile libdmabuf which provices apis to access dmabuf heap framework.

[lumag]

What is the reason for the recipe being named qcom-libdmabufheap instead of just libdmabufheap ?

[lumag]

There doesn't seem to be a versioned release tag. Please rename the recipe to foo_git.bb and set PV = "0.0+git"

[quic-vjitta]

There doesn't seem to be a versioned release tag. Please rename the recipe to foo_git.bb and set PV = "0.0+git"
Added it.

[quic-vjitta]

What is the reason for the recipe being named qcom-libdmabufheap instead of just libdmabufheap ?

This source code has some changes from qualcomm and is diverged from android open source libdmabufheap code, So it's being named with qcom-libdmabufheap.

[lumag]

Other than the unnecessary FILES, what is the reason for the recipe being named qcom-libdmabufheap instead of just libdmabufheap ?

[lumag]

Also please drop the gerrit tag from the commit message

[koenkooi]

Other than the unnecessary FILES, what is the reason for the recipe being named qcom-libdmabufheap instead of just libdmabufheap ?

And if it's a variant of an existing upstream project, there need to the appropriate (R)CONFLICTS /(R)REPLACES/(R)PROVIDES stanzas to alert the parser to the conflicts.

[github-actions]

Test Results

 2 files  ±0   4 suites  ±0   1m 21s ⏱️ ±0s
19 tests ±0  19 ✅ ±0  0 💤 ±0  0 ❌ ±0 
38 runs  ±0  38 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit a0f449f. ± Comparison against base commit 313aa65.

[github-actions]

Test jobs for commit a0f449f

• Job 64301 on qcs6490
• Job 64300 on qcs9100

[quic-vjitta]

Also please drop the gerrit tag from the commit message

done

[lumag]

• Drop the qcom- prefix from the recipe name, everything in this layer is qcom-related.
• Make it tested in the CI

[lumag]

What is the reason for the recipe being named qcom-libdmabufheap instead of just libdmabufheap ?

This source code has some changes from qualcomm and is diverged from android open source libdmabufheap code, So it's being named with qcom-libdmabufheap.

In such a case, it might be better package libdmabufheap and add your patches on top of it. I strongly dislike the idea of qcom-specific forks of the existing projects. And qcom-specific recipes.

[lumag]

Okay. After looking at the AOSP source... Don't package it. But the commit message should document that it's a fork of the AOSP library. Inside the recipe please add a brief comment describing Qualcomm changes, so that a random user browsing the repo tree would understand the difference and the reason. Please follow @koenkooi's suggestion and add 'PROVIDES' notes.

[lumag]

Also, while I noticed it. Neither libdmabufheap nor libvmmem are BSP-related packages. Please move them to a more sensible location. Maybe recipes-support.