date:20190628

Re: [android-building] Building an old specific commit in one AOSP project

2019-06-28 Thread 'Colin Cross' via Android Building

You can download the manifest_*.xml file from any build from the date that
you want, then use repo sync -m /tmp/manifest_*.xml to sync the revisions
from that manifest.

On Fri, Jun 28, 2019 at 7:56 AM Alex  wrote:

> Hi folks,
>
> I did not find any related post to my question so I decided to create one.
> However, feel free to link any relevant post I may have missed.
>
> Problem: I would like to build one project in AOSP at a very specific
> commit.
>
> The procedure:
>
>- Find the commit ID
>- Find the appropriate manifest branch (git tag --contains $COMMIT_ID
>) in the appropriate project in the mirror
>- Init the manifest branch from the mirror
>- Checkout the project at $COMMIT_ID
>- Source build/envsetup.sh and do a *mma*
>
>
> However, if this procedure mostly works, sometimes you have a problem
> because the dependencies of your project as not synced and the build fail.
>
> Since Google on its CI (
> https://ci.android.com/builds/branches/aosp-master/grid ) always build
> the tree with the last commit on each repo, the idea was to checkout *every
> *project in AOSP at the date of the commit I want to build (e.g.
> $COMMIT_ID is 15.06.2019, let's checkout every project at this date).
> However, this *fails* because some project are not synced (during the
> sync from the mirror) with their history (e.g prebuilts tools).
>
> I also tried to checkout the master branch from the AOSP mirror but the
> problem remains (e.g. clone-depth of some project is still 1).
>
> My question is rather easy: how do one build a specific commit in one of
> AOSP project.
>
>
> Ps : If you want to reproduce the problem, you may try to build commit 
> 830cb39cb2a0f1bf6704d264e2a5c5029c175dd7
> from platform/system/bt on branch android-9.0.0_r17 .
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/a5befb35-0739-434b-8964-b5ecdfa00eb0%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAMbhsRTScOYrfOLcMuMMZxtuouRHmz7v97iAKWpd3VzQKFSsCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] Is there a way to crosscompile emulator for arm64 ?

2019-06-28 Thread Igor Kukushkin

Hello,
For a very dirty workaround, you may find armtranslator (used in vbox86,
genymotion and in a bunch of noname x86 hdmi sticks) capable of running
some ARM apps with decent performance. Running the whole system (even
trimmed down to Go-style system) would result in penalties ranging in
5-30x, even boot would take ages and you still get the equivalent of very
early cortex core.

As for ARM-on-ARM, right now I believe there are no open products capable
of that AND capable of bootstrapping AOSP (check Xvisor for example), but I
would really love to find it wrong.

Another option would be to buy cheap but powerful boards (ODROID in 4gb
edition?) and tune them (multiple viewports through Surfaceflinger or
Condroid-like approach) , that would save on development time, but it
doesn't scales well (think you'll have a year of amortizing costs with
$10/month).

(I'm currently investigating what are possible opensource options for
lightweight on-device Android virtualization on ARM, color me surprised
anyone?)

--
best,
Igor

On Fri, Jun 28, 2019 at 4:56 PM Yoan Lefevre 
wrote:

> Hello all,
>
> I tried to post this message on the Android Emulator group, but as there
> is not activity since 2017, I have the weird feeling I will not get
> anything there ^^. So here is my problem...
>
> Regarding some needs on a project (scaling + third parties only available
> in arm64), I must run an arm64 emulated device. I saw there and there that
> the arm64 image based used with x86 emulator are not really efficient, and
> people used to go with x86 image based if this solution meets their
> requirements (which here, is not). Facing this issue, I was wondering if
> there were a possibility to rebuild emulator for an arm64 host, and if it
> was interesting (on a performance point of view) to run an arm64 image
> instance with it ?
>
> While waiting for further info, I will dig into the original x86 emulator
> for an arm64 image based, to see by myself if the performance are really
> bad or not...
>
> Thanks !
>
> Regards,
> Yoan Lefevre
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/844dcf81-74ce-4430-bfed-5884eab7ed97%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAK-rsLK%3DSGs6mq8v3%3DPgMwysWnADodM%3DiFCHUrHOeoKqoZXUEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] Build failed with Android 9.0

2019-06-28 Thread 'Dan Willemsen' via Android Building

How did you download it? Based on the banner, that's at least partially
master, not 9.0. A mismatched source tree could explain that error (or it
happened to be broken when you synced, and you should try syncing again if
you do want master).

- Dan

On Fri, Jun 28, 2019, 7:56 AM 岳羽 <384378...@qq.com> wrote:

> Here is all the commands:
> 1. source build/envsetup.sh
> 2. lunch 21 (aosp_x86-eng)
> 3. rm -rf out && make -j4 2>&1 | tee b.log
> than, always show the error log.
>
> On Thursday, June 27, 2019 at 4:54:10 PM UTC+8, Alessio Balsini wrote:
>>
>> Can you please post all the exact commands you ran?
>>
>> Cheers,
>> Alessio
>>
>> On Mon, Jun 24, 2019 at 4:45 PM 岳羽 <3843...@qq.com> wrote:
>> >
>> > I download the source code of AOSP with VMWare Ubuntu18.04, When I
>> build with "rm -rf out && make -j4 2>&1 | tee b.log", always failed.
>> > all the logs below
>> >
>> > 
>> > PLATFORM_VERSION_CODENAME=R
>> > PLATFORM_VERSION=R
>> > TARGET_PRODUCT=aosp_x86_64
>> > TARGET_BUILD_VARIANT=eng
>> > TARGET_BUILD_TYPE=release
>> > TARGET_ARCH=x86_64
>> > TARGET_ARCH_VARIANT=x86_64
>> > TARGET_2ND_ARCH=x86
>> > TARGET_2ND_ARCH_VARIANT=x86_64
>> > HOST_ARCH=x86_64
>> > HOST_2ND_ARCH=x86
>> > HOST_OS=linux
>> > HOST_OS_EXTRA=Linux-4.18.0-23-generic-x86_64-Ubuntu-18.04.2-LTS
>> > HOST_CROSS_OS=windows
>> > HOST_CROSS_ARCH=x86
>> > HOST_CROSS_2ND_ARCH=x86_64
>> > HOST_BUILD_TYPE=release
>> > BUILD_ID=PI
>> > OUT_DIR=out
>> > 
>> > [100% 1/1] out/soong/.minibootstrap/minibp
>> out/soong/.bootstrap/build.ninja
>> > [  1% 2/140] compile out/soong/.bootstrap/blueprint-deptools/pkg/
>> github.com/google/blueprint/deptools.a
>> > [  2% 3/140] compile out/soong/.bootstrap/blueprint-parser/pkg/
>> github.com/google/blueprint/parser.a
>> > [  2% 4/140] compile out/soong/.bootstrap/blueprint-parser/test/
>> github.com/google/blueprint/parser.a
>> > [  3% 5/140] compile out/soong/.bootstrap/blueprint-pathtools/test/
>> github.com/google/blueprint/pathtools.a
>> > [  4% 6/140] compile out/soong/.bootstrap/blueprint-pathtools/pkg/
>> github.com/google/blueprint/pathtools.a
>> > [  5% 7/140] compile out/soong/.bootstrap/blueprint-proptools/test/
>> github.com/google/blueprint/proptools.a
>> > [  5% 8/140] compile out/soong/.bootstrap/gotestmain/obj/gotestmain.a
>> > [  6% 9/140] compile out/soong/.bootstrap/loadplugins/obj/loadplugins.a
>> > [  7% 10/140] compile
>> out/soong/.bootstrap/gotestrunner/obj/gotestrunner.a
>> > [  7% 11/140] compile out/soong/.bootstrap/blueprint-proptools/pkg/
>> github.com/google/blueprint/proptools.a
>> > [  8% 12/140] link out/soong/.bootstrap/gotestmain/obj/a.out
>> > [  9% 13/140] link out/soong/.bootstrap/gotestrunner/obj/a.out
>> > [ 10% 14/140] link out/soong/.bootstrap/loadplugins/obj/a.out
>> > [ 10% 15/140] cp out/soong/.bootstrap/bin/gotestrunner
>> > [ 11% 16/140] cp out/soong/.bootstrap/bin/gotestmain
>> > [ 12% 17/140] cp out/soong/.bootstrap/bin/loadplugins
>> > [ 12% 18/140] gotestmain
>> out/soong/.bootstrap/blueprint-bootstrap-bpdoc/test/test.go
>> > [ 13% 19/140] gotestmain
>> out/soong/.bootstrap/blueprint-parser/test/test.go
>> > [ 14% 20/140] gotestmain out/soong/.bootstrap/blueprint/test/test.go
>> > [ 15% 21/140] gotestmain
>> out/soong/.bootstrap/blueprint-pathtools/test/test.go
>> > [ 15% 22/140] compile out/soong/.bootstrap/blueprint-parser/test/test.a
>> > [ 16% 23/140] compile
>> out/soong/.bootstrap/blueprint-pathtools/test/test.a
>> > [ 17% 24/140] compile out/soong/.bootstrap/blueprint/test/
>> github.com/google/blueprint.a
>> > [ 17% 25/140] link out/soong/.bootstrap/blueprint-parser/test/test
>> > [ 18% 26/140] compile out/soong/.bootstrap/blueprint/pkg/
>> github.com/google/blueprint.a
>> > [ 19% 27/140] compile out/soong/.bootstrap/blueprint/test/test.a
>> > [ 20% 28/140] test github.com/google/blueprint/parser
>> > [ 20% 29/140] link out/soong/.bootstrap/blueprint-pathtools/test/test
>> > [ 21% 30/140] test github.com/google/blueprint/pathtools
>> > [ 22% 31/140] gotestmain
>> out/soong/.bootstrap/blueprint-proptools/test/test.go
>> > [ 22% 32/140] compile
>> out/soong/.bootstrap/blueprint-bootstrap-bpdoc/pkg/
>> github.com/google/blueprint/bootstrap/bpdoc.a
>> > [ 23% 33/140] compile
>> out/soong/.bootstrap/blueprint-bootstrap-bpdoc/test/
>> github.com/google/blueprint/bootstrap/bpdoc.a
>> > [ 24% 34/140] compile
>> out/soong/.bootstrap/blueprint-proptools/test/test.a
>> > [ 25% 35/140] compile
>> out/soong/.bootstrap/blueprint-bootstrap-bpdoc/test/test.a
>> > [ 25% 36/140] compile out/soong/.bootstrap/blueprint-bootstrap/pkg/
>> github.com/google/blueprint/bootstrap.a
>> > [ 26% 37/140] link out/soong/.bootstrap/blueprint-proptools/test/test
>> > [ 27% 38/140] compile out/soong/.bootstrap/soong/pkg/android/soong.a
>> > [ 27% 39/140] gotestmain
>> out/soong/.bootstrap/soong-android/test/test.go
>> > [ 28% 40/140] gotestmain out/soong/.bootstrap/soong-apex/test/test.go
>> > [ 29%

[android-building] Is there a way to crosscompile emulator for arm64 ?

2019-06-28 Thread Yoan Lefevre

Hello all,

I tried to post this message on the Android Emulator group, but as there is 
not activity since 2017, I have the weird feeling I will not get anything 
there ^^. So here is my problem...

Regarding some needs on a project (scaling + third parties only available 
in arm64), I must run an arm64 emulated device. I saw there and there that 
the arm64 image based used with x86 emulator are not really efficient, and 
people used to go with x86 image based if this solution meets their 
requirements (which here, is not). Facing this issue, I was wondering if 
there were a possibility to rebuild emulator for an arm64 host, and if it 
was interesting (on a performance point of view) to run an arm64 image 
instance with it ? 

While waiting for further info, I will dig into the original x86 emulator 
for an arm64 image based, to see by myself if the performance are really 
bad or not...

Thanks !

Regards,
Yoan Lefevre

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/844dcf81-74ce-4430-bfed-5884eab7ed97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] [pixel 3] build the userdebug version to gain adb remount, adb push permission

2019-06-28 Thread jw wang

Hi Alessio

I was missing the steps of binary blob for pixel 3, after installing the 
blob into root of aosp, it works as a charm !

On Thursday, June 27, 2019 at 4:50:21 PM UTC+8, Alessio Balsini wrote:
>
> Hi Jw, 
>
> There are some missing pieces in your procedure, e.g., you didn't 
> mention the device binaries and the flashing procedure is not 
> complete. 
> Please, try again following the documentation: 
> https://source.android.com/setup/build/building. 
>
> Cheers, 
> Alessio 
>
>
> On Mon, Jun 24, 2019 at 4:45 PM jw wang > 
> wrote: 
> > 
> > Hello google, 
> > 
> > not sure if this is the right place for this topic, I bought pixel 3, 
> apparently came with the user build which mean I'm unable to perform adb 
> remount, adb push, so I repo sync android-9.0.0_r11 AOSP, 
> > lunch 19. aosp_blueline-userdebug, , make -j4, after building finish and 
> generate binary result,  my questions are : 
> > 
> > 1. if it's possible to gain adb remount, and adb push permissions from 
> this userdebug build image ?  or additional configuration is needed ? 
> > 2. I'm coping the system.img and boot.img from 
> ubuntu/android-9.0.0_r11/out/target/product/blueline   to windows folder, 
> perform fastboot flash system system.img,   and fastboot flash system 
> boot.img, but it ends up entering a bootloop in bootloader,  should I 
> better do the entire flash in the 
> android-9.0.0_r11/out/target/product/blueline  at my ubuntu  ?? 
> > 
> > 
> > thanks 
> > 
> > -- 
> > -- 
> > You received this message because you are subscribed to the "Android 
> Building" mailing list. 
> > To post to this group, send email to android-...@googlegroups.com 
>  
> > To unsubscribe from this group, send email to 
> > android-...@googlegroups.com  
> > For more options, visit this group at 
> > http://groups.google.com/group/android-building?hl=en 
> > 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups "Android Building" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to android-...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/android-building/fa07f02a-2a7d-482e-abc3-3612072a3189%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/b10db5c4-fcf3-471d-856b-6139d495affa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] Build failed with Android 9.0

2019-06-28 Thread 岳羽

Here is all the commands:
1. source build/envsetup.sh
2. lunch 21 (aosp_x86-eng)
3. rm -rf out && make -j4 2>&1 | tee b.log
than, always show the error log.

On Thursday, June 27, 2019 at 4:54:10 PM UTC+8, Alessio Balsini wrote:
>
> Can you please post all the exact commands you ran? 
>
> Cheers, 
> Alessio 
>
> On Mon, Jun 24, 2019 at 4:45 PM 岳羽 <3843...@qq.com > wrote: 
> > 
> > I download the source code of AOSP with VMWare Ubuntu18.04, When I build 
> with "rm -rf out && make -j4 2>&1 | tee b.log", always failed. 
> > all the logs below 
> > 
> >  
> > PLATFORM_VERSION_CODENAME=R 
> > PLATFORM_VERSION=R 
> > TARGET_PRODUCT=aosp_x86_64 
> > TARGET_BUILD_VARIANT=eng 
> > TARGET_BUILD_TYPE=release 
> > TARGET_ARCH=x86_64 
> > TARGET_ARCH_VARIANT=x86_64 
> > TARGET_2ND_ARCH=x86 
> > TARGET_2ND_ARCH_VARIANT=x86_64 
> > HOST_ARCH=x86_64 
> > HOST_2ND_ARCH=x86 
> > HOST_OS=linux 
> > HOST_OS_EXTRA=Linux-4.18.0-23-generic-x86_64-Ubuntu-18.04.2-LTS 
> > HOST_CROSS_OS=windows 
> > HOST_CROSS_ARCH=x86 
> > HOST_CROSS_2ND_ARCH=x86_64 
> > HOST_BUILD_TYPE=release 
> > BUILD_ID=PI 
> > OUT_DIR=out 
> >  
> > [100% 1/1] out/soong/.minibootstrap/minibp 
> out/soong/.bootstrap/build.ninja 
> > [  1% 2/140] compile out/soong/.bootstrap/blueprint-deptools/pkg/
> github.com/google/blueprint/deptools.a 
> > [  2% 3/140] compile out/soong/.bootstrap/blueprint-parser/pkg/
> github.com/google/blueprint/parser.a 
> > [  2% 4/140] compile out/soong/.bootstrap/blueprint-parser/test/
> github.com/google/blueprint/parser.a 
> > [  3% 5/140] compile out/soong/.bootstrap/blueprint-pathtools/test/
> github.com/google/blueprint/pathtools.a 
> > [  4% 6/140] compile out/soong/.bootstrap/blueprint-pathtools/pkg/
> github.com/google/blueprint/pathtools.a 
> > [  5% 7/140] compile out/soong/.bootstrap/blueprint-proptools/test/
> github.com/google/blueprint/proptools.a 
> > [  5% 8/140] compile out/soong/.bootstrap/gotestmain/obj/gotestmain.a 
> > [  6% 9/140] compile out/soong/.bootstrap/loadplugins/obj/loadplugins.a 
> > [  7% 10/140] compile 
> out/soong/.bootstrap/gotestrunner/obj/gotestrunner.a 
> > [  7% 11/140] compile out/soong/.bootstrap/blueprint-proptools/pkg/
> github.com/google/blueprint/proptools.a 
> > [  8% 12/140] link out/soong/.bootstrap/gotestmain/obj/a.out 
> > [  9% 13/140] link out/soong/.bootstrap/gotestrunner/obj/a.out 
> > [ 10% 14/140] link out/soong/.bootstrap/loadplugins/obj/a.out 
> > [ 10% 15/140] cp out/soong/.bootstrap/bin/gotestrunner 
> > [ 11% 16/140] cp out/soong/.bootstrap/bin/gotestmain 
> > [ 12% 17/140] cp out/soong/.bootstrap/bin/loadplugins 
> > [ 12% 18/140] gotestmain 
> out/soong/.bootstrap/blueprint-bootstrap-bpdoc/test/test.go 
> > [ 13% 19/140] gotestmain 
> out/soong/.bootstrap/blueprint-parser/test/test.go 
> > [ 14% 20/140] gotestmain out/soong/.bootstrap/blueprint/test/test.go 
> > [ 15% 21/140] gotestmain 
> out/soong/.bootstrap/blueprint-pathtools/test/test.go 
> > [ 15% 22/140] compile out/soong/.bootstrap/blueprint-parser/test/test.a 
> > [ 16% 23/140] compile 
> out/soong/.bootstrap/blueprint-pathtools/test/test.a 
> > [ 17% 24/140] compile out/soong/.bootstrap/blueprint/test/
> github.com/google/blueprint.a 
> > [ 17% 25/140] link out/soong/.bootstrap/blueprint-parser/test/test 
> > [ 18% 26/140] compile out/soong/.bootstrap/blueprint/pkg/
> github.com/google/blueprint.a 
> > [ 19% 27/140] compile out/soong/.bootstrap/blueprint/test/test.a 
> > [ 20% 28/140] test github.com/google/blueprint/parser 
> > [ 20% 29/140] link out/soong/.bootstrap/blueprint-pathtools/test/test 
> > [ 21% 30/140] test github.com/google/blueprint/pathtools 
> > [ 22% 31/140] gotestmain 
> out/soong/.bootstrap/blueprint-proptools/test/test.go 
> > [ 22% 32/140] compile out/soong/.bootstrap/blueprint-bootstrap-bpdoc/pkg/
> github.com/google/blueprint/bootstrap/bpdoc.a 
> > [ 23% 33/140] compile 
> out/soong/.bootstrap/blueprint-bootstrap-bpdoc/test/
> github.com/google/blueprint/bootstrap/bpdoc.a 
> > [ 24% 34/140] compile 
> out/soong/.bootstrap/blueprint-proptools/test/test.a 
> > [ 25% 35/140] compile 
> out/soong/.bootstrap/blueprint-bootstrap-bpdoc/test/test.a 
> > [ 25% 36/140] compile out/soong/.bootstrap/blueprint-bootstrap/pkg/
> github.com/google/blueprint/bootstrap.a 
> > [ 26% 37/140] link out/soong/.bootstrap/blueprint-proptools/test/test 
> > [ 27% 38/140] compile out/soong/.bootstrap/soong/pkg/android/soong.a 
> > [ 27% 39/140] gotestmain out/soong/.bootstrap/soong-android/test/test.go 
> > [ 28% 40/140] gotestmain out/soong/.bootstrap/soong-apex/test/test.go 
> > [ 29% 41/140] gotestmain out/soong/.bootstrap/soong-bpf/test/test.go 
> > [ 30% 42/140] test github.com/google/blueprint/proptools 
> > [ 30% 43/140] link out/soong/.bootstrap/blueprint/test/test 
> > [ 31% 44/140] gotestmain out/soong/.bootstrap/soong-cc/test/test.go 
> > [ 32% 45/140] gotestmain 
> out/soong/.bootstrap/soong-cc-config/test/test.

[android-building] Building an old specific commit in one AOSP project

2019-06-28 Thread Alex

Hi folks,

I did not find any related post to my question so I decided to create one. 
However, feel free to link any relevant post I may have missed.

Problem: I would like to build one project in AOSP at a very specific 
commit.

The procedure:

   - Find the commit ID
   - Find the appropriate manifest branch (git tag --contains $COMMIT_ID ) 
   in the appropriate project in the mirror
   - Init the manifest branch from the mirror
   - Checkout the project at $COMMIT_ID
   - Source build/envsetup.sh and do a *mma*


However, if this procedure mostly works, sometimes you have a problem 
because the dependencies of your project as not synced and the build fail.

Since Google on its CI ( 
https://ci.android.com/builds/branches/aosp-master/grid ) always build the 
tree with the last commit on each repo, the idea was to checkout *every 
*project 
in AOSP at the date of the commit I want to build (e.g. $COMMIT_ID is 
15.06.2019, let's checkout every project at this date). However, this 
*fails* because some project are not synced (during the sync from the 
mirror) with their history (e.g prebuilts tools).

I also tried to checkout the master branch from the AOSP mirror but the 
problem remains (e.g. clone-depth of some project is still 1).

My question is rather easy: how do one build a specific commit in one of 
AOSP project.


Ps : If you want to reproduce the problem, you may try to build commit 
830cb39cb2a0f1bf6704d264e2a5c5029c175dd7 
from platform/system/bt on branch android-9.0.0_r17 .

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/a5befb35-0739-434b-8964-b5ecdfa00eb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-building] Building an old specific commit in one AOSP project

Re: [android-building] Is there a way to crosscompile emulator for arm64 ?

Re: [android-building] Build failed with Android 9.0

[android-building] Is there a way to crosscompile emulator for arm64 ?

Re: [android-building] [pixel 3] build the userdebug version to gain adb remount, adb push permission

Re: [android-building] Build failed with Android 9.0

[android-building] Building an old specific commit in one AOSP project

7 matches

Site Navigation

Mail list logo

Footer information