why are you trying to do that? soong will automatically give you the
right sysroot when it calls clang.
On Wed, May 22, 2024 at 12:04 PM 'Ashiq Shyam' via Android Building
wrote:
>
> How do I add sysroot/usr/include/android/ that is prebuilts/ndk/ to an
> android.bp that is in external/Helloworl
if you install all the other packages and just don't install that one,
does it work? if so, i'll update the docs.
(i know we've done some work to remove curses dependencies, but i
don't know whether we got them _all_.)
On Tue, May 14, 2024 at 11:04 AM giulio...@gmail.com
wrote:
>
> Hi, i am unab
+the webrtc OWNERS. (because, no, the Android ABI does not include
AVX2. i'm curious why this hasn't caused trouble for folks using the
emulator on older hardware, since the Studio requirements also don't
include AVX2?)
On Tue, Nov 14, 2023 at 9:46 AM Michael Goffioul
wrote:
>
> Since this commit
#x27;ll be
>> following up with a more final solution, but this should also unblock you.
>>
>> Steve
>>
>> On Thu, Sep 21, 2023 at 3:08 PM 'enh' via Android Building
>> wrote:
>>>
>>> thanks! i talked to our llvm folks, and they
--soong_out "out/soong" --out
> "out" -o out/soong/build.ninja --globListDir build --globFile
> out/soong/globs-build.ninja -t -l out/.module_paths/Android.bp.list
> --available_env out/soong/soong.environment.available --used_env
> out/soong/soong.environment.u
what's the renderscript connection here? what's the build error you're seeing?
On Wed, Sep 20, 2023 at 10:06 PM 'Alexander Koskovich' via Android
Building wrote:
>
> AOSP (main) won't compile starting from this version onward. Is there a plan
> to migrate renderscript to a newer Clang version or
i'd guess upgrading your cpu would have more benefit --- but note that
more threads is more important than single-core performance.
On Mon, Sep 18, 2023 at 7:16 PM 洪归风 wrote:
>
> Can you reduce compile times simply by upgrading to faster memory? I'm
> encountering a similar issue where it takes
looks like you're using WSL --- use real Linux instead. (or
https://github.com/android/ndk/issues/1755 suggests that WSL2 might
work better than WSL1.)
On Mon, Sep 18, 2023 at 7:16 PM Kiran Kaur wrote:
>
> hi Team,
>
> I am new to AOSP and trying to build android for raspberry pi 4b but while
>
On Fri, Sep 15, 2023 at 7:16 AM Alexey Pavlyutkin
wrote:
>
> Hi Orion!
>
> Very similar question, but we're interested in RISK-V. If there is a way to
> build standalone ART on top of Linux for RISK-V. The motivation is we develop
> new cores/SOC's and AOSP is far of readiness,
what specificall
no, not unless you're building 32-bit host tools (which isn't true for
any recent release; for older releases you likely need to use an older
version of Ubuntu to build anyway!). i've removed it from the doc.
thanks for pointing this out!
On Thu, Jul 27, 2023 at 5:41 PM dismalbread4106 maps (disma
ith Dsouza' via Android Building <
android-building@googlegroups.com> wrote:
> We'll share builds from aosp-main in a few weeks (we're sorry it's a bit
> delayed).
>
> Thanks for reporting the issue with the BUILD ID we;ll fix that too.
>
>
>
&
and the BUILD_ID when i build still says AOSP.MASTER?
```
PLATFORM_VERSION_CODENAME=VanillaIceCream
PLATFORM_VERSION=VanillaIceCream
PRODUCT_INCLUDE_TAGS=com.android.mainline
TARGET_PRODUCT=aosp_cf_arm64_phone
TARGET_BUILD_VARIANT=userdebug
TARGET_ARCH=a
looks like ci.android.com doesn't have an aosp-main yet?
https://ci.android.com/builds/branches/aosp-main/grid? isn't working for me
(and https://ci.android.com/builds/branches/aosp-master/grid? seems out of
date, as "promised"?)
it also seems like "main" doesn't show up in the gerrit list of bran
lding@googlegroups.com> wrote:
>
>> There is build system support for 64-bit windows binaries, but it's not
>> very well tested. A change like
>> https://android-review.git.corp.google.com/c/platform/build/+/2645079 will
>> produce a 64-bit zipalign.exe.
>
i suspect they mean "i want
https://android-review.googlesource.com/c/platform/build/+/2380864";, the
commit message for which mentions that there's no 64-bit Windows build
support (but you shouldn't need it either --- the OS doesn't support zip64,
so there'd be little use in being able to generate
i get 25min builds on "AMD Ryzen Threadripper PRO 3995WX 64-Cores" (so 128
hyperthreaded cores) and 256GiB of ram. i have no experience with anything
like the configuration you're suggesting, but i'd _definitely_ increase the
ram. i don't remember the last time we built with less than 128GiB. your
On Wed, May 3, 2023 at 12:53 PM Roman Lebedenko wrote:
> Hey,
>
> I am trying to build android source to be able testing unity apps. So I
> pull the master branch,
> ran:
> . build/envsetup.sh
> lunch
> ...
> what build variant should I choose to be able running x86 host based
> emulator with ar
On Thu, Apr 13, 2023 at 7:44 AM Artin Kennedy
wrote:
> Hi all,
> I am new in android. I want to use from m and mm macros. After googling I
> found that must execute envsetup.sh.
>
> This is my main challenge.
>
> before getting build aosp, I get manifest with repo. when runing "repo
> sync" af
machines useful. (similarly with disk space, though it's always
easier to add disk space after the fact than it is memory.)
On Tue, Mar 14, 2023 at 9:19 AM Michael Swartout
wrote:
> You purchased way to much, overkill.
>
> On Tue, Mar 14, 2023 at 10:56 AM 'enh' via Andr
yeah, unfortunately i'm only aware of two options, and they're both
basically "throw money at the problem until it goes away":
1. get a better computer. (256 GiB of ram, 64 cores, and 2 TiB of ssd are
the current default.)
2. build in the cloud.
https://cs.android.com/android/platform/superprojec
(yeah, anecdotally "about a minute" sounds about right for the
machines developers at google have. i've seen 2-3 minutes too.)
On Mon, Feb 6, 2023 at 12:01 PM Michael Swartout
wrote:
>
> Lucky yours only takes 60 seconds. It takes 18 minutes, everytime I make a
> change to almost anything.
>
> O
On Thu, Jan 12, 2023 at 5:03 PM Michael Goffioul
wrote:
> On Wed, Jan 11, 2023 at 2:32 AM 'enh' via Android Building <
> android-building@googlegroups.com> wrote:
>
>> On Tue, Jan 10, 2023 at 5:17 PM Michael Goffioul <
>> michael.goffi...@gmail.com>
On Tue, Jan 10, 2023 at 5:17 PM Michael Goffioul
wrote:
> Well, it turns out I believe there's invalid code in the external camera
> provider HAL, which happens to work only on 32 bits. More specifically,
> this snippet:
> https://cs.android.com/android/platform/superproject/+/master:hardware/int
yeah, until fairly recently we used Ubuntu, but we've been using debian for
the last couple of years. i'd expect either to work.
On Sun, Aug 28, 2022, 18:51 Michael wrote:
> Debian or Ubuntu would work. Google documents show a distribution with the
> .deb packaging system. Will have the right de
which is why i said "whatever timeout that is" --- it's obviously a
_different_ timeout. (or `-t` is broken, but it looks like the message is
coming from elsewhere.)
On Tue, Jun 28, 2022 at 7:49 AM SHUBHAM SALUNKHE <
salunkheshubham1...@gmail.com> wrote:
> But i am giving 120 sec with -t option.
you'll need to find whatever that 30s timeout is and increase it.
On Mon, Jun 27, 2022 at 11:01 AM SHUBHAM SALUNKHE <
salunkheshubham1...@gmail.com> wrote:
> Hi,
> Thanks for solution. it worked but sometime its giving following timeout
> exception after executing command
>
> adb shell dumpsys -t
the wrap.* properties are broken in AOSP right now... (they're broken in S
too.)
here's the workaround to make the wrap. properties work:
adb shell setprop dalvik.vm.force-java-zygote-fork-loop true
adb shell stop
adb shell start
the commands you're using don't look right ... try this instead:
oh, and if you're on a recent AOSP build, you might want to try
cherrypicking
https://android-review.googlesource.com/c/platform/frameworks/base/+/1978990
--- the `wrap.` system properties are a bit broken atm. (the wrap.sh stuff
for apps works fine though.)
On Tue, Feb 15, 2022 at 12:40 PM enh w
you did replace `[process]` with your actual process name, right?
On Tue, Feb 15, 2022 at 12:29 PM SHUBHAM SALUNKHE <
salunkheshubham1...@gmail.com> wrote:
> Hi All,
> I am trying to find memory leak using libmemunreachable library
> in AOSP. i have getting following output on adb shell,
On Tue, Dec 21, 2021 at 1:10 PM Abhayadev S wrote:
>
> Hi,
>
> I have a headless Android 10 device where i am trying to enable the adb by
> default on a "user" mode build.
> Also, I am trying to integrate a custom adb key and hoping to skip the
> usb/adb debugging confirmation on screen.
>
> I h
the CI server has large binaries too:
https://ci.android.com/builds/submitted/8096863/aosp_arm64-userdebug/latest
and so do i locally:
-rwxr-x--- 1 enh primarygroup 67654656 Jan 19 18:28
out/host/windows-x86/bin/adb.exe
but if i run strip on it:
-rwxr-x--- 1 enh primarygroup 5974528 Jan 19 18:31
31 matches
Mail list logo
