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, but we would like to run a seria of microbenches for JIT/AOT and make an output for our core engineers or possibly fix JIT/AOT. Also we need to use custom toolchain to have an ability to make fixes to GNU/LLVM/etc. Where should I dig for that? Thank you
Cheers, Alex On Thursday, November 24, 2022 at 12:45:46 PM UTC+3 Orion Hodson wrote: > The lunch target is arbitrary if doing a host build. The one cited > is plucked from `art/test/README.chroot.md`. > > The `buildbot-build.sh --host` invocation does a fairly minimal host build > and builds all the dependencies needed for ART and libcore tests. > > On Wed, 16 Nov 2022 at 19:08, 'Fabien Sanglard' via Android Building < > [email protected]> wrote: > >> Why not use `aosp_x86_64-eng` target? >> >> ``` >> source build/envsetup.sh >> lunch aosp_x86_64-eng >> m -j62 dalvikvm >> out/host/linux-x86/bin/dalvikvm -showversion >> ``` >> >> Outputs: >> ``` >> ART version 2.1.0 x86_64 >> ``` >> > On Thursday, November 3, 2022 at 1:36:07 PM UTC-7 Kunal Sareen wrote: >> >>> Hi all, >>> >>> I'm trying to build and run the Android Runtime (ART) standalone (i.e. >>> natively) on a Linux (Ubuntu 22.04) system. I'm trying to do this to have a >>> faster turn-around time for development (I'm planning on working on ART for >>> a research project). >>> >>> My understanding is that I need to use the `silvermont-eng` target, >>> which I set using `lunch`. However, if I try to build ART as an APEX >>> package (as is mentioned in the ART build README), then the built >>> executables expect the runtime linker to be at `/system/bin/linker` so fail >>> to run natively on the Linux machine. >>> >>> Here's how I've built the above (I'm using the `master-art` manifest in >>> order to only build ART): >>> ``` >>> repo init -b master-art -u >>> https://android.googlesource.com/platform/manifest >>> source build/envsetup.sh >>> export SOONG_ALLOW_MISSING_DEPENDENCIES=true >>> lunch silvermont-eng >>> TARGET_BUILD_APPS="com.android.art" TARGET_BUILD_UNBUNDLED=true m >>> ``` >>> >>> I presume the issues are related to building an APEX package for ART. Is >>> there a way to not build an APEX package then? >>> >>> Any help you can offer will be much appreciated. >>> >>> Sincerely, >>> Kunal >>> >> -- >> > -- >> 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]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/android-building/48810a16-8c46-4979-a9e6-da11d4f55333n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/android-building/48810a16-8c46-4979-a9e6-da11d4f55333n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/d44fb938-47a4-4c8c-bf5b-ae26503e3e07n%40googlegroups.com.
