I found that I do not have build/core.
so,I synced again,no error happened ,but I still do not have that directory.
I just downloaded the sourcecode two weeks ago.
What should I do to fix it?


On Wednesday, March 29, 2017 at 4:41:08 AM UTC+8, Dan Willemsen wrote:
>
> It looks like it's not finding your source directory. Running `gettop` 
> should return the absolute path to your source directory. You can override 
> this by setting the TOP environment variable, but it should auto-detect the 
> value if you're in the source directory.
>
> That being said, if your source directory is corrupt due to this move, 
> that could also cause problems -- does build/core/envsetup.mk exist? 
> (build/core should be a symlink to build/make/core). If it doesn't exist, 
> where there any errors from the last `repo sync`?
>
> - Dan
>
> On Tue, Mar 28, 2017 at 7:49 AM darview_cheng <[email protected] 
> <javascript:>> wrote:
>
>> How can I build with the master branch with this change?
>>
>>
>> <https://lh3.googleusercontent.com/-xlgp3uhNcIk/WNpZkBfhIHI/AAAAAAAAAAg/VNACwzIFX9ogEiZTonCgrRb4b5HAll1hQCLcB/s1600/2017-03-28%2B20%253A39%253A23%25E5%25B1%258F%25E5%25B9%2595%25E6%2588%25AA%25E5%259B%25BE.png>
>>
>>
>>
>>
>>
>> 在 2016年10月12日星期三 UTC+8上午3:59:50,Dan Willemsen写道:
>>
>>> I’ll be submitting https://android-review.googlesource.com/286781 
>>> shortly in order to move the `build` project to `build/make`. This will 
>>> only affect the master branch.
>>>
>>>
>>>    - 
>>>    
>>>    If you don’t have any local changes to the build project, just sync 
>>>    like normal, everything should just work.
>>>    
>>>
>>>
>>>    - 
>>>    
>>>    If you have uncommitted changes, your sync will fail, and you’ll 
>>>    either have to commit your changes or reset the files in order to sync.
>>>    
>>>
>>>
>>>    - 
>>>    
>>>    If you have local branches, the safest solution is to backup your 
>>>    changes (to gerrit, or otherwise) before your next sync, then apply them 
>>>    into the new project. If you don’t do that, this command should be able 
>>> to 
>>>    restore your branches, at least until `git gc` runs:
>>>    
>>>
>>> (cd build/make; git fetch ../../.repo/projects/build.git 
>>> refs/heads/*:refs/heads/* refs/published/*:refs/published/*; git config -l 
>>> -f ../../.repo/projects/build.git/config | grep '^branch.' | sed 's/=/ /' | 
>>> xargs -L1 git config)
>>>
>>> If you encounter any problems, please respond here.
>>>
>>> Thanks,
>>> Dan
>>>
>> -- 
>> -- 
>> You received this message because you are subscribed to the "Android 
>> Building" mailing list.
>> To post to this group, send email to [email protected] 
>> <javascript:>
>> To unsubscribe from this group, send email to
>> [email protected] <javascript:>
>> 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 [email protected] <javascript:>.
>> 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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to