Hi, Fengwei

On 1 April 2015 at 17:27, yfw <fengwei.yin@linaro.org> wrote:
Hi list,
I don't know whether this is correct list for my questions. If it's not, please let me know and sorry for the noise.

Yes, this is the right place. 
We have a premium member who is trying to create member build based on
LCR. Here is the first questions they asked:
   What's the difference between AOSP and LCR?
AOSP has many branches, and LCR builds are based on the latest google released version, like the  android-5.1.0_r3 now, which means
it's more stable than the AOSP master branch.
AOSP master branch has the latest source, but it is updated every day, and has the case that even can not build successfully.
 
I downloaded the android source (I suppose it's LCR) by following the link here: https://wiki.linaro.org/Platform/Android/GetSource#Platform_Code_Get_source_and_Building

But normally it's better to download and build the source according to the instruction in following link:
https://releases.linaro.org/latest/android/lcr/armv8-android-juno-lsk#tabs-3


and got couple of questions regarding this source:
1. Is this source code for LCR?
It's source code for LCR, but not the latest version of LCR builds.
The steps there should work as well.

2. I suppose the source code could be divided to two parts:
   - base android src defined by MANIFEST_BRANCH. Which match the same
     tag on Google AOSP exactly even they are from Linaro android git
     server.
   - Addon projects from Linaro defined by local manifest.
   Let me know if I have wrong assumption.
Yes, you are right. 

   This is important because the member is from PRC. It's very easy
   to hit network issue when we download the source from Linaro android
   git server.
hmm, this is different with my experience.
Could they report their error when download source from linaro android server?
 
   If my understanding is correct, we could suggest a temporary
   workaround to member that they download the base android src from
   Google AOSP server. And download addon projects from Linaro server.
Yes, this can work.
changing MANIFEST_REPO in the above link you mentioned to https://android.googlesource.com/platform/manifest
will make it download source from google AOSP server.

3. I noticed there is a directory named "android-patchset" which
   includeds some additional patches. But it looks like LCR doesn't
   apply them. I checked two place:
   - linaro_android_build_cmds.sh. It exports PATCHSETS. But doesn't
     use it.
   - bionic revision in pinned-manifest.xml and the snapshot of AOSP.
     They are exactly same. So no additional patch applied on bionic
     when android-patchset has bionic patch

   Did I miss something here?
If you check the script here:
https://releases.linaro.org/15.03/android/lcr/armv8-android-juno-lsk/linaro_android_build_cmds.sh

you will see lines like following:
# download and apply the patches
git clone git://android.git.linaro.org/android-patchsets.git
for i in $PATCHSETS; do
sh ./android-patchsets/$i
done 
This will help to apply the necessary patches.

--
Best Regards,
Yongqin Liu
---------------------------------------------------------------
#mailing list
linaro-android@lists.linaro.org