Skip to content
  1. Jan 20, 2021
  2. Jan 19, 2021
  3. Jan 18, 2021
    • Inseob Kim's avatar
      Implement directed vendor snapshot · 7cf1465d
      Inseob Kim authored
      Vendors can now generate only needed modules by setting the following
      Makefile variables:
      
      - DIRECTED_VENDOR_SNAPSHOT: set to true
      - VENDOR_SNAPSHOT_MODULES: list of snapshot candidates
      
      e.g.
      
      DIRECTED_VENDOR_SNAPSHOT := true
      VENDOR_SNAPSHOT_MODULES := toybox_vendor sh_vendor libbase libcutils ...
      
      Bug: 157967325
      Test: m dist vendor-snapshot after setting those in BoardConfig.mk
      Change-Id: I6515a43d9358d94483d7c7fa2b066f9dd457f6aa
      7cf1465d
    • Inseob Kim's avatar
      Refine sysprop_library header rules · 0641004a
      Inseob Kim authored
      Instead of unreliable giant if clause, it's enough to check dependency
      between platform (system, system-ext), product, and vendor.
      
      Test: sysprop_test soong test
      Test: link against host_supported sysprop_library and use internal props
      Change-Id: I7bd5df00b302fa261eff5120106aacc3df93c1b2
      0641004a
  4. Jan 16, 2021
  5. Jan 15, 2021
    • Treehugger Robot's avatar
      Merge "Add java_boot_libs to sdk" · 2b72906a
      Treehugger Robot authored
      2b72906a
    • Chih-Hung Hsieh's avatar
      add more global default checks · 34850d35
      Chih-Hung Hsieh authored
      Test: make with and without WITH_TIDY=1
      Change-Id: Iee07707158f7204e961970ba4d518403b3b2aaf3
      34850d35
    • Chih-Hung Hsieh's avatar
      WITH_TIDY=1 implies -warnings-as-errors=-* · 1b4934a2
      Chih-Hung Hsieh authored
      * This allows local projects to enable clang-tidy
        and catch errors in a default build, but allows
        all warnings in a global build with WITH_TIDY=1.
      
      Test: make with WITH_TIDY=1
      Change-Id: I92a10af24b23ee9f04eebb0513e8f611dd7dcf59
      1b4934a2
    • Chris Parsons's avatar
      Improve aquery-related validation and error handling · 4f069891
      Chris Parsons authored
      Also introduce test suite for aquery handling
      
      Test: m nothing
      Test: lunch aosp_flame && USE_BAZEL_ANALYSIS=1 m libc
      Change-Id: I2493d42782099ea0b575968fca38bce6f0d59015
      4f069891
    • Paul Duffin's avatar
      Export dex implementation jars from prebuilt_apex · 064b70c9
      Paul Duffin authored
      Dexpreopt and boot jars package check all require access to dex
      implementation jars created for java_library and java_sdk_library. They
      were available when building from source but not when building from
      prebuilts, even though they are embedded within the .apex files that
      are referenced from prebuilt_apex.
      
      This changes adds support to prebuilt_apex to export the dex
      implementation jars and updates java_import to use those exported dex
      implementation jars.
      
      In a source build dexpreopt/boot jars package check access the apex (or
      platform) specific variant of a java_library, e.g. core-oj, from which
      it retrieves the dex implementation jar path.
      
      After this change in a prebuilt build dexpreopt/boot jars package check
      behave in the same way except in this case they retrieve the dex
      implementation jar path from the apex (or platform) specific variant of
      the java_import, e.g. core-oj.
      
      The work to export files from a `.apex` file for use by other modules
      is performed by a new `deapexer` module type. It is not used directly
      in an `Android.bp` file but instead is created implicitly by
      `prebuilt_apex`,
      
      In order to do that this contains the following changes:
      * Adds a new `dexapexer` module type to handle the exporting of files
        from the `.apex` file.
      * Adds an exported_java_libs property to prebuilt_apex to specify the
        set of libraries whose dex implementation jars need exporting.
      * Creates apex specific variants of the libraries listed in the
        exported_java_libs property.
      * Adds the set of exported files to the ApexInfo to make them available
        to the apex specific variants.
      * Prevents the prebuilt_apex variants from being merged together as
        they will not be compatible.
      * Modifies java_import to use the exported file for variants of a
        prebuilt_apex.
      * Adds a ninja rule to unpack (using deapexer) the contents of the
        prebuilt_apex's apex file, verify that the required files are present
        and make them available as outputs for other rules to use.
      * Some minor refactorings to support these changes.
      * Adds tests to cover prebuilt only, prebuilt with source preferred,
        and prebuilt preferred with source.
      
      Test: m nothing
      Bug: 171061220
      Change-Id: Ic9bed81fb65b92f0d59f64c0bce168a9ed44cfac
      064b70c9
    • Paul Duffin's avatar
      Add java_boot_libs to sdk · db170e4a
      Paul Duffin authored
      The build has some implicit dependencies (via the boot jars
      configuration) on a number of modules, e.g. core-oj, apache-xml, that
      are part of the java boot class path and which are provided by mainline
      modules (e.g. art, conscrypt, runtime-i18n) but which are not otherwise
      used outside those mainline modules.
      
      As they are not needed outside the mainline modules adding them to
      the sdk/module-exports as either java_libs, or java_header_libs would
      end up exporting more information than was strictly necessary. This
      change adds the java_boot_libs property to allow those modules to be
      exported as part of the sdk/module_exports without exposing any
      unnecessary information.
      
      Some points to note:
      * The java_import has to have a valid file for the src property
        otherwise it will be disabled.
      * The src property is supposed to reference a jar file but the
        java_boot_libs property will make it reference an empty file (not
        an empty jar) so that any attempt to use that file as a jar, e.g.
        compiling against it, will cause a build failure.
      * The name of the file passed to the src property should make it
        clear that the file is not intended to be used.
      * The test makes sure that only the jar file is copied to the
        snapshot.
      
      Test: m nothing
      Bug: 171061220
      Change-Id: I175331e4c8e3874ab70a67cdc2f76ed1576e41eb
      db170e4a
    • Colin Cross's avatar
    • Inseob Kim's avatar
      Allow sysprop library API files to be missing · c9770d6a
      Inseob Kim authored
      If sysprop library contains only internal properties, the API txt file
      will be empty. This allows the API files to be missing in such cases to
      turn off API-Review bit.
      
      Bug: 177036449
      Test: manual test
      Change-Id: I8cb0b10e135cf211dae45ab14ccc9bc04e248634
      c9770d6a
Loading