2
When I create a project and the appcompat_v7 is closed the project gets error, but if it is open has no problem, it is normal for projects to depend on the appcompat_v7?
3 answers
3
Yes, it is necessary to support older versions of emulators. You can change the SDK to at least 14 or higher, which does not depend on the appcompat.
1
Yes, it’s normal. It turns out that the project appcompat_v7 has the libraries that the project needs to import to work on older versions of emulators, or rather emulators emulating older versions of the Android OS.
But it is possible to take out this dependency. You have to look in the . xml files for this.
As an addendum, change the project name with something specific to easily identify which appcompatv7 is which project, or add the appcompat project to the list of related projects you’ll be developing from. Will facilitate to close unnecessary projects/open necessary ones.
1
Daniloalbergardi,
If your project is being developed using the library appcompat, it is necessary that it is assigned to your project. By your image is missing the imports of that library.
What good is?
These libraries have been made available as a support mode for devices using older versions of Android, we can illustrate a good example of this is how to access the SDCARD between versions with ContextCompat.getExternalFilesDirs which can be used in all versions.
To add appcompat to your project go to:
Properties do seu projeto > Android > Add e coloque o appcompat.
Browser other questions tagged android-eclipse app-compat-v7
You are not signed in. Login or sign up in order to post.