force_build_llvm_components_defaults
name
,
srcs
,
host_supported
,
device_supported
,
aidl
,
allow_undefined_symbols
,
apex_available
,
arch
,
asflags
,
auto_gen_config
,
bootstrap
,
c_std
,
cflags
,
clang
,
clang_asflags
,
clang_cflags
,
compile_multilib
,
conlyflags
,
corpus
,
cpp_std
,
cppflags
,
data
,
debug
,
defaults
,
defaults_visibility
,
device_specific
,
dictionary
,
disable_framework
,
dist
,
double_loadable
,
enabled
,
exclude_shared_libs
,
exclude_srcs
,
exclude_static_libs
,
export_cflags
,
export_generated_headers
,
export_header_lib_headers
,
export_include_dirs
,
export_shared_lib_headers
,
export_static_lib_headers
,
export_system_include_dirs
,
force_symbols_not_weak_list
,
force_symbols_weak_list
,
fuzz_config
,
generated_headers
,
generated_sources
,
gnu_extensions
,
group_static_libs
,
gtest
,
header_abi_checker
,
header_libs
,
host_ldlibs
,
host_required
,
include_build_directory
,
include_dirs
,
init_rc
,
inject_bssl_hash
,
installable
,
instruction_set
,
isolated
,
ldflags
,
licenses
,
linker_script
,
local_include_dirs
,
logtags
,
lto
,
min_sdk_version
,
multilib
,
native_bridge_supported
,
native_coverage
,
no_libcrt
,
no_named_install_directory
,
nocrt
,
notice
,
objs
,
openmp
,
overrides
,
owner
,
pack_relocations
,
pgo
,
prefix_symbols
,
product_specific
,
proprietary
,
proto
,
ramdisk
,
ramdisk_available
,
recovery
,
recovery_available
,
relative_install_path
,
renderscript
,
require_root
,
required
,
rtti
,
runtime_libs
,
sanitize
,
sdk_variant_only
,
sdk_version
,
shared
,
shared_libs
,
soc_specific
,
sort_bss_symbols_by_size
,
static
,
static_executable
,
static_libs
,
static_ndk_lib
,
stem
,
stl
,
strip
,
stubs
,
suffix
,
symlink_preferred_arch
,
symlinks
,
system_ext_specific
,
system_shared_libs
,
target
,
target.host
,
target.platform
,
target.ramdisk
,
target.recovery
,
target.vendor
,
target_required
,
test_config
,
test_config_template
,
test_for
,
test_mainline_modules
,
test_min_api_level
,
test_min_sdk_version
,
test_options
,
test_per_src
,
test_suites
,
tidy
,
tidy_checks
,
tidy_checks_as_errors
,
tidy_flags
,
unexported_symbols_list
,
unique_host_soname
,
use_apex_name_macro
,
use_clang_lld
,
use_version_lib
,
vendor
,
vendor_available
,
version_script
,
vintf_fragments
,
visibility
,
vndk
,
whole_static_libs
,
yacc
name
string, The name of the module. Must be unique across all modules.
srcs
list of strings, list of source files used to compile the C/C++ module. May be .c, .cpp, or .S files.
srcs may reference the outputs of other modules that produce source files like genrule
or filegroup using the syntax ":module".
host_supported
bool, If set to true, build a variant of the module for the host. Defaults to false.
device_supported
bool, If set to true, build a variant of the module for the device. Defaults to true.
⊕aidl
include_dirs
list of strings, list of directories that will be added to the aidl include paths.
local_include_dirs
list of strings, list of directories relative to the Blueprints file that will
be added to the aidl include paths.
generate_traces
bool, whether to generate traces (for systrace) for this interface
allow_undefined_symbols
bool, allow the module to contain undefined symbols. By default,
modules cannot contain undefined symbols that are not satisified by their immediate
dependencies. Set this flag to true to remove --no-undefined from the linker flags.
This flag should only be necessary for compiling low-level libraries like libc.
apex_available
list of strings, Availability of this module in APEXes. Only the listed APEXes can contain
this module. If the module has stubs then other APEXes and the platform may
access it through them (subject to visibility).
"//apex_available:anyapex" is a pseudo APEX name that matches to any APEX.
"//apex_available:platform" refers to non-APEX partitions like "system.img".
Default is ["//apex_available:platform"].
arch
interface
asflags
list of strings, list of module-specific flags that will be used for .S compiles
auto_gen_config
bool, Flag to indicate whether or not to create test config automatically. If AndroidTest.xml
doesn't exist next to the Android.bp, this attribute doesn't need to be set to true
explicitly.
bootstrap
bool, Allows this module to use non-APEX version of libraries. Useful
for building binaries that are started before APEXes are activated.
c_std
string, C standard version to use. Can be a specific version (such as "gnu11"),
"experimental" (which will use draft versions like C1x when available),
or the empty string (which will use the default).
cflags
list of strings, list of module-specific flags that will be used for C and C++ compiles.
clang
bool, Deprecated. true is the default, false is invalid.
clang_asflags
list of strings, list of module-specific flags that will be used for .S compiles when
compiling with clang
clang_cflags
list of strings, list of module-specific flags that will be used for C and C++ compiles when
compiling with clang
compile_multilib
string, control whether this module compiles for 32-bit, 64-bit, or both. Possible values
are "32" (compile for 32-bit only), "64" (compile for 64-bit only), "both" (compile for both
architectures), or "first" (compile for 64-bit on a 64-bit platform, and 32-bit on a 32-bit
platform
conlyflags
list of strings, list of module-specific flags that will be used for C compiles
corpus
list of strings, Optional list of seed files to be installed to the fuzz target's output
directory.
cpp_std
string, C++ standard version to use. Can be a specific version (such as
"gnu++11"), "experimental" (which will use draft versions like C++1z when
available), or the empty string (which will use the default).
cppflags
list of strings, list of module-specific flags that will be used for C++ compiles
data
list of strings, list of files or filegroup modules that provide data that should be installed alongside
the test
⊕debug, release
cflags
list of strings, list of module-specific flags that will be used for C and C++ compiles in debug or
release builds
defaults
list of strings
defaults_visibility
list of strings, Controls the visibility of the defaults module itself.
device_specific
bool, whether this module is specific to a device, not only for SoC, but also for off-chip
peripherals. When set to true, it is installed into /odm (or /vendor/odm if odm partition
does not exist, or /system/vendor/odm if both odm and vendor partitions do not exist).
This implies `soc_specific:true`.
dictionary
string, Optional dictionary to be installed to the fuzz target's output directory.
disable_framework
bool, Add RunCommandTargetPreparer to stop framework before the test and start it after the test.
⊕dist
targets
list of strings, copy the output of this module to the $DIST_DIR when `dist` is specified on the
command line and any of these targets are also on the command line, or otherwise
built
dest
string, The name of the output artifact. This defaults to the basename of the output of
the module.
dir
string, The directory within the dist directory to store the artifact. Defaults to the
top level directory ("").
suffix
string, A suffix to add to the artifact file name (before any extension).
double_loadable
bool, whether this module is capable of being loaded with other instance
(possibly an older version) of the same module in the same process.
Currently, a shared library that is a member of VNDK (vndk: {enabled: true})
can be double loaded in a vendor process if the library is also a
(direct and indirect) dependency of an LLNDK library. Such libraries must be
explicitly marked as `double_loadable: true` by the owner, or the dependency
from the LLNDK lib should be cut if the lib is not designed to be double loaded.
enabled
bool, emit build rules for this module
Disabling a module should only be done for those modules that cannot be built
in the current environment. Modules that can build in the current environment
but are not usually required (e.g. superceded by a prebuilt) should not be
disabled as that will prevent them from being built by the checkbuild target
and so prevent early detection of changes that have broken those modules.
exclude_shared_libs
list of strings, list of shared libs that should not be used to build this module
exclude_srcs
list of strings, list of source files that should not be used to build the C/C++ module.
This is most useful in the arch/multilib variants to remove non-common files
exclude_static_libs
list of strings, list of static libs that should not be used to build this module
export_cflags
list of strings, list of plain cc flags to be used for any module that links against this module.
export_include_dirs
list of strings, list of directories relative to the Blueprints file that will
be added to the include path (using -I) for this module and any module that links
against this module. Directories listed in export_include_dirs do not need to be
listed in local_include_dirs.
export_system_include_dirs
list of strings, list of directories that will be added to the system include path
using -isystem for this module and any module that links against this module.
force_symbols_not_weak_list
string, local file name to pass to the linker as -force_symbols_not_weak_list
force_symbols_weak_list
string, local file name to pass to the linker as -force_symbols_weak_list
fuzz_config
FuzzConfig, Config for running the target on fuzzing infrastructure.
generated_sources
list of strings, list of generated sources to compile. These are the names of gensrcs or
genrule modules.
gnu_extensions
bool, if set to false, use -std=c++* instead of -std=gnu++*
group_static_libs
bool, group static libraries. This can resolve missing symbols issues with interdependencies
between static libraries, but it is generally better to order them correctly instead.
gtest
bool, if set, build against the gtest library. Defaults to true.
Properties for ABI compatibility checker
enabled
bool, Enable ABI checks (even if this is not an LLNDK/VNDK lib)
symbol_file
string, Path to a symbol file that specifies the symbols to be included in the generated
ABI dump file
exclude_symbol_versions
list of strings, Symbol versions that should be ignored from the symbol file
exclude_symbol_tags
list of strings, Symbol tags that should be ignored from the symbol file
host_ldlibs
list of strings, -l arguments to pass to linker for host-provided shared libraries
host_required
list of strings, names of other modules to install on host if this module is installed
include_build_directory
bool, Add the directory containing the Android.bp file to the list of include
directories. Defaults to true.
include_dirs
list of strings, list of directories relative to the root of the source tree that will
be added to the include path using -I.
If possible, don't use this. If adding paths from the current directory use
local_include_dirs, if adding paths from other modules use export_include_dirs in
that module.
init_rc
list of strings, init.rc files to be installed if this module is installed
inject_bssl_hash
bool, Inject boringssl hash into the shared library. This is only intended for use by external/boringssl.
installable
bool
instruction_set
string, the instruction set architecture to use to compile the C/C++
module.
isolated
bool, if set, use the isolated gtest runner. Defaults to false.
ldflags
list of strings, list of module-specific flags that will be used for all link steps
licenses
list of strings, Names of the licenses that apply to this module.
linker_script
string, if set, the path to a linker script to pass to ld -r when combining multiple object files.
local_include_dirs
list of strings, list of directories relative to the Blueprints file that will
be added to the include path using -I
logtags
list of strings, *.logtags files, to combine together in order to generate the /system/etc/event-log-tags
file
⊕lto
Lto must violate capitialization style for acronyms so that it can be
referred to in blueprint files as "lto"
never
bool
full
bool
thin
bool
min_sdk_version
string, Minimum sdk version that the artifact should support when it runs as part of mainline modules(APEX).
multilib
interface
native_bridge_supported
bool, Whether this module is built for non-native architecures (also known as native bridge binary)
native_coverage
bool
no_libcrt
bool, don't link in libclang_rt.builtins-*.a
no_named_install_directory
bool, Disables the creation of a test-specific directory when used with
relative_install_path. Useful if several tests need to be in the same
directory, but test_per_src doesn't work.
nocrt
bool, don't link in crt_begin and crt_end. This flag should only be necessary for
compiling crt or libc.
notice
string, relative path to a file to include in the list of notices for the device
objs
list of strings, names of other cc_object modules to link into this module using partial linking
openmp
bool, Build and link with OpenMP
overrides
list of strings, Names of modules to be overridden. Listed modules can only be other binaries
(in Make or Soong).
This does not completely prevent installation of the overridden binaries, but if both
binaries would be installed by default (in PRODUCT_PACKAGES) the other binary will be removed
from PRODUCT_PACKAGES.
owner
string, vendor who owns this module
pack_relocations
bool, Generate compact dynamic relocation table, default true.
⊕pgo
instrumentation
bool
sampling
bool
profile_file
string
benchmarks
list of strings
enable_profile_use
bool
cflags
list of strings, Additional compiler flags to use when building this module
for profiling (either instrumentation or sampling).
prefix_symbols
string, if set, add an extra objcopy --prefix-symbols= step
product_specific
bool, whether this module is specific to a software configuration of a product (e.g. country,
network operator, etc). When set to true, it is installed into /product (or
/system/product if product partition does not exist).
proprietary
bool, whether this is a proprietary vendor module, and should be installed into /vendor
⊕proto
type
string, Proto generator type. C++: full or lite. Java: micro, nano, stream, or lite.
plugin
string, Proto plugin to use as the generator. Must be a cc_binary_host module.
include_dirs
list of strings, list of directories that will be added to the protoc include paths.
local_include_dirs
list of strings, list of directories relative to the bp file that will
be added to the protoc include paths.
canonical_path_from_root
bool, whether to identify the proto files from the root of the
source tree (the original method in Android, useful for
android-specific protos), or relative from where they were
specified (useful for external/third party protos).
This defaults to true today, but is expected to default to
false in the future.
static
bool, Link statically against the protobuf runtime
ramdisk
bool, Whether this module is installed to ramdisk
ramdisk_available
bool, Make this module available when building for ramdisk
recovery
bool, Whether this module is installed to recovery partition
recovery_available
bool, Make this module available when building for recovery
relative_install_path
string, install to a subdirectory of the default install path for the module
⊕renderscript
include_dirs
list of strings, list of directories that will be added to the llvm-rs-cc include paths
flags
list of strings, list of flags that will be passed to llvm-rs-cc
target_api
string, Renderscript API level to target
require_root
bool, Add RootTargetPreparer to auto generated test config. This guarantees the test to run
with root permission.
required
list of strings, names of other modules to install if this module is installed
rtti
bool, pass -frtti instead of -fno-rtti
runtime_libs
list of strings, list of modules that should be installed with this module. This is similar to 'required'
but '.vendor' suffix will be appended to the module names if the shared libraries have
vendor variants and this module uses VNDK.
⊕sanitize
enable AddressSanitizer, ThreadSanitizer, or UndefinedBehaviorSanitizer
never
bool
address
bool, main sanitizers
thread
bool
hwaddress
bool
undefined
bool, local sanitizers
all_undefined
bool
misc_undefined
list of strings
fuzzer
bool
safestack
bool
cfi
bool
integer_overflow
bool
scudo
bool
scs
bool
⊕diag
Sanitizers to run in the diagnostic mode (as opposed to the release mode).
Replaces abort() on error with a human-readable error message.
Address and Thread sanitizers always run in diagnostic mode.
undefined
bool
cfi
bool
integer_overflow
bool
misc_undefined
list of strings
no_recover
list of strings
recover
list of strings, value to pass to -fsanitize-recover=
blacklist
string, value to pass to -fsanitize-blacklist
sdk_variant_only
bool, If true, always create an sdk variant and don't create a platform variant.
sdk_version
string, Minimum sdk version supported when compiling against the ndk. Setting this property causes
two variants to be built, one for the platform and one for apps.
shared
StaticOrSharedProperties
shared_libs
list of strings, list of modules that should be dynamically linked into this module.
soc_specific
bool, whether this module is specific to an SoC (System-On-a-Chip). When set to true,
it is installed into /vendor (or /system/vendor if vendor partition does not exist).
sort_bss_symbols_by_size
bool, Order symbols in .bss section by their sizes. Only useful for shared libraries.
static
StaticOrSharedProperties
static_executable
bool, compile executable with -static
static_libs
list of strings, list of modules that should be statically linked into this module.
static_ndk_lib
bool
stem
string, set the name of the output
stl
string, Select the STL library to use. Possible values are "libc++",
"libc++_static", "libstdc++", or "none". Leave blank to select the
default.
⊕strip
none
bool
all
bool
keep_symbols
bool
keep_symbols_list
list of strings
keep_symbols_and_debug_frame
bool
⊕stubs
symbol_file
string, Relative path to the symbol map. The symbol map provides the list of
symbols that are exported for stubs variant of this library.
versions
list of strings, List versions to generate stubs libs for.
suffix
string, set suffix of the name of the output
symlink_preferred_arch
bool, if set, install a symlink to the preferred architecture
symlinks
list of strings, install symlinks to the binary. Symlink names will have the suffix and the binary
extension (if any) appended
system_ext_specific
bool, whether this module extends system. When set to true, it is installed into /system_ext
(or /system/system_ext if system_ext partition does not exist).
system_shared_libs
list of strings, list of system libraries that will be dynamically linked to
shared library and executable modules. If unset, generally defaults to libc,
libm, and libdl. Set to [] to prevent linking against the defaults.
target
interface
⊕target.host, target.android
⊕target.platform
shared_libs
list of strings, list of shared libs that should be use to build the platform variant
of a module that sets sdk_version. This should rarely be necessary,
in most cases the same libraries are available for the SDK and platform
variants.
⊕target.ramdisk
static_libs
list of strings, list of static libs that only should be used to build the recovery
variant of the C/C++ module.
exclude_shared_libs
list of strings, list of shared libs that should not be used to build
the ramdisk variant of the C/C++ module.
exclude_static_libs
list of strings, list of static libs that should not be used to build
the ramdisk variant of the C/C++ module.
⊕target.recovery
srcs
list of strings, list of source files that should only be used in the
recovery variant of the C/C++ module.
exclude_srcs
list of strings, list of source files that should not be used to
build the recovery variant of the C/C++ module.
cflags
list of strings, List of additional cflags that should be used to build the recovery
variant of the C/C++ module.
shared_libs
list of strings, list of shared libs that only should be used to build the recovery
variant of the C/C++ module.
static_libs
list of strings, list of static libs that only should be used to build the recovery
variant of the C/C++ module.
exclude_shared_libs
list of strings, list of shared libs that should not be used to build
the recovery variant of the C/C++ module.
exclude_static_libs
list of strings, list of static libs that should not be used to build
the recovery variant of the C/C++ module.
⊕target.vendor
srcs
list of strings, list of source files that should only be used in the
vendor variant of the C/C++ module.
exclude_srcs
list of strings, list of source files that should not be used to
build the vendor variant of the C/C++ module.
cflags
list of strings, List of additional cflags that should be used to build the vendor
variant of the C/C++ module.
override_export_include_dirs
list of strings, list of exported include directories, like
export_include_dirs, that will be applied to the
vendor variant of this library. This will overwrite
any other declarations.
shared_libs
list of strings, list of shared libs that only should be used to build the vendor
variant of the C/C++ module.
static_libs
list of strings, list of static libs that only should be used to build the vendor
variant of the C/C++ module.
exclude_shared_libs
list of strings, list of shared libs that should not be used to build the vendor variant
of the C/C++ module.
exclude_static_libs
list of strings, list of static libs that should not be used to build the vendor variant
of the C/C++ module.
exclude_runtime_libs
list of strings, list of runtime libs that should not be installed along with the vendor
variant of the C/C++ module.
version_script
string, version script for this vendor variant
suffix
string, set suffix of the name of the output
target_required
list of strings, names of other modules to install on target if this module is installed
test_config
string, the name of the test configuration (for example "AndroidTest.xml") that should be
installed with the module.
test_config_template
string, the name of the test configuration template (for example "AndroidTestTemplate.xml") that
should be installed with the module.
test_for
list of strings, List of APEXes that this module tests. The module has access to
the private part of the listed APEXes even when it is not included in the
APEXes.
test_mainline_modules
list of strings, Add parameterized mainline modules to auto generated test config. The options will be
handled by TradeFed to download and install the specified modules on the device.
test_min_api_level
int64, Add MinApiLevelModuleController to auto generated test config. If the device property of
"ro.product.first_api_level" < Test_min_api_level, then skip this module.
test_min_sdk_version
int64, Add MinApiLevelModuleController to auto generated test config. If the device property of
"ro.build.version.sdk" < Test_min_sdk_version, then skip this module.
test_options
TestOptions, Test options.
test_per_src
bool, Create a separate binary for each source file. Useful when there is
global state that can not be torn down and reset between each test suite.
test_suites
list of strings, list of compatibility suites (for example "cts", "vts") that the module should be
installed into.
tidy
bool, whether to run clang-tidy over C-like sources.
tidy_checks
list of strings, Extra checks to enable or disable in clang-tidy
tidy_checks_as_errors
list of strings, Checks that should be treated as errors.
tidy_flags
list of strings, Extra flags to pass to clang-tidy
unexported_symbols_list
string, local file name to pass to the linker as -unexported_symbols_list
unique_host_soname
bool, rename host libraries to prevent overlap with system installed libraries
use_apex_name_macro
bool, Adds __ANDROID_APEX_<APEX_MODULE_NAME>__ macro defined for apex variants in addition to __ANDROID_APEX__
use_clang_lld
bool, Use clang lld instead of gnu ld.
use_version_lib
bool, make android::build:GetBuildNumber() available containing the build ID.
vendor
bool, whether this module is specific to an SoC (System-On-a-Chip). When set to true,
it is installed into /vendor (or /system/vendor if vendor partition does not exist).
Use `soc_specific` instead for better meaning.
vendor_available
bool, whether this module should be allowed to be directly depended by other
modules with `vendor: true`, `proprietary: true`, or `vendor_available:true`.
In addition, this module should be allowed to be directly depended by
product modules with `product_specific: true`.
If set to true, three variants will be built separately, one like
normal, another limited to the set of libraries and headers
that are exposed to /vendor modules, and the other to /product modules.
The vendor and product variants may be used with a different (newer) /system,
so it shouldn't have any unversioned runtime dependencies, or
make assumptions about the system that may not be true in the
future.
If set to false, this module becomes inaccessible from /vendor or /product
modules.
Default value is true when vndk: {enabled: true} or vendor: true.
Nothing happens if BOARD_VNDK_VERSION isn't set in the BoardConfig.mk
If PRODUCT_PRODUCT_VNDK_VERSION isn't set, product variant will not be used.
version_script
string, local file name to pass to the linker as --version_script
vintf_fragments
list of strings, VINTF manifest fragments to be installed if this module is installed
visibility
list of strings, Controls the visibility of this module to other modules. Allowable values are one or more of
these formats:
["//visibility:public"]: Anyone can use this module.
["//visibility:private"]: Only rules in the module's package (not its subpackages) can use
this module.
["//visibility:override"]: Discards any rules inherited from defaults or a creating module.
Can only be used at the beginning of a list of visibility rules.
["//some/package:__pkg__", "//other/package:__pkg__"]: Only modules in some/package and
other/package (defined in some/package/*.bp and other/package/*.bp) have access to
this module. Note that sub-packages do not have access to the rule; for example,
//some/package/foo:bar or //other/package/testing:bla wouldn't have access. __pkg__
is a special module and must be used verbatim. It represents all of the modules in the
package.
["//project:__subpackages__", "//other:__subpackages__"]: Only modules in packages project
or other or in one of their sub-packages have access to this module. For example,
//project:rule, //project/library:lib or //other/testing/internal:munge are allowed
to depend on this rule (but not //independent:evil)
["//project"]: This is shorthand for ["//project:__pkg__"]
[":__subpackages__"]: This is shorthand for ["//project:__subpackages__"] where
//project is the module's package. e.g. using [":__subpackages__"] in
packages/apps/Settings/Android.bp is equivalent to
//packages/apps/Settings:__subpackages__.
["//visibility:legacy_public"]: The default visibility, behaves as //visibility:public
for now. It is an error if it is used in a module.
If a module does not specify the `visibility` property then it uses the
`default_visibility` property of the `package` module in the module's package.
If the `default_visibility` property is not set for the module's package then
it will use the `default_visibility` of its closest ancestor package for which
a `default_visibility` property is specified.
If no `default_visibility` property can be found then the module uses the
global default of `//visibility:legacy_public`.
The `visibility` property has no effect on a defaults module although it does
apply to any non-defaults module that uses it. To set the visibility of a
defaults module, use the `defaults_visibility` property on the defaults module;
not to be confused with the `default_visibility` property on the package module.
See https://android.googlesource.com/platform/build/soong/+/master/README.md#visibility for
more details.
⊕vndk
enabled
bool, declared as a VNDK or VNDK-SP module. The vendor variant
will be installed in /system instead of /vendor partition.
`vendor_available` must be explicitly set to either true or
false together with `vndk: {enabled: true}`.
support_system_process
bool, declared as a VNDK-SP module, which is a subset of VNDK.
`vndk: { enabled: true }` must set together.
All these modules are allowed to link to VNDK-SP or LL-NDK
modules only. Other dependency will cause link-type errors.
If `support_system_process` is not set or set to false,
the module is VNDK-core and can link to other VNDK-core,
VNDK-SP or LL-NDK modules only.
extends
string, Extending another module
whole_static_libs
list of strings, list of modules whose object files should be linked into this module
in their entirety. For static library modules, all of the .o files from the intermediate
directory of the dependency will be linked into this modules .a file. For a shared library,
the dependency's .a file will be linked into this module using -Wl,--whole-archive.
yacc
YaccProperties
llvm_defaults
name
,
srcs
,
host_supported
,
device_supported
,
aidl
,
allow_undefined_symbols
,
apex_available
,
arch
,
asflags
,
auto_gen_config
,
bootstrap
,
c_std
,
cflags
,
clang
,
clang_asflags
,
clang_cflags
,
compile_multilib
,
conlyflags
,
corpus
,
cpp_std
,
cppflags
,
data
,
debug
,
defaults
,
defaults_visibility
,
device_specific
,
dictionary
,
disable_framework
,
dist
,
double_loadable
,
enabled
,
exclude_shared_libs
,
exclude_srcs
,
exclude_static_libs
,
export_cflags
,
export_generated_headers
,
export_header_lib_headers
,
export_include_dirs
,
export_shared_lib_headers
,
export_static_lib_headers
,
export_system_include_dirs
,
force_symbols_not_weak_list
,
force_symbols_weak_list
,
fuzz_config
,
generated_headers
,
generated_sources
,
gnu_extensions
,
group_static_libs
,
gtest
,
header_abi_checker
,
header_libs
,
host_ldlibs
,
host_required
,
include_build_directory
,
include_dirs
,
init_rc
,
inject_bssl_hash
,
installable
,
instruction_set
,
isolated
,
ldflags
,
licenses
,
linker_script
,
local_include_dirs
,
logtags
,
lto
,
min_sdk_version
,
multilib
,
native_bridge_supported
,
native_coverage
,
no_libcrt
,
no_named_install_directory
,
nocrt
,
notice
,
objs
,
openmp
,
overrides
,
owner
,
pack_relocations
,
pgo
,
prefix_symbols
,
product_specific
,
proprietary
,
proto
,
ramdisk
,
ramdisk_available
,
recovery
,
recovery_available
,
relative_install_path
,
renderscript
,
require_root
,
required
,
rtti
,
runtime_libs
,
sanitize
,
sdk_variant_only
,
sdk_version
,
shared
,
shared_libs
,
soc_specific
,
sort_bss_symbols_by_size
,
static
,
static_executable
,
static_libs
,
static_ndk_lib
,
stem
,
stl
,
strip
,
stubs
,
suffix
,
symlink_preferred_arch
,
symlinks
,
system_ext_specific
,
system_shared_libs
,
target
,
target.host
,
target.platform
,
target.ramdisk
,
target.recovery
,
target.vendor
,
target_required
,
test_config
,
test_config_template
,
test_for
,
test_mainline_modules
,
test_min_api_level
,
test_min_sdk_version
,
test_options
,
test_per_src
,
test_suites
,
tidy
,
tidy_checks
,
tidy_checks_as_errors
,
tidy_flags
,
unexported_symbols_list
,
unique_host_soname
,
use_apex_name_macro
,
use_clang_lld
,
use_version_lib
,
vendor
,
vendor_available
,
version_script
,
vintf_fragments
,
visibility
,
vndk
,
whole_static_libs
,
yacc
name
string, The name of the module. Must be unique across all modules.
srcs
list of strings, list of source files used to compile the C/C++ module. May be .c, .cpp, or .S files.
srcs may reference the outputs of other modules that produce source files like genrule
or filegroup using the syntax ":module".
host_supported
bool, If set to true, build a variant of the module for the host. Defaults to false.
device_supported
bool, If set to true, build a variant of the module for the device. Defaults to true.
⊕aidl
include_dirs
list of strings, list of directories that will be added to the aidl include paths.
local_include_dirs
list of strings, list of directories relative to the Blueprints file that will
be added to the aidl include paths.
generate_traces
bool, whether to generate traces (for systrace) for this interface
allow_undefined_symbols
bool, allow the module to contain undefined symbols. By default,
modules cannot contain undefined symbols that are not satisified by their immediate
dependencies. Set this flag to true to remove --no-undefined from the linker flags.
This flag should only be necessary for compiling low-level libraries like libc.
apex_available
list of strings, Availability of this module in APEXes. Only the listed APEXes can contain
this module. If the module has stubs then other APEXes and the platform may
access it through them (subject to visibility).
"//apex_available:anyapex" is a pseudo APEX name that matches to any APEX.
"//apex_available:platform" refers to non-APEX partitions like "system.img".
Default is ["//apex_available:platform"].
arch
interface
asflags
list of strings, list of module-specific flags that will be used for .S compiles
auto_gen_config
bool, Flag to indicate whether or not to create test config automatically. If AndroidTest.xml
doesn't exist next to the Android.bp, this attribute doesn't need to be set to true
explicitly.
bootstrap
bool, Allows this module to use non-APEX version of libraries. Useful
for building binaries that are started before APEXes are activated.
c_std
string, C standard version to use. Can be a specific version (such as "gnu11"),
"experimental" (which will use draft versions like C1x when available),
or the empty string (which will use the default).
cflags
list of strings, list of module-specific flags that will be used for C and C++ compiles.
clang
bool, Deprecated. true is the default, false is invalid.
clang_asflags
list of strings, list of module-specific flags that will be used for .S compiles when
compiling with clang
clang_cflags
list of strings, list of module-specific flags that will be used for C and C++ compiles when
compiling with clang
compile_multilib
string, control whether this module compiles for 32-bit, 64-bit, or both. Possible values
are "32" (compile for 32-bit only), "64" (compile for 64-bit only), "both" (compile for both
architectures), or "first" (compile for 64-bit on a 64-bit platform, and 32-bit on a 32-bit
platform
conlyflags
list of strings, list of module-specific flags that will be used for C compiles
corpus
list of strings, Optional list of seed files to be installed to the fuzz target's output
directory.
cpp_std
string, C++ standard version to use. Can be a specific version (such as
"gnu++11"), "experimental" (which will use draft versions like C++1z when
available), or the empty string (which will use the default).
cppflags
list of strings, list of module-specific flags that will be used for C++ compiles
data
list of strings, list of files or filegroup modules that provide data that should be installed alongside
the test
⊕debug, release
cflags
list of strings, list of module-specific flags that will be used for C and C++ compiles in debug or
release builds
defaults
list of strings
defaults_visibility
list of strings, Controls the visibility of the defaults module itself.
device_specific
bool, whether this module is specific to a device, not only for SoC, but also for off-chip
peripherals. When set to true, it is installed into /odm (or /vendor/odm if odm partition
does not exist, or /system/vendor/odm if both odm and vendor partitions do not exist).
This implies `soc_specific:true`.
dictionary
string, Optional dictionary to be installed to the fuzz target's output directory.
disable_framework
bool, Add RunCommandTargetPreparer to stop framework before the test and start it after the test.
⊕dist
targets
list of strings, copy the output of this module to the $DIST_DIR when `dist` is specified on the
command line and any of these targets are also on the command line, or otherwise
built
dest
string, The name of the output artifact. This defaults to the basename of the output of
the module.
dir
string, The directory within the dist directory to store the artifact. Defaults to the
top level directory ("").
suffix
string, A suffix to add to the artifact file name (before any extension).
double_loadable
bool, whether this module is capable of being loaded with other instance
(possibly an older version) of the same module in the same process.
Currently, a shared library that is a member of VNDK (vndk: {enabled: true})
can be double loaded in a vendor process if the library is also a
(direct and indirect) dependency of an LLNDK library. Such libraries must be
explicitly marked as `double_loadable: true` by the owner, or the dependency
from the LLNDK lib should be cut if the lib is not designed to be double loaded.
enabled
bool, emit build rules for this module
Disabling a module should only be done for those modules that cannot be built
in the current environment. Modules that can build in the current environment
but are not usually required (e.g. superceded by a prebuilt) should not be
disabled as that will prevent them from being built by the checkbuild target
and so prevent early detection of changes that have broken those modules.
exclude_shared_libs
list of strings, list of shared libs that should not be used to build this module
exclude_srcs
list of strings, list of source files that should not be used to build the C/C++ module.
This is most useful in the arch/multilib variants to remove non-common files
exclude_static_libs
list of strings, list of static libs that should not be used to build this module
export_cflags
list of strings, list of plain cc flags to be used for any module that links against this module.
export_include_dirs
list of strings, list of directories relative to the Blueprints file that will
be added to the include path (using -I) for this module and any module that links
against this module. Directories listed in export_include_dirs do not need to be
listed in local_include_dirs.
export_system_include_dirs
list of strings, list of directories that will be added to the system include path
using -isystem for this module and any module that links against this module.
force_symbols_not_weak_list
string, local file name to pass to the linker as -force_symbols_not_weak_list
force_symbols_weak_list
string, local file name to pass to the linker as -force_symbols_weak_list
fuzz_config
FuzzConfig, Config for running the target on fuzzing infrastructure.
generated_sources
list of strings, list of generated sources to compile. These are the names of gensrcs or
genrule modules.
gnu_extensions
bool, if set to false, use -std=c++* instead of -std=gnu++*
group_static_libs
bool, group static libraries. This can resolve missing symbols issues with interdependencies
between static libraries, but it is generally better to order them correctly instead.
gtest
bool, if set, build against the gtest library. Defaults to true.
Properties for ABI compatibility checker
enabled
bool, Enable ABI checks (even if this is not an LLNDK/VNDK lib)
symbol_file
string, Path to a symbol file that specifies the symbols to be included in the generated
ABI dump file
exclude_symbol_versions
list of strings, Symbol versions that should be ignored from the symbol file
exclude_symbol_tags
list of strings, Symbol tags that should be ignored from the symbol file
host_ldlibs
list of strings, -l arguments to pass to linker for host-provided shared libraries
host_required
list of strings, names of other modules to install on host if this module is installed
include_build_directory
bool, Add the directory containing the Android.bp file to the list of include
directories. Defaults to true.
include_dirs
list of strings, list of directories relative to the root of the source tree that will
be added to the include path using -I.
If possible, don't use this. If adding paths from the current directory use
local_include_dirs, if adding paths from other modules use export_include_dirs in
that module.
init_rc
list of strings, init.rc files to be installed if this module is installed
inject_bssl_hash
bool, Inject boringssl hash into the shared library. This is only intended for use by external/boringssl.
installable
bool
instruction_set
string, the instruction set architecture to use to compile the C/C++
module.
isolated
bool, if set, use the isolated gtest runner. Defaults to false.
ldflags
list of strings, list of module-specific flags that will be used for all link steps
licenses
list of strings, Names of the licenses that apply to this module.
linker_script
string, if set, the path to a linker script to pass to ld -r when combining multiple object files.
local_include_dirs
list of strings, list of directories relative to the Blueprints file that will
be added to the include path using -I
logtags
list of strings, *.logtags files, to combine together in order to generate the /system/etc/event-log-tags
file
⊕lto
Lto must violate capitialization style for acronyms so that it can be
referred to in blueprint files as "lto"
never
bool
full
bool
thin
bool
min_sdk_version
string, Minimum sdk version that the artifact should support when it runs as part of mainline modules(APEX).
multilib
interface
native_bridge_supported
bool, Whether this module is built for non-native architecures (also known as native bridge binary)
native_coverage
bool
no_libcrt
bool, don't link in libclang_rt.builtins-*.a
no_named_install_directory
bool, Disables the creation of a test-specific directory when used with
relative_install_path. Useful if several tests need to be in the same
directory, but test_per_src doesn't work.
nocrt
bool, don't link in crt_begin and crt_end. This flag should only be necessary for
compiling crt or libc.
notice
string, relative path to a file to include in the list of notices for the device
objs
list of strings, names of other cc_object modules to link into this module using partial linking
openmp
bool, Build and link with OpenMP
overrides
list of strings, Names of modules to be overridden. Listed modules can only be other binaries
(in Make or Soong).
This does not completely prevent installation of the overridden binaries, but if both
binaries would be installed by default (in PRODUCT_PACKAGES) the other binary will be removed
from PRODUCT_PACKAGES.
owner
string, vendor who owns this module
pack_relocations
bool, Generate compact dynamic relocation table, default true.
⊕pgo
instrumentation
bool
sampling
bool
profile_file
string
benchmarks
list of strings
enable_profile_use
bool
cflags
list of strings, Additional compiler flags to use when building this module
for profiling (either instrumentation or sampling).
prefix_symbols
string, if set, add an extra objcopy --prefix-symbols= step
product_specific
bool, whether this module is specific to a software configuration of a product (e.g. country,
network operator, etc). When set to true, it is installed into /product (or
/system/product if product partition does not exist).
proprietary
bool, whether this is a proprietary vendor module, and should be installed into /vendor
⊕proto
type
string, Proto generator type. C++: full or lite. Java: micro, nano, stream, or lite.
plugin
string, Proto plugin to use as the generator. Must be a cc_binary_host module.
include_dirs
list of strings, list of directories that will be added to the protoc include paths.
local_include_dirs
list of strings, list of directories relative to the bp file that will
be added to the protoc include paths.
canonical_path_from_root
bool, whether to identify the proto files from the root of the
source tree (the original method in Android, useful for
android-specific protos), or relative from where they were
specified (useful for external/third party protos).
This defaults to true today, but is expected to default to
false in the future.
static
bool, Link statically against the protobuf runtime
ramdisk
bool, Whether this module is installed to ramdisk
ramdisk_available
bool, Make this module available when building for ramdisk
recovery
bool, Whether this module is installed to recovery partition
recovery_available
bool, Make this module available when building for recovery
relative_install_path
string, install to a subdirectory of the default install path for the module
⊕renderscript
include_dirs
list of strings, list of directories that will be added to the llvm-rs-cc include paths
flags
list of strings, list of flags that will be passed to llvm-rs-cc
target_api
string, Renderscript API level to target
require_root
bool, Add RootTargetPreparer to auto generated test config. This guarantees the test to run
with root permission.
required
list of strings, names of other modules to install if this module is installed
rtti
bool, pass -frtti instead of -fno-rtti
runtime_libs
list of strings, list of modules that should be installed with this module. This is similar to 'required'
but '.vendor' suffix will be appended to the module names if the shared libraries have
vendor variants and this module uses VNDK.
⊕sanitize
enable AddressSanitizer, ThreadSanitizer, or UndefinedBehaviorSanitizer
never
bool
address
bool, main sanitizers
thread
bool
hwaddress
bool
undefined
bool, local sanitizers
all_undefined
bool
misc_undefined
list of strings
fuzzer
bool
safestack
bool
cfi
bool
integer_overflow
bool
scudo
bool
scs
bool
⊕diag
Sanitizers to run in the diagnostic mode (as opposed to the release mode).
Replaces abort() on error with a human-readable error message.
Address and Thread sanitizers always run in diagnostic mode.
undefined
bool
cfi
bool
integer_overflow
bool
misc_undefined
list of strings
no_recover
list of strings
recover
list of strings, value to pass to -fsanitize-recover=
blacklist
string, value to pass to -fsanitize-blacklist
sdk_variant_only
bool, If true, always create an sdk variant and don't create a platform variant.
sdk_version
string, Minimum sdk version supported when compiling against the ndk. Setting this property causes
two variants to be built, one for the platform and one for apps.
shared
StaticOrSharedProperties
shared_libs
list of strings, list of modules that should be dynamically linked into this module.
soc_specific
bool, whether this module is specific to an SoC (System-On-a-Chip). When set to true,
it is installed into /vendor (or /system/vendor if vendor partition does not exist).
sort_bss_symbols_by_size
bool, Order symbols in .bss section by their sizes. Only useful for shared libraries.
static
StaticOrSharedProperties
static_executable
bool, compile executable with -static
static_libs
list of strings, list of modules that should be statically linked into this module.
static_ndk_lib
bool
stem
string, set the name of the output
stl
string, Select the STL library to use. Possible values are "libc++",
"libc++_static", "libstdc++", or "none". Leave blank to select the
default.
⊕strip
none
bool
all
bool
keep_symbols
bool
keep_symbols_list
list of strings
keep_symbols_and_debug_frame
bool
⊕stubs
symbol_file
string, Relative path to the symbol map. The symbol map provides the list of
symbols that are exported for stubs variant of this library.
versions
list of strings, List versions to generate stubs libs for.
suffix
string, set suffix of the name of the output
symlink_preferred_arch
bool, if set, install a symlink to the preferred architecture
symlinks
list of strings, install symlinks to the binary. Symlink names will have the suffix and the binary
extension (if any) appended
system_ext_specific
bool, whether this module extends system. When set to true, it is installed into /system_ext
(or /system/system_ext if system_ext partition does not exist).
system_shared_libs
list of strings, list of system libraries that will be dynamically linked to
shared library and executable modules. If unset, generally defaults to libc,
libm, and libdl. Set to [] to prevent linking against the defaults.
target
interface
⊕target.host, target.android
⊕target.platform
shared_libs
list of strings, list of shared libs that should be use to build the platform variant
of a module that sets sdk_version. This should rarely be necessary,
in most cases the same libraries are available for the SDK and platform
variants.
⊕target.ramdisk
static_libs
list of strings, list of static libs that only should be used to build the recovery
variant of the C/C++ module.
exclude_shared_libs
list of strings, list of shared libs that should not be used to build
the ramdisk variant of the C/C++ module.
exclude_static_libs
list of strings, list of static libs that should not be used to build
the ramdisk variant of the C/C++ module.
⊕target.recovery
srcs
list of strings, list of source files that should only be used in the
recovery variant of the C/C++ module.
exclude_srcs
list of strings, list of source files that should not be used to
build the recovery variant of the C/C++ module.
cflags
list of strings, List of additional cflags that should be used to build the recovery
variant of the C/C++ module.
shared_libs
list of strings, list of shared libs that only should be used to build the recovery
variant of the C/C++ module.
static_libs
list of strings, list of static libs that only should be used to build the recovery
variant of the C/C++ module.
exclude_shared_libs
list of strings, list of shared libs that should not be used to build
the recovery variant of the C/C++ module.
exclude_static_libs
list of strings, list of static libs that should not be used to build
the recovery variant of the C/C++ module.
⊕target.vendor
srcs
list of strings, list of source files that should only be used in the
vendor variant of the C/C++ module.
exclude_srcs
list of strings, list of source files that should not be used to
build the vendor variant of the C/C++ module.
cflags
list of strings, List of additional cflags that should be used to build the vendor
variant of the C/C++ module.
override_export_include_dirs
list of strings, list of exported include directories, like
export_include_dirs, that will be applied to the
vendor variant of this library. This will overwrite
any other declarations.
shared_libs
list of strings, list of shared libs that only should be used to build the vendor
variant of the C/C++ module.
static_libs
list of strings, list of static libs that only should be used to build the vendor
variant of the C/C++ module.
exclude_shared_libs
list of strings, list of shared libs that should not be used to build the vendor variant
of the C/C++ module.
exclude_static_libs
list of strings, list of static libs that should not be used to build the vendor variant
of the C/C++ module.
exclude_runtime_libs
list of strings, list of runtime libs that should not be installed along with the vendor
variant of the C/C++ module.
version_script
string, version script for this vendor variant
suffix
string, set suffix of the name of the output
target_required
list of strings, names of other modules to install on target if this module is installed
test_config
string, the name of the test configuration (for example "AndroidTest.xml") that should be
installed with the module.
test_config_template
string, the name of the test configuration template (for example "AndroidTestTemplate.xml") that
should be installed with the module.
test_for
list of strings, List of APEXes that this module tests. The module has access to
the private part of the listed APEXes even when it is not included in the
APEXes.
test_mainline_modules
list of strings, Add parameterized mainline modules to auto generated test config. The options will be
handled by TradeFed to download and install the specified modules on the device.
test_min_api_level
int64, Add MinApiLevelModuleController to auto generated test config. If the device property of
"ro.product.first_api_level" < Test_min_api_level, then skip this module.
test_min_sdk_version
int64, Add MinApiLevelModuleController to auto generated test config. If the device property of
"ro.build.version.sdk" < Test_min_sdk_version, then skip this module.
test_options
TestOptions, Test options.
test_per_src
bool, Create a separate binary for each source file. Useful when there is
global state that can not be torn down and reset between each test suite.
test_suites
list of strings, list of compatibility suites (for example "cts", "vts") that the module should be
installed into.
tidy
bool, whether to run clang-tidy over C-like sources.
tidy_checks
list of strings, Extra checks to enable or disable in clang-tidy
tidy_checks_as_errors
list of strings, Checks that should be treated as errors.
tidy_flags
list of strings, Extra flags to pass to clang-tidy
unexported_symbols_list
string, local file name to pass to the linker as -unexported_symbols_list
unique_host_soname
bool, rename host libraries to prevent overlap with system installed libraries
use_apex_name_macro
bool, Adds __ANDROID_APEX_<APEX_MODULE_NAME>__ macro defined for apex variants in addition to __ANDROID_APEX__
use_clang_lld
bool, Use clang lld instead of gnu ld.
use_version_lib
bool, make android::build:GetBuildNumber() available containing the build ID.
vendor
bool, whether this module is specific to an SoC (System-On-a-Chip). When set to true,
it is installed into /vendor (or /system/vendor if vendor partition does not exist).
Use `soc_specific` instead for better meaning.
vendor_available
bool, whether this module should be allowed to be directly depended by other
modules with `vendor: true`, `proprietary: true`, or `vendor_available:true`.
In addition, this module should be allowed to be directly depended by
product modules with `product_specific: true`.
If set to true, three variants will be built separately, one like
normal, another limited to the set of libraries and headers
that are exposed to /vendor modules, and the other to /product modules.
The vendor and product variants may be used with a different (newer) /system,
so it shouldn't have any unversioned runtime dependencies, or
make assumptions about the system that may not be true in the
future.
If set to false, this module becomes inaccessible from /vendor or /product
modules.
Default value is true when vndk: {enabled: true} or vendor: true.
Nothing happens if BOARD_VNDK_VERSION isn't set in the BoardConfig.mk
If PRODUCT_PRODUCT_VNDK_VERSION isn't set, product variant will not be used.
version_script
string, local file name to pass to the linker as --version_script
vintf_fragments
list of strings, VINTF manifest fragments to be installed if this module is installed
visibility
list of strings, Controls the visibility of this module to other modules. Allowable values are one or more of
these formats:
["//visibility:public"]: Anyone can use this module.
["//visibility:private"]: Only rules in the module's package (not its subpackages) can use
this module.
["//visibility:override"]: Discards any rules inherited from defaults or a creating module.
Can only be used at the beginning of a list of visibility rules.
["//some/package:__pkg__", "//other/package:__pkg__"]: Only modules in some/package and
other/package (defined in some/package/*.bp and other/package/*.bp) have access to
this module. Note that sub-packages do not have access to the rule; for example,
//some/package/foo:bar or //other/package/testing:bla wouldn't have access. __pkg__
is a special module and must be used verbatim. It represents all of the modules in the
package.
["//project:__subpackages__", "//other:__subpackages__"]: Only modules in packages project
or other or in one of their sub-packages have access to this module. For example,
//project:rule, //project/library:lib or //other/testing/internal:munge are allowed
to depend on this rule (but not //independent:evil)
["//project"]: This is shorthand for ["//project:__pkg__"]
[":__subpackages__"]: This is shorthand for ["//project:__subpackages__"] where
//project is the module's package. e.g. using [":__subpackages__"] in
packages/apps/Settings/Android.bp is equivalent to
//packages/apps/Settings:__subpackages__.
["//visibility:legacy_public"]: The default visibility, behaves as //visibility:public
for now. It is an error if it is used in a module.
If a module does not specify the `visibility` property then it uses the
`default_visibility` property of the `package` module in the module's package.
If the `default_visibility` property is not set for the module's package then
it will use the `default_visibility` of its closest ancestor package for which
a `default_visibility` property is specified.
If no `default_visibility` property can be found then the module uses the
global default of `//visibility:legacy_public`.
The `visibility` property has no effect on a defaults module although it does
apply to any non-defaults module that uses it. To set the visibility of a
defaults module, use the `defaults_visibility` property on the defaults module;
not to be confused with the `default_visibility` property on the package module.
See https://android.googlesource.com/platform/build/soong/+/master/README.md#visibility for
more details.
⊕vndk
enabled
bool, declared as a VNDK or VNDK-SP module. The vendor variant
will be installed in /system instead of /vendor partition.
`vendor_available` must be explicitly set to either true or
false together with `vndk: {enabled: true}`.
support_system_process
bool, declared as a VNDK-SP module, which is a subset of VNDK.
`vndk: { enabled: true }` must set together.
All these modules are allowed to link to VNDK-SP or LL-NDK
modules only. Other dependency will cause link-type errors.
If `support_system_process` is not set or set to false,
the module is VNDK-core and can link to other VNDK-core,
VNDK-SP or LL-NDK modules only.
extends
string, Extending another module
whole_static_libs
list of strings, list of modules whose object files should be linked into this module
in their entirety. For static library modules, all of the .o files from the intermediate
directory of the dependency will be linked into this modules .a file. For a shared library,
the dependency's .a file will be linked into this module using -Wl,--whole-archive.
yacc
YaccProperties
llvm_tblgen
name
,
compile_multilib
,
device_specific
,
dist
,
enabled
,
host_required
,
in
,
init_rc
,
licenses
,
native_bridge_supported
,
notice
,
outs
,
owner
,
product_specific
,
proprietary
,
ramdisk
,
recovery
,
required
,
soc_specific
,
system_ext_specific
,
target.host
,
target_required
,
vendor
,
vintf_fragments
,
visibility
name
string, The name of the module. Must be unique across all modules.
compile_multilib
string, control whether this module compiles for 32-bit, 64-bit, or both. Possible values
are "32" (compile for 32-bit only), "64" (compile for 64-bit only), "both" (compile for both
architectures), or "first" (compile for 64-bit on a 64-bit platform, and 32-bit on a 32-bit
platform
device_specific
bool, whether this module is specific to a device, not only for SoC, but also for off-chip
peripherals. When set to true, it is installed into /odm (or /vendor/odm if odm partition
does not exist, or /system/vendor/odm if both odm and vendor partitions do not exist).
This implies `soc_specific:true`.
⊕dist
targets
list of strings, copy the output of this module to the $DIST_DIR when `dist` is specified on the
command line and any of these targets are also on the command line, or otherwise
built
dest
string, The name of the output artifact. This defaults to the basename of the output of
the module.
dir
string, The directory within the dist directory to store the artifact. Defaults to the
top level directory ("").
suffix
string, A suffix to add to the artifact file name (before any extension).
enabled
bool, emit build rules for this module
Disabling a module should only be done for those modules that cannot be built
in the current environment. Modules that can build in the current environment
but are not usually required (e.g. superceded by a prebuilt) should not be
disabled as that will prevent them from being built by the checkbuild target
and so prevent early detection of changes that have broken those modules.
host_required
list of strings, names of other modules to install on host if this module is installed
in
string
init_rc
list of strings, init.rc files to be installed if this module is installed
licenses
list of strings, Names of the licenses that apply to this module.
native_bridge_supported
bool, Whether this module is built for non-native architecures (also known as native bridge binary)
notice
string, relative path to a file to include in the list of notices for the device
outs
list of strings
owner
string, vendor who owns this module
product_specific
bool, whether this module is specific to a software configuration of a product (e.g. country,
network operator, etc). When set to true, it is installed into /product (or
/system/product if product partition does not exist).
proprietary
bool, whether this is a proprietary vendor module, and should be installed into /vendor
ramdisk
bool, Whether this module is installed to ramdisk
recovery
bool, Whether this module is installed to recovery partition
required
list of strings, names of other modules to install if this module is installed
soc_specific
bool, whether this module is specific to an SoC (System-On-a-Chip). When set to true,
it is installed into /vendor (or /system/vendor if vendor partition does not exist).
system_ext_specific
bool, whether this module extends system. When set to true, it is installed into /system_ext
(or /system/system_ext if system_ext partition does not exist).
⊕target.host, target.android
target_required
list of strings, names of other modules to install on target if this module is installed
vendor
bool, whether this module is specific to an SoC (System-On-a-Chip). When set to true,
it is installed into /vendor (or /system/vendor if vendor partition does not exist).
Use `soc_specific` instead for better meaning.
vintf_fragments
list of strings, VINTF manifest fragments to be installed if this module is installed
visibility
list of strings, Controls the visibility of this module to other modules. Allowable values are one or more of
these formats:
["//visibility:public"]: Anyone can use this module.
["//visibility:private"]: Only rules in the module's package (not its subpackages) can use
this module.
["//visibility:override"]: Discards any rules inherited from defaults or a creating module.
Can only be used at the beginning of a list of visibility rules.
["//some/package:__pkg__", "//other/package:__pkg__"]: Only modules in some/package and
other/package (defined in some/package/*.bp and other/package/*.bp) have access to
this module. Note that sub-packages do not have access to the rule; for example,
//some/package/foo:bar or //other/package/testing:bla wouldn't have access. __pkg__
is a special module and must be used verbatim. It represents all of the modules in the
package.
["//project:__subpackages__", "//other:__subpackages__"]: Only modules in packages project
or other or in one of their sub-packages have access to this module. For example,
//project:rule, //project/library:lib or //other/testing/internal:munge are allowed
to depend on this rule (but not //independent:evil)
["//project"]: This is shorthand for ["//project:__pkg__"]
[":__subpackages__"]: This is shorthand for ["//project:__subpackages__"] where
//project is the module's package. e.g. using [":__subpackages__"] in
packages/apps/Settings/Android.bp is equivalent to
//packages/apps/Settings:__subpackages__.
["//visibility:legacy_public"]: The default visibility, behaves as //visibility:public
for now. It is an error if it is used in a module.
If a module does not specify the `visibility` property then it uses the
`default_visibility` property of the `package` module in the module's package.
If the `default_visibility` property is not set for the module's package then
it will use the `default_visibility` of its closest ancestor package for which
a `default_visibility` property is specified.
If no `default_visibility` property can be found then the module uses the
global default of `//visibility:legacy_public`.
The `visibility` property has no effect on a defaults module although it does
apply to any non-defaults module that uses it. To set the visibility of a
defaults module, use the `defaults_visibility` property on the defaults module;
not to be confused with the `default_visibility` property on the package module.
See https://android.googlesource.com/platform/build/soong/+/master/README.md#visibility for
more details.


Comments
-
Greg Hurrell
(In reply to comment #0)
If this is the standard new user experience I would expect a lot of them to no keep the app.
It's not the standard new user experience. You're running 3.5a2 and the "a" stands for "alpha":
http://en.wikipedia.org/wiki/Development_stage#Alpha
If you want a non-alpha release, the latest stable release is version 3.2 which you can get from here:
https://wincent.com/a/products/synergy-classic/download/tiger/
If you'd like to see the quitting problems fixed, can you please provide the crash reports? You should be able to find them in your ~/Library/Logs/CrashReporter/ folder.
Add a comment
Comments are now closed for this issue.


Access to the life history database is granted to limited individuals to date. Please keep your login information private and do not share
the database or URL with anyone until you are granted permission.
{% if user.is_superuser %}
If you are seeing this message, you are a Superuser... only Superusers have the ability to create new users or add species to the database.


{% extends "base.html" %} {% block body_class %}template-homepage{% endblock %} {% block content %} {%load static%}
This degree is intended to prepare students to transfer to Washington’s public four-year colleges and universities and many private colleges with junior standing and the majority of the prerequisites for selected science majors completed. This degree partially fulfills the general education requirements as explained in the AA-DTA degree. You will need to take additional credits from Social Science and the Humanities Distribution Areas at SVC or the four-year transfer institution to satisfy bachelor’s degree requirements.
The Computer Information Systems program is designed to expose students to a broad spectrum of disciplines within the field of information technology: operating systems, hardware support, network administration, application software, database design and programming. With successful completion of the program, students will have discovered the area which best fits their interest and aptitude, and be prepared to pursue entry-level positions or further education.
Program coursework includes web design, digital photography, image manipulation, illustration, user interface design, digital marketing, digital videography as well as programming and scripting basics. SVC's Multimedia & Interactive Technology program will prepare students for work in media-rich fields of web design, graphic arts, or video game development. This program can be completed entirely online.


Directly extract and plot stochastic common trends from a cointegration system using different approaches, currently including Kasa (1992) and Gonzalo and Granger (1995). The approach proposed by Gonzalo and Granger, also known as Permanent-Transitory Decomposition, is widely used in macroeconomics and market microstructure literature. Kasa's approach, on the other hand, has a nice property that it only uses the super consistent estimator: the cointegration vector 'beta'. This package also provides functions calculate P-value from Johansen Statistics according to the approximation method proposed by Doornik (1998). Update: 0.7-1: Fix bugs in calculation alpha. Add formulas and more explanations. 0.6-1: Rewrite the description file. 0.5-1: Add functions to calculate P-value from Johansen statistic, and vice versa.
| Version: | 0.7-1 |
| Depends: | R (≥ 2.10) |
| Imports: | methods, MASS, urca |
| Published: | 2013-09-05 |
| Author: | Fan Yang |
| Maintainer: | Fan Yang <yfno1 at msn.com> |
| License: | GPL-2 | GPL-3 [expanded from: GPL (≥ 2)] |
| NeedsCompilation: | no |
| In views: | TimeSeries |
| CRAN checks: | CommonTrend results |
| Reference manual: | CommonTrend.pdf |
| Package source: | CommonTrend_0.7-1.tar.gz |
| Windows binaries: | r-devel: CommonTrend_0.7-1.zip, r-release: CommonTrend_0.7-1.zip, r-oldrel: CommonTrend_0.7-1.zip |
| OS X binaries: | r-release: CommonTrend_0.7-1.tgz, r-oldrel: CommonTrend_0.7-1.tgz |
| Old sources: | CommonTrend archive |
Please use the canonical form https://CRAN.R-project.org/package=CommonTrend to link to this page.


{{ categoryName}}
Computer games developer
Computer games designer, video games designer
Computer games developers make games for the internet, mobile phones, PCs and games consoles.
Computer games tester
Games tester, quality assurance tester, video games tester, quality assurance technician
Computer games testers play computer games to check they work properly. They find and record problems or bugs.
IT support technician
IT user support technician, IT helpdesk technician, service desk technician, help desk support analyst
IT technical support staff diagnose and solve software and hardware problems for computer users.
Software developer
Programmer
Software developers design, build and test computer programmes for business, education and leisure activities.


What is the Natick Highschool Computer Science Club?
The Natick Highschool Computer Science Club is a club that was created in 2021 in Natick, MA. It is associated with the Natick High School, and is run mainly by us, its members. We started it to get more people in the community involved with computer science as well as have a positive impact on others around us.


--- layout: post title: Software dev links date: 2006-10-07 00:00:00 category: software-development ---
A few links that have piled up:


Metasploit route command can be used to establish a route to other networks that can be
used to launch Metasploit exploits
usage: route [add|remove] <network_to_attack> <subnet> <session_to_pivot_through>
msf exploit(handler) > route add <IP_ADDRESS> <IP_ADDRESS> 1
[*] Route added
msf auxiliary(tcp) > route print
Active Routing Table
====================
Subnet Netmask Gateway
------ ------- -------
<IP_ADDRESS> <IP_ADDRESS> Session 1
There are limitations to using Meterpreter session. Only modules within
Metasploit can directly use the session. Furthermore, the sessions only transmit TCP
packets.
Note: Only use MSF route here. If you're in Meterpreter session, using 'route' will mess up the hosts routing table!
Note: The routing we provide with the run autoroute command gives us the freedom to work in the Metasploit Framework. But when we try to reach the target with a Kali tools, we need tools like port forwarding or proxychains.


{% load static %}
NetScale
LOGIN
SIGN UP
×
Log onto NetScale
{% csrf_token %}
×
netscale
We are at our best together.
Another sentence here.
FIND OUT NOW
LEARN MORE


| Permission Node | Info | |
|---|---|---|
| block.tap | ALL |
Node for taping blocks with the tree tap |
| block.wrench | ALL |
Node for wrenching blocks |
| command.* | OP |
Permission for commands, if FTBUtilities command overriding is enabled.


Press Scan to start channel scan!
Press Stop to stop channel scan!
These are raw values, they are higher than the RSSI values displayed everywhere else!
Got maximum RSSI ({{maxRssi}}) on {{maxChannel}} ({{maxFreq}} MHz).
{{channel.channel}} ({{channel.freq}} MHz): {{channel.rssi}}


Custom built wordpress membership directory plug-in replacement for the default user system. Member accounts, profile management, public member directory, multiple user level restrictions, customized profile w/ajax image image--lazyload upload, uses wpdb & wp_list_table for default wordpress feel, searchable/filterable member listings, and payment/fees tracking.
mscra.com


{% import 'headers.html' as headers %} {% import 'footers.html' as footers %} {% import 'algo.html' as algo %}
This article is focused on showing efficient techniques regarding prime counting or, in general, counting numbers coprime to some set of numbers. Here, \(P\) will refer either to the set of all primes or the sequence of subsequent primes (\(k\)-th element of this sequence will be denoted as \(P_k\)). Definitions used in this article:
Notice, that \(\pi(x) = \pi(\lfloor x \rfloor)\), \(\phi(n,a) = \phi(\lfloor n \rfloor, a)\), and \(P_k(n,a) = P_k(\lfloor n \rfloor,a)\).
A sequence \(S\) of \(m\) pairwisely coprime numbers (\(m \le 100, S_i \le 10^5\)) is given. How many there are numbers less or equal to \(n\) (\(n \le 10^{13})\) not divisible by any element of \(S\)?
Let \(C_S(n)\) denote answer to given question. First, answer is equal to amount of numbers in a range except numbers divisible by at least one number from sequence. From inclusion-exclusion principle, $$C_S(n) = n - \sum_{i=1}^{m} \lfloor \frac{n}{S_i} \rfloor + \sum_{i=1}^{m} \sum_{j=i+1}^{m} \lfloor \frac{n}{S_i S_j} \rfloor - \dots + (-1)^m \lfloor \frac{n}{S_1 S_2 \dots S_m} \rfloor$$ Note that as all numbers are coprime, it is not necessary to calculate any \(lcm\) (otherwise there would be \(lcm(S_{i_1}, S_{i_2}, \dots S_{i_l})\) instead of \(S_{i_1} S_{i_2} \dots S_{i_l}\)
How to estimate number of operations occuring using this technique? Let \(f(S,n)\) denote set of all multiples of elements of \(S\) lower or equal to \(n\). There are two banal ways:
Let \(\phi_S(n, a)\) denote an amount of numbers in range \(\lt 1;n \gt\) coprime to all numbers in sequence \(S\) up to an index \(a\): $$ \phi_S(n, a)=|\{x: x \le n \land \forall_{i \le a} S_i \nmid x\}| $$ Note, that \(\phi(n, a)=\phi_P(n,a)\). How to calculate values of that function?
All numbers not divisible by any element of \(S_1, \dots, S_a\) are all numbers not divisible by any element of \(S_1, \dots, S_{a-1}\) except those divisible by \(S_a\). As \(S_a\) is coprime to all previous elements, each element in range \(\lt 1; \lfloor \frac{n}{S_a} \rfloor \gt \) not divisible by \(S_1, \dots, S_{a-1}\) multiplied by \(S_a\) will yield a number:
Conversely, if some number satisfies three points above, it can be obtained as product described above. Thus: $$\phi_S(n, a)=\phi_S(n, a-1)-\phi_S(\lfloor \frac{n}{S_a} \rfloor, a-1)$$ $$\phi_S(n, 0)=n$$
Also, notice, that \(\lfloor \frac{\lfloor \frac{n}{ a } \rfloor}{b} \rfloor = \lfloor \frac{n}{ab} \rfloor\) where \(n,a,b \in N\) - to show it, let \(n=kab+la+m\), where \(la+m \lt ab\), also \(k,l,m \in N \cup \{0\}\) and \(m \lt a\) $$ \lfloor \frac{\lfloor \frac{n}{ a } \rfloor}{b} \rfloor = \lfloor \frac{\lfloor \frac{ kab+la+m }{ a } \rfloor}{b} \rfloor = \lfloor \frac{kb+l}{b} \rfloor = $$ $$ = k = \lfloor \frac{kab}{ab} \rfloor = \lfloor \frac{kab+al+m}{ab} \rfloor = \lfloor \frac{n}{ab} \rfloor$$
And the sought value is \(\phi_S(n, |S|)\). While this formula is immediate consequence of Legendre's formula, it gives the possibility to reformulate the solution in moderately elegant way:
Input: two values \(n,a\), for which \(\phi(n,a)\) will be calculated; note, that it will be calculated for sequence of prime numbers.
' , '121 7', {'color_description':{'standard':'', 'change':'', 'crucial':'Value \(\phi(n,a)\) to calculate', 'iterator':'Iterator for \(\phi( \\frac{n}{P_a}, a-1)\)', 'exponent':'Iterator for \(\phi( n, a-1)\)', '_red':'Value \(\phi( \\frac{n}{P_a}, a-1)\) to subtract', '_green':'Value \(\phi(n, a-1)\) to add', 'helper2':''} }) }}A number \(n \le 10^{11}\) is given; how many there are primes in a range \(\lt 1;n \gt\)?
This problem can be solved by finding all primes in a range with a regular Erastothenes sieve: complexity is obviously unsatisfactory \(O(n\log \log n)\).
Legendre's formula states, that:
{% set sqrt=" \lfloor \sqrt{n} \\rfloor " %} $$ \pi(n) = -1 + \pi( {{sqrt}} ) + n - \sum_{p_i \le {{sqrt}} } \lfloor \frac{n}{p_i} \rfloor + \sum_{p_i \le p_j \le {{sqrt}} } \lfloor \frac{n}{p_i p_j} \rfloor + \dots + (-1)^{ k } \lfloor \frac{n}{p_1 p_2 \dots p_k} \rfloor$$Where:
It suffers from same problems as an analogous method shown in problem I - its number of operations is too great.
First, the problem will be divided into two distinct problems:
{% set partial_sq=" n^{1/L} " %}First problem can be defined in terms of a partial sieve function: $$\phi(n, \pi( {{partial_sq}} ))$$ gives the sought result.
Let \(P_k(n, a)\) be defined as amount of number lower equal to \(n\) with exactly \(k\) prime divisors (not necessarily distinct), none of them less or equal to \(P_a\). Then: $$\phi(n, h) = P_0(n, h) + P_1(n, h) + P_2(n, h) + \dots $$ $$\pi(n) = P_1(n,h) + h $$ $$\pi(n) = h + \phi(n, h) - P_0(n,h) - P_2(n,h) - \dots $$
How to calculate \(P_k(n, a)\) though? The banal solution, for \(k \ge 2\): $$P_k(n, a)=\sum_{i_1=a+1}^{\pi(n^{1/2})} \sum_{i_2=i_1}^{\pi(n^{1/2})} \dots \sum_{i_{k-1}=i_{k-2}}^{\pi(n^{1/2})} \max(\pi(\frac{n}{P_{i_1} P_{i_2} \dots P_{i_{k-1}}}) - i_{k-1} + 1, 0) $$ It counts, for each possible result of multiplying \(k-1\) primes, where \(P_{i_v} \le P_{i_{v+1}}\), in how many ways last prime (that may be greater than \(n^{1/2}\), and has to be greater or equal to \(P_{i_{k-1}}\)) can be chosen?
One can move a bit further - arguing, that, if \((P_{i_1} \le P_{i_2} \le \dots \le P_{i_k})\), then, better bounds on each \(i_x\) may be placed:
The above allows to represent the formula for \(P_k(n,a)\) in a different way: $$P_k(n, a) = \sum_{i_1=a+1}^{\pi(n^{1/k})} \sum_{i_2=i_1}^{\pi(n^{\frac{1-1/L}{k-1} }) } \dots \sum_{i_{k-1}=i_{k-2}}^{\pi(n^{1-(k-1)/L}) } \max(\pi(\frac{n}{P_{i_1} P_{i_2} \dots P_{i_{k-1}}}) - i_{k-1} + 1, 0) $$ In general, presenting formula in this form does not seem to be an extraordinarily bright idea - it will be discussed as a special case of applying the above.
Another problem: many values of \(\pi(x)\) have to be calculated to use this formula; to solve this problem, one can use standard erastothenes sieve. The greatest amount of primes has to be sieved when finding \(P_2(n, a)\) - namely, \(\pi(\frac{n}{P_{a+1}})\) - thus, for certain \(L\), \(\pi(n^{1-1/L})\) has to be calculated in something like \(O(n^{1-1/L} \log\log(n))\).
Say, \(L=4\) - then:
To summarize, if \(a=\pi(n^{1/4})\), the sought result can be expressed as $$ \pi(n) = a + \phi(n, a) - 1 - P_2(n, a) - P_3(n, a) $$ as all values \(P_4(n, a), P_5(n, a), \dots\) are equal to 0.
So, the complexity of this algorithm is \(O(n^{3/4} \log \log n)\).
Say, You're given \(q\) queries in form \(\phi(n,a)\), where \(n,q \le 3*10^7\), and You have to answer them offline. How cope?
Instead of constructing recursive solutions, one can:
Overall complexity is \(O(n\log(n) + n\log\log(n) + q\log(n)) = O(n\log(n) + q\log(n))\) - \(O(n \log(n))\) for at most \(n\) changes - marking number as composite, \(O(n \log\log(n))\) for a sieve, and \(O(q \log(n))\) for query answering.
There is one particular consequence of this method: If one wants to calculate \(\phi(n, a)\), one can use recursion-like structures to calculate \(\phi(x,\_)\) for \(x \ge n^{2/3}\), and use sieve with superimposed segment tree otherwise; If \(a=n^{1/3}\), Then number of queries passed to sieve along with number of nodes in recursion-like structure will be lower or equal to \(n^{2/3}\) (\(n^{1/3}\) values \(z\) in recursion in form \(\phi(z, \_)\) for \(z \ge n^{2/3}\) spawning at most \(a=n^{1/3}\) queries/nodes each), and so, complexity for calculating \(\phi(n, n^{1/3})\) will be equal to \(O(n^{2/3} \log(n))\).
{{ algo.neo_algorithm(2, 'Calculating set of values of \(\phi(n, a)\)', 'Input: first, \(q\) - amount of queries, then \(q\) queries in form \(n, a\) - the algorithm\'s aim will be to calculate \(\phi(n, a)\) for each pair
' , '5 7 2 15 3 11 0 14 4 12 3', {'input_type':'textarea', 'color_description':{'standard':'', 'change':'', 'crucial':'Value \(\phi(n,a)\) to calculate', 'iterator':'Iterator for prime search in a sieve', 'exponent':'Iterator for removing divisible numbers in a sieve', '_red':'Number of already sieved primes', 'helper1':'Comparing query prime nr and current prime nr', 'helper2':'Index and element used in query'} }) }}Notice, that one can use a persistent segment tree to preserve information about updates; this doesn't change anything except possibility to execute queries online and necessity to have \(O(n^{2/3} \log(n))\) memory - which can be cumbersome, given usual constraints in this type of problems.
For \(h=\pi(n^{1/3})\):
$$\pi(n) = h + \phi(n, h) - P_0(n,h) - P_2(n,h)$$ $$\pi(n) = \pi(n^{1/3}) + \phi(n, \pi(n^{1/3})) - 1 - P_2(n,\pi(n^{1/3}))$$Consequently, one can find \(\pi(n)\) in \(O(n^{2/3} \log(n))\).
Most problems involving techniques described above usually ask about divisibility of numbers belonging to a large (with size \(\gt 10^9\)) interval. Examples include:
{{ footers.full_lower() }}


Our product is fully personalized and well balanced for all age of customers or adults. We maintain the standards by lorem ipsum and certified by dolor set amet.
Our product is fully personalized and well balanced for all age of customers or adults. We maintain the standards by lorem ipsum and certified by dolor set amet.
Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos, In massa urna pellentesque habitant morbi tristique senectus.
Call us : 002-6666-8888 or fill out our online booking & equiry form and we’ll contact you.
Make Appointment


Albert Einstein
Einstein is known for revolutuinizing the world of physics. His most widely known contribution is the theory of relativity, which states that E = mc2. In this equation, E refers to energy requirement. The m in the equation stands for the mass of a given object, and c is the abbreviation for the speed of light, which is around 299,792,458 meters per second. This is less commonly known as the universal speed limit!
What does this mean to us? Well, for starters, anything with mass cannot ever reach the speed of light. If mass has any value other than 0, the faster it travels, the energy required to reach that velocity amplifies exponentially. To be able to reach c, an object of mass would require infinite energy. That is why only photons (particles of light) are the only particles that can travel at the speed of light: because they have 0 mass! Are we having fun yet??
Einstein himself, while known as the father of relativity, also made many other important contributions to science. Before he became famous, he was a lowly patent office clerk, working with math in his spare time. In his entire life, he published more than 300 scholarly articles, about half of which were not science related at all. He lived from 1879 to 1955, during his lifetime he received the Nobel Peace Prize in physics, but surprisingly not for relativity. Rather, he received the award for the discovery and mapping of the photoelectric effect. His prize money was given to his wife and children in exchange for a divorce (he was in love with his cousin).


It is open for everyone and free to take part. Participants submit their work samples online. Our judges will shortlist a list of individuals that they deem fit for the movie production.
A set of producers will provide finance for the movie. The budget will be decided after the selection of participants. All selected participants will have to to sign a contract for one movie.
No upfront fee will be provided to any participant. 50% of all profits will be equally distributed among the selected participants in ratio of their effort and experience in making the movie.
We invite talented artists and film making enthusiasts to participate in the contest. Participants can only take part in any one category of their choice.
Participants can only enter the contest till this date. All entries received after this date will be rejected. You are welcome to apply the next year.
Our judges will handpick the script writer(s). The script idea will be further developed with the help of industry experts.
Our judges will select the best direction entries who will work with experienced directors in the upcoming movie of 2017.
The actors will be chosen as per the demand of the script. These actors will work alongside established actors for the movie.
Screenplay will be finalized for the movie of 2017. The scene, location and cast breakdown will also be finalized at this stage.
The production budget will be finalized. UNit production manager will be selected and the shooting schedule will be finalized.
Shooting for the movie will begin and all cast will have to be available during the full shoot of the movie as per the schedule.
We intend to finish the shooting by the end of Sep 2017 and that gives us 3 months for post production work and movie release.
Editing and post production work will be finished during this period. Visual effects will be rendered as per the movie demand.
The movie will be promoted digitally and through offline channels. We will also prepare entries for various film festivals.
We intend to release the movie across India in the month of December. If budget allows, we will release in many languages.
Lead Actor
Director
Script Writer
All selections will be completely based on talent and compatibility with the script and roles.
Please note that this competition is only for Indian Citizens.


the time this alarm was acknowledged
the user that acknowledged this alarm
the number of times this alarm has triggered
the alarm's description
link to the alarm details page on the source instance
the first time an event has triggered this alarm
the alarm ID
journal memo - a note associated with the reduction key for this alarm
the most recent event that triggered this alarm
which location the alarm originated from
the alarm's log message
the node's ID associated with this alarm
the node's label associated with this alarm
the parameters emitted with this alarm's event
the alarm's reduction key
the service associated with the event
the alarm's severity
sticky memo - a note associated with this specific alarm instance
who the alarm was suppressed by
when the alarm was suppressed
when the alarm will stop being suppressed
the trouble ticket ID associated with this alarm
the link to the trouble ticket system if defined
the state of the trouble ticket associated with this alarm
the alarm's type
the UEI of the event associated with this alarm
the most recent time the event has triggered this alarm
Generated using TypeDoc
Represents an OpenNMS alarm.


Seeds of M82 were treated with ethyl metanesulfonate (0.5 percent EMS for 12 h; LD15)
causing primarily C/G to T/A transitions
EMS mutagenesis protocol (tomato seeds)
Imbide seeds on wet Whatman paper (8-10 hrs)
Transfer seeds to an Erlenmeyer bottle containing dH2O (100ml for 10,000 seeds)
Add 0.5% EMS solution
Mix and incubate for 12 hrs with gentle shaking in hood at room temperature
Remove the EMS (put EMS solution into 1M NaOH overnight,
then dispose as regular waste.
Also wash all dishes and pipettes with NaOH)
Rinse the seeds extensively under running water for 5-10 minutes
Dry the seeds in incubator
Sow the seeds, preferably on the same day
Calibration of EMS concentration: (all treatments were given for 12hours)
0.5% EMS = LD15
0.7% = LD25
0.9% = LD70
1%= LD90


We are Cena and we need your help. The Cena Swiper helps us to label food pictures. Our final goal is to create an artificial intelligence that can learn your taste and help us find the best plates served around you. Help us reach our ultimate goal by swiping some images.
Currently we are working on a reward system. Your swipes will be taken in to account when rewards are available.


You can sort, filter, add or remove columns in the log window to make your investigation easier. You can change the order of the columns by clicking and dragging the columns where you want them to go.
Filter the Error Code Column to show only non-success error codes by clicking on the header of the Error Code Column and clicking Custom Filter… In the filter window, add all error codes, then select ERROR_SUCCESS and click the << Remove button. This will show all the failed API calls in the log pane. While this allows you to view all the API failures you’ll see that the Reports feature creates a more organized view based on error type, pass/fail, and will allow you to easily drill down on each API Failure.
Click on the header of any column to sort the column or to add a filter. Filtering the column here will only change the log entries you are currently viewing, Holodeck will continue to intercept and log all API calls. To change which API calls Holodeck will intercept and log click Log > Filter on the menu bar.
To add or remove a column click View > Field Chooser this will allow you to choose which fields show up in the log pane. This will not change what information is exported to the log. All fields will be exported.


About the event
Walkathon is an event, where people walk to raise awareness for a certain cause. We, at Oakridge International School Bangalore, are organizing a Walkathon. This walkathon will be approximately a 5 kilometer walk around a populous area in Bangalore. This will help people understand methods for optimal usage of water and methods for water conservation.
This event will help people know, “Every drop counts”. The idea behind this initiative is to raise awareness about the usage of this precious compound, and its conservation. Join us for this exciting event and the nobel cause for our country.


Basic Information
Description
The wolf is the largest Canidae. It is also differentiated by the broad snout, short ears, short torso, and longer tail. It is slender and very powerful. It's legs are also longer than other typical canids. Wolves have a large head, strong jaw, and blunt snout. The teeth are very good for crushing bone. Females are typically a little smaller than males. Wolves have a wide varity of coats with some being thinner and some being thicker depending on the environment they live in. They also come in many different colors also depending on the environment and habitat the species is typically from.
- Learn more at wolf.org
- Learn even more at National Geographic
Diet
The wolf feeds mainly on wild herbivorous hoofed mammels like deer, moose, and elk. In North America, the diet consists of large hoofed mammels and medium sized mammels, including elk, moose, caribou, white-tailed deer and mule deer. In Europe and Asia, the diet consists of medium hoofed mammels and domesticed species, including moose, red deer, roe deer, and wild boar. Wolves will also hunt smaller animals whwen needed as well. The have also been known to eat certain fruit and berries as well as grass.
Habitat
Wolves are from Eurasia and North America. Their habitat has been reduced by two-thirds because of human predation. Wolves can live in many climates depending on their subspecies. They range from the arid Middle East, to the Cascade Locks, to the Arctic. They prefer wilderness and remote areas. They are typically foudn between sea level and 3,000 meters. Their habitat depends on many different factors from prey, to humans, to water, to snow.


A mapper module that adds text labels to isolines. The module processes the input field data and generates a Point mesh and a list of text labels. These can be displayed by the text_glyph module.
module Isolabel_core <src_file="isolabel.c"> { omethod+req update ( .in+read+notify+req, .in.nnodes+req, .num_labels+read+notify+req, .format+read+notify+req, .out+write, .string_vals+write ) = "isolabel_update"; Mesh+Node_Data+IPort2 ∈ int+IPort2 num_labels; string+IPort2 format; Mesh+OPort2 out { ncell_sets = 1; Point cell_set { ncells => <-.nnodes; node_connect_list => init_array(ncells, 0, ncells-1); }; }; string+OPort2 string_vals[]; };
The Isolabel_core module generates text annotation labels for isoline displays. It connects to the field output of the isoline module and generates a Point mesh and an array of string values. The Point mesh contains the position of the labels while the string array contains the actual label text at each point. These outputs can be directly connected to the text_glyph module, which will then display the labels. The number of labels output and the format of the label text can both be controlled. The module is designed to work best when used with an isoline module, however it can be used to generate text labels for any Mesh with a matching set of scalar Node data.
The label placement algorithm is quite simple and works best in a 2D isoline context. The module subsamples the input node list at even intervals. This will generate a series of nodes that are regularly spaced throughout the input data. Provided the input nodes are distributed evenly in space the output nodes should also be evenly distributed. Although this method works acceptably in most contexts it should be noted that it is not suitable for animation. Due to the way the algorithm works the labels move around unpredictably as parameters are changed. Hence, for example, recording a moving othroslice with labels would not be possible.
&in
Reference to a set of Field data which should be used by the module to generate the text labels. The Field should consist of a Mesh and Node Data. Only the first set of Node data is used and that Node data must be scalar.
num_labels
Number of text labels that should be generated. This is an integer parameter.
format
C style formatting specification string that sets how the Node data values should be converted into text. By altering this format string the exact format of the output labels can be controlled. Internally the format string is used in a call to the sprintf function to perform the necessary conversion. It should be noted that the User macro isolabel does not expose this parameter. Instead it constructs the format string automatically from a UI control.
out
Point mesh containing the locations of each text label. This output can be directly input into the text_glyph module to display the generated labels. If the input mesh contains any transformation data this is copied across to the output mesh.
stringvals[]
String array containing the actual label text that should be displayed. This output can be directly input into the text_glyph module to display the generated labels.
The low-level Isolabel_core module is used in the Functional Macro Isolabel and the User Macro isolabel. Additionally, these macros also use the Isolabel_Params parameter block group, as do the UI macros.
Two example applications are provided, IsolabelEg1 and IsolabelEg2. These applications generate text labels for 2D and 3D isoline plots.
xp_comm_proj/isolabel/isl_mods.v contains the V definitions of the Isolabel_Params group and the Isolabel_core module.
Please refer to AVS documentation for more information on the isoline and text_glyph modules. This module does not use the AG kit, and should not be confused with AGContour which also contains isoline labels.
The low-level IsolabelMods library containing the module Isolabel_core does not specify a process. By default the express process will be used.
John Sheehan, Ian Curington Advanced Visual Systems, Ltd. Hanworth Lane, Chertsey, Surrey, UK KT16 9JX
Andrew Dodd International AVS Centre
Isolabel_Params, Isolabel, IsolabelUI, isolabel, IsolabelEg1, IsolabelEg2.


Northern Irish man arrested in England in connection with Essex lorry deaths
by Stephen McNeiceA 23-year-old man from Northern Ireland has been arrested in England in connection with the discovery of 39 bodies in a lorry in Essex last month.
The bodies of the Vietnamese nationals were found in a refrigerated container in Grays, Essex on October 23rd.
They were found after the lorry arrived in the UK from Belgium.
Police in the UK say they arrested a 23-year-old man in early hours of this morning on the M40 in Beaconsfield, Buckinghamshire in connection with the investigation.
He's being held on suspicion of conspiracy to traffic people and conspiracy to assist unlawful immigration.
Several other people have previously been arrested in connection with the investigation.
25-year-old lorry driver Maurice Robinson, of Craigavon in County Armagh, has been charged with 39 counts of manslaughter, conspiracy to traffic people, conspiracy to assist unlawful immigration, and money laundering.
Meanwhile, a High Court judge yesterday said he is going to ask UK authorities for more information in relation to their pursuit of a man in connection with the investigation.
22-year-old Eamon Harrison from Mayobridge in Co Down is wanted in the UK on 39 charges of manslaughter, a charge of human trafficking and one charge of conspiring to assist unlawful immigration.