How to change a project's name in Eclipse - android

How can I change a project's name in Eclipse?

Soong is a build system specifically for Android Platform development, and not Android app development, even though the Android Platform can contain regular Android apps built for the system image. That means Soong is not supported to use outside of Android Platform builds.
Your best bet here is to import/copy DeskClock's source code into Android Studio and write your own build.gradle files manually.

Related

Use a custom android.jar in an Android Studio project to compile against

A standard Android project uses the sdk.dir property in your local.properties to find your local Android SDK and resolve the appropriate android.jar file to use for compiling against for all of the platform classes.
I'm working on an Android system app so I know I will have access to certain classes an methods that are not ordinarily accessible to standard apps.
I still want to work in Android Studio though so I work with a modified android.jar which I use to overwrite the standard one in my SDK folder.
This approach works fine but I want to know if there is a way to achieve this without butchering my local SDK jar files.
In short, how can I get gradle to resolve an android.jar file of my choosing for compilation purposes but still use the SDK folder for everything else?

How make compiler into android studio project with renderscript?

I tried to import multiple android projects with render scripts, but often it does not make me compile with the "Project SDK is not defined" warning.
How should I do? Do I have to include some words?
I was interested in this project:
https://android.googlesource.com/platform/frameworks/rs/+/master/tests/java_api/LivePreview/
Use Android Studio 2.3.3
Those sources are part of the platform build, not a normal app build used by Android Studio (or even Eclipse.) In order to build it in Android Studio, you would need to manually setup your own project structure and pull the code into the correct place. Sources need to follow the Android Studio / gradle layout (app/src/main/java/... for Java sources, app/src/main/rs for Renderscript sources, etc.)
The SDK location is typically stored in the local.properties file at the top level of your project tree and is developer specific (not committed to rev control.)

Differences of Android apk exported by Eclipse and Android Studio

What are the differences of apk from Eclipse and Android Studio[IntelliJ IDEA]
is there more security in Android Studio build?
Android Studio utilizes the fast growing Gradle build system. It builds on top of the concepts of Apache Ant and Apache Maven but it also introduces a Groovy DSL (Domain-Specific Language) that allows for scripted builds which opens up many automation possibilities like uploading your beta .apk to TestFlight for testing.
Eclipse on the other hand uses Apache Ant as its main build system which a very robust XML based build system .
Please check this SO Answer
ADT (Eclipse) vs. Android Studio: How much APK file size difference is normal?
Conclusion
Both are identical.But i prefer Android Studio.
They both use the Android SDK to generate the APKs, they should be identical.
Code protection (security by obfuscation) is done with ProGuard both on Android Studio and on ADT (Eclipse). So if you use ProGuard, there should be no difference.

How to completely disable NDK support in Android Studio

We have a multi-platform project, with native support, that we are developing in Android Studio using libgdx. We have builds working for Desktop, IOS, Android, Android Wear, and HTML5.
On each of these platforms, we have a different "native" plugin that we are using: a static .a native library on IOS, a .dll on Windows, a bunch of .so files in Android, and a Javascript library on HTML5. All of these, except for the HTML5 version, are built on separate platforms so can't possibly be built by the same Android Studio NDK build.
The problem is that for each of the .java files that declare JNI routines, Android Studio 1.4.x wants to find the source files, but those source files can't possibly be compiled in the IOS project, and likewise for the PC project when running on a Mac.
The standard solution on SO is to add
sourceSets {
main {
jni.srcDirs = [] //disable automatic ndk-build
}
}
To the android{} section, but this ONLY works for the Android, Android Wear launcher projects, and NOT Desktop, IOS, HTML5, etc.
I just want Android Studio to give up on trying to compile NDK, because it can't possibly be done on non-Android projects. Other than finding a downgrade somewhere, how do I do that?
Thanks!
So, I decided that I could figure this out - and I did!
Of course, the NDK builder is just a plugin in IntelliJ, so all you have to do to disable it is to
go to your AndroidStudio installation,
find the "plugins" directory
move or delete the "android-ndk" folder
Tada! No more NDK plugin!
Correct way is to uninstall NDK using SDK manager.
go to Android Studio-> Tools -> SDK Manager
Under SDK tools tab uncheck "NDK", "CMake", "LLDB" and then apply changes. NDK components will be removed.
Downside is NDK is removed for all project. Still struggling to find a way to disable NDK for a particular project only.
If you would like to keep the NDK build for future use and not use it for specific projects just make sure to uncheck these options in the new project dialog...

Qt: make and install module on non-host platform

I am developing an app using a QML-based module (https://github.com/papyros/qml-material) on OSX and would like to test the app on Android and iOS.
How do I set up the qmake file so that the module gets properly installed for the Android and iOS platforms (or, for that matter, any other non-host platform which I have in my Qt distribution) on my host system?
In this specific case, just copying the module folder to e.g. Qt/5.4/android_armv7/qml does not work as the module needs to install some QtQuick Styles and other stuff elsewhere as well.
I figured this out. Running the platform-specific qmake alone wasn't working because this project contained two subprojects, each one with its own Makefile.
It was sufficient to (re-)run the platform-specific qmake for each subproject and for the main project prior to running sudo make install.
So the bottom line is, make sure that the Makefiles that qmake generates for subprojects are updated for your target platform.

Categories

Resources