a759cc912f
This does almost everything until the final build and fails there because we are using too modern software with a too old project, I think. Signed-off-by: Raito Bezarius <masterancpp@gmail.com>
38 lines
1.1 KiB
Text
38 lines
1.1 KiB
Text
ECLIPSE ANDROID PROJECT IMPORT SUMMARY
|
|
======================================
|
|
|
|
Ignored Files:
|
|
--------------
|
|
The following files were *not* copied into the new Gradle project; you
|
|
should evaluate whether these are still needed in your project and if
|
|
so manually move them:
|
|
|
|
* 0001-Add-33c3-configuration-No-CA-yet.patch
|
|
* android.iml
|
|
* patches.txt
|
|
|
|
Moved Files:
|
|
------------
|
|
Android Gradle projects use a different directory structure than ADT
|
|
Eclipse projects. Here's how the projects were restructured:
|
|
|
|
* AndroidManifest.xml => app/src/main/AndroidManifest.xml
|
|
* assets/ => app/src/main/assets
|
|
* lint.xml => app/lint.xml
|
|
* res/ => app/src/main/res/
|
|
* src/ => app/src/main/java/
|
|
|
|
Next Steps:
|
|
-----------
|
|
You can now build the project. The Gradle project needs network
|
|
connectivity to download dependencies.
|
|
|
|
Bugs:
|
|
-----
|
|
If for some reason your project does not build, and you determine that
|
|
it is due to a bug or limitation of the Eclipse to Gradle importer,
|
|
please file a bug at http://b.android.com with category
|
|
Component-Tools.
|
|
|
|
(This import summary is for your information only, and can be deleted
|
|
after import once you are satisfied with the results.)
|