Clone of https://chromium.googlesource.com/chromium/src/build with Mozilla's local modifications
9f9e39c561
This is the GN equivalent of build/java.gypi. It is a template for creating an Android library including java code and Android resources. It currently only compiles java files (including files in srcjars from srcjar targets like java_cpp_template) and zips them together in a .jar and creates the corresponding .jar.TOC. Some of the things still to do: proguard_preprocess, android_lint, emma coverage, dex, everything resources. Adds android_java_library rule for base_java, guava, and jsr-305. This add the --java-srcjars argument to javac.py. This will accept a .zip of .java files and include those files in the compilation. This approach is preferred over using the --src-gendirs option. Many of the parts of building Android stuff (libraries, resources, apks) require knowledge of the dependents of that thing. Examples: javac classpath, for resources aapt needs to know about all dependents, dexing for an apk needs to know about all java code going into that apk. For gyp, this is done primarily with all_dependent_settings. There is then some of this logic in two particular steps (dexing and proguard). These steps, when building an instrumentation apk, need to exclude the things in the tested apk and this is done by having the tested apk essentially write a file saying what it did in those steps and the test apk reading that file and excluding stuff. In GN, all_dependent_settings doesn't really work. This change introduces a new way of calculating and using this information. Specifically .build_config files and build_utils.ExpandFileArgs(). The build_config file for a target contains the information that depends on dependents. The logic in write_build_config and the logic in the template specification are very much tied together (in some sense, write_build_config is just the part of the template specification that can actually inspect the dependency graph). With build_utils.ExpandFileArgs() all the other build scripts are essentially unaware of the .build_config files and can just be written in a (mostly) straightforward way. A large part of the information calculated by the build_config is finding input files to later actions. This requires that those later actions writes a depfile that contains any inputs that are specified by the build_config (in the case of this change, javac and the classpath files). Since a action's script shouldn't really know about the build_config file and what information it got from that, it is safest for the action to write *all* of its inputs into the depfile (but to be correct it only has to write those that aren't explicitly specified in the build files). Depends on: https://codereview.chromium.org/341823003/ BUG=359249 Review URL: https://codereview.chromium.org/269943005 git-svn-id: http://src.chromium.org/svn/trunk/src/build@280995 4ff67af0-8c30-449e-8e8b-ad334ec8d88c |
||
---|---|---|
android | ||
config | ||
git-hooks | ||
internal | ||
ios | ||
linux | ||
mac | ||
secondary | ||
slave | ||
temp_gyp | ||
toolchain | ||
util | ||
win | ||
OWNERS | ||
README.chromium | ||
all.gyp | ||
apk_fake_jar.gypi | ||
apk_test.gypi | ||
apply_locales.py | ||
asan.saves | ||
branding_value.sh | ||
build-ctags.sh | ||
build_config.h | ||
check_return_value.py | ||
chrome_settings.gypi | ||
common.croc | ||
common.gypi | ||
common_untrusted.gypi | ||
compiled_action.gni | ||
compiler_version.py | ||
copy_test_data_ios.gypi | ||
copy_test_data_ios.py | ||
cp.py | ||
detect_host_arch.py | ||
dir_exists.py | ||
download_nacl_toolchains.py | ||
env_dump.py | ||
escape_unicode.py | ||
extract_from_cab.py | ||
filename_rules.gypi | ||
find_isolated_tests.py | ||
gdb-add-index | ||
get_landmines.py | ||
get_syzygy_binaries.py | ||
gn_helpers.py | ||
gn_run_binary.py | ||
grit_action.gypi | ||
grit_target.gypi | ||
gyp_chromium | ||
gyp_chromium.py | ||
gyp_helper.py | ||
gypi_to_gn.py | ||
install-build-deps-android.sh | ||
install-build-deps.sh | ||
install-chroot.sh | ||
intsafe_workaround.h | ||
inverse_depth.py | ||
isolate.gypi | ||
jar_file_jni_generator.gypi | ||
java.gypi | ||
java_aidl.gypi | ||
java_apk.gypi | ||
java_prebuilt.gypi | ||
java_strings_grd.gypi | ||
jni_generator.gypi | ||
json_schema_bundle_compile.gypi | ||
json_schema_compile.gypi | ||
json_to_struct.gypi | ||
landmine_utils.py | ||
landmines.py | ||
nocompile.gypi | ||
output_dll_copy.rules | ||
precompile.cc | ||
precompile.h | ||
protoc.gypi | ||
protoc_java.gypi | ||
protoc_java.py | ||
release.gypi | ||
repack_action.gypi | ||
sanitize-mac-build-log.sed | ||
sanitize-mac-build-log.sh | ||
sanitize-win-build-log.sed | ||
sanitize-win-build-log.sh | ||
shim_headers.gypi | ||
some.gyp | ||
symlink.py | ||
toolchain_vs2013.hash | ||
tree_truth.sh | ||
uiautomator_test.gypi | ||
update-linux-sandbox.sh | ||
vs_toolchain.py | ||
whitespace_file.txt | ||
win_precompile.gypi |
README.chromium
List of property sheets to be included by projects: common.vsprops Not used anymore. No-op. Kept for compatibility with current projects. debug.vsprops Enables debug settings. Must be included directly in Debug configuration. Includes internal\essential.vsprops. external_code.vsprops Contains settings made to simplify usage of external (non-Google) code. It relaxes the warning levels. Should be included after debug.vsprops or release.vsprops to override their settings. output_dll_copy.rules Run to enable automatic copy of DLL when they are as an input file in a vcproj project. release.vsprops Enables release settings. Must be included directly in Release configuration. Includes internal\essential.vsprops. Also includes "internal\release_impl$(CHROME_BUILD_TYPE).vsprops". So the behavior is dependant on the CHROME_BUILD_TYPE environment variable.