Граф коммитов

6 Коммитов

Автор SHA1 Сообщение Дата
yfriedman@chromium.org da06ce8ed8 [Android] Change jni_gen_dir to jni_gen_package for jni_generator.
With the old name it was getting relativized which is undesirable. See
bug for more details.

BUG=159133
TBR=ben (nobody really cares about this outside of build/ which cjhopman approved)


Review URL: https://chromiumcodereview.appspot.com/12558005

git-svn-id: http://src.chromium.org/svn/trunk/src/build@186803 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2013-03-07 22:34:05 +00:00
tedchoc@chromium.org 7a45e488db Add gyp flag to specify whether we should optimize JNI generation.
Do not regenerate JNI files (and subsequently the .so file) if they have
not changed.  This will happen if you edit a java file that has a native
counterpart, but the native signatures were not touched.

We do not enable this all the time as some build systems require that
when you modify an input, the output should also be modified.  This
also will result in more command line output, so we'll keep it behind
a developer flag for now.

BUG=


Review URL: https://chromiumcodereview.appspot.com/12314025

git-svn-id: http://src.chromium.org/svn/trunk/src/build@183936 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2013-02-22 00:37:33 +00:00
bulach@chromium.org 7d38bac524 Android: uses "import" section and inner classes for obtaining qualified JNI parameters.
Rather than explicitly listing all the parameters
(see crbug.com/158722), infer almost all of them from the import section and inner classes.
Assumes other classes are in the same package as a fallback.

BUG=159397
TEST=base/android/jni_generator/jni_generator_tests.py


Review URL: https://chromiumcodereview.appspot.com/11363079

git-svn-id: http://src.chromium.org/svn/trunk/src/build@166482 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2012-11-07 19:06:51 +00:00
bulach@chromium.org 97330b958e Android: passes a list of qualified JNI parameters as a param to the generator.
Instead of hardcoding the list of qualified JNI parameters,
pass it as a parameter so that different modules can inject their
classes.
This is the first step in such decoupling; follow up will start splitting
the class_list.jni list closer to their modules.

BUG=158722
TEST=jni_generator_tests

Review URL: https://chromiumcodereview.appspot.com/11339013

git-svn-id: http://src.chromium.org/svn/trunk/src/build@165250 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2012-10-31 22:58:15 +00:00
bulach@chromium.org cd14de0058 Uses gyp "rules" rather than "actions" templates for the JNI generator.
This allow finer grain control over what is rebuilt.
Also, since we have approval over the generated header file name,
it greatly simplifies both the generator and also all the gyp files
as they no longer need to list the header file and keep in sync with the
java file, so the process now is as simple as adding a single java file
to the sources.

BUG=137069
TEST=build on android


Review URL: https://chromiumcodereview.appspot.com/10798010

git-svn-id: http://src.chromium.org/svn/trunk/src/build@147515 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2012-07-19 20:02:55 +00:00
yfriedman@chromium.org 884abb2d56 Add templates for building java and running the jni_generator.
As requested in http://codereview.chromium.org/10073024/, I've created
templates for these two actions. I've also applied them to base.


Review URL: http://codereview.chromium.org/10081035

git-svn-id: http://src.chromium.org/svn/trunk/src/build@132537 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2012-04-17 04:39:52 +00:00