Repo sync did not sync "external/chromium_org/third_party/angle_dx11"

311 views
Skip to first unread message

Varun Mehra

unread,
Apr 23, 2014, 4:16:32 PM4/23/14
to android-...@googlegroups.com
I downloaded the Android source code for the first time yesterday. I followed all the instructions listed on the AOSP website. Once the Sync was completed I followed the steps required to build the source code. On 'make' I got an error because make was trying to include files in the "external/chromium_org/third_party/angle_dx11/" directory, but when I browsed to the synched code on my local system, the angle_dx11 folder was not present. So I cloned it from the GIT repository. After cloning from the GIT repository it still can't find some files like "translator_glsl.target.linux-x86.mk". These files are not present in the master branch. I can see them in the following commit: "cf535b38ef0774fa41d36868f25f004ead02f1ef".

Is the Android build broken? What should I do to overcome this problem?

I know this isn't probably a good idea but I downloaded the missing files manually from the commit to my local system. After that I get the following error:

including ./external/chromium_org/Android.mk ...
external/chromium_org/third_party/angle_dx11/src/translator_common.target.linux-arm.mk:1: *** multiple target patterns.  Stop.


Glenn Kasten

unread,
Apr 23, 2014, 6:01:07 PM4/23/14
to android-...@googlegroups.com
I just did repo sync on AOSP master for project external/chromium_org, and do see directory third_party/angle_dx11.
So you may have a corrupt workspace. 
I suggest you preserve your current workspace especially any files you may have changed,
then make a new workspace,
repo sync again, 
verify you have the directory as expected,
then copy over work-in-progress from original workspace.

Conley Owens

unread,
Apr 23, 2014, 9:23:10 PM4/23/14
to android-...@googlegroups.com
> Is the Android build broken? What should I do to overcome this problem?

There has been some work done in the past couple days to update the
chromium_org projects and make sure any fixes made get out to AOSP
immediately. There were a couple of transient states where the build
was broken due to this transition and your error message is identical
to one of them. If you run "repo sync" in your client as Glenn
suggested, you should be fine.
> --
> --
> 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-buildi...@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-buildi...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Shahin Ansari

unread,
Apr 23, 2014, 9:40:14 PM4/23/14
to android-...@googlegroups.com
I had a similar problem. What helped me was that I deleted the parent directory and repo sync'd again. I am sure you know this, but adding the -c switch helps a lot. 
Reply all
Reply to author
Forward
0 new messages