Create Device Profiles

We should close this issue and open new tickets for anything found from here on out. Agree?

Current state:

FF contains the 3 qemu targets the make up the "generic/default" MACHINES .
For the FF release it might be too late to turn the arm+arm64 target on but for GG this will be the default SDK providers.

Summary of the 09/28 SAT call:

• the SDK needs to be build for generic/default 'MACHINES' (aarch64, arm32, x86-64)

  • these could be 'generic-arm', 'generic-aarch64', 'generic-x86-64'

  • (see some samples in meta-linaro/conf/machine/ as pointer)

• the SDK needs to be extensible through rpm (rpm-feeds) to pull-in new profiles

  • single rpm built by local sdk

  • rpm feed produced by bitbake (nativesdk)

  • rpm feed setup/shared by local sdk
    *

>3) Tadao Tanikawa asked if we will create an SDK for each profile?

One thing related to SDK.
What if application developer wants to use additional toolchain/SDK (say, B-SDK) that is not in the AGL's SDK image?
I wonder which of the below should be the recommended solution.

i) He must install B-SDK on top of AGL-SDK environment.
ii) He must add B-SDK to the image first (by writing some recipes), then build SDK for his use.

I just am not sure if Qt or other a few famous toolkits are exhausted list of development tools/libraries app developers may want for his app to be built for AGL.

My notes from the BoF session at ALS. 

1) It was noted by Renesas folks that we should try to align with GDP for BSP creation and maintenance. They currently have separate teams for maintaining the BSPs for each project.

2)  asked about the role of meta-agl-bsp in the new design and if it is intended to go away eventually. 

3) asked if we will create an SDK for each profile? replied that the goal is to minimize the number of SDKs required and that the default tune for the BSPs is a step towards getting there.  Tanikawa noted that we will need a specific SDK for demos that use Qt. 

4) General question of what does core mean?  We need a policy to determine what is in meta-agl and what is outside of meta-agl. 

5) noted that there will be cases where a BSP vendor needs to use an older version of a package (e.g., gstreamer for Porter board in most recent BSP). How will the BSP and SDK provide for this?  

6) and asked about EGL apps and EGL headers in different BSPs. What about MESA headers having different levels in different BSPs?  

I know there was some more discussion after the end of the session that I did not capture notes for among Jan-Simon, Tanikawa, Damian, and another Renesas engineer. 

Overall, I think we need to update the documents and probably the diagram based on this feedback.  Another face to face meeting is being set up for a smaller group in two weeks.