In working on the lsk-v3.18-android tree, I noticed that the android tree has an android/configs directory with an android-base and android-recommended config fragments.
Is there a reason we are using linaro specific config fragments in our CI loops instead of these?
If there are Linaro specific addtions, we should switch to using the android fragments plus smaller linaro-specific fragments, and put comments in our linaro fragments as to why the extra options are needed.
Kevin
We should drop the linaro specific android config fragment. It was added when we did not have android config fragment. We have switched to using android/configs/android-base.cfg for TC2 . Few of the builds still use linaro/configs/android.cfg since it is still around.
On 20 May 2015 at 21:28, Kevin Hilman khilman@linaro.org wrote:
In working on the lsk-v3.18-android tree, I noticed that the android tree has an android/configs directory with an android-base and android-recommended config fragments.
Is there a reason we are using linaro specific config fragments in our CI loops instead of these?
If there are Linaro specific addtions, we should switch to using the android fragments plus smaller linaro-specific fragments, and put comments in our linaro fragments as to why the extra options are needed.
Kevin
Excellent.
I will kill the linaro-specific one in the lsk-v3.18 tree.
Kevin
On Wed, May 20, 2015 at 9:04 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
We should drop the linaro specific android config fragment. It was added when we did not have android config fragment. We have switched to using android/configs/android-base.cfg for TC2 . Few of the builds still use linaro/configs/android.cfg since it is still around.
On 20 May 2015 at 21:28, Kevin Hilman khilman@linaro.org wrote:
In working on the lsk-v3.18-android tree, I noticed that the android tree has an android/configs directory with an android-base and android-recommended config fragments.
Is there a reason we are using linaro specific config fragments in our CI loops instead of these?
If there are Linaro specific addtions, we should switch to using the android fragments plus smaller linaro-specific fragments, and put comments in our linaro fragments as to why the extra options are needed.
Kevin
have you guys discussed putting together a build for v3.18 and Android?
On Wed, May 20, 2015 at 10:14 AM Kevin Hilman khilman@linaro.org wrote:
Excellent.
I will kill the linaro-specific one in the lsk-v3.18 tree.
Kevin
On Wed, May 20, 2015 at 9:04 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
We should drop the linaro specific android config fragment. It was added when we did not have android config fragment. We have switched to using android/configs/android-base.cfg for TC2 . Few of the builds still use linaro/configs/android.cfg since it is still around.
On 20 May 2015 at 21:28, Kevin Hilman khilman@linaro.org wrote:
In working on the lsk-v3.18-android tree, I noticed that the android tree has an android/configs directory with an android-base and android-recommended config fragments.
Is there a reason we are using linaro specific config fragments in our CI loops instead of these?
If there are Linaro specific addtions, we should switch to using the android fragments plus smaller linaro-specific fragments, and put comments in our linaro fragments as to why the extra options are needed.
Kevin
linaro-android@lists.linaro.org
-
Alan Bennett -
Kevin Hilman -
Vishal Bhoj