Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I am a beginner to Android NDK with Android Studio. While trying to grasp the ideas through tutorials I got my self very confused. Mainly I am confused about the building method of native project.
For example while following this tutorial, when I build the project there is no file created inside libs project. Moreover, there is no need of Android.mk and Application.mk make files also.
However, second tutorial deals with the make file.
Can anyone please explain to me step by step explanation of build steps. I am not sure how hard it is for Android team to make a simple tutorial explanation one version of built.
Not sure, if by the time of this writing (2016/02/01 - Android Studio 2.0 Preview 9) NDK is officially supported yet, but it's surely been under development. That's the reason of using Eclipse+ADT+NDK in the official guide as you can see in the Setup section. I believe, once the process is done, the documentation will be updated.
You're free to choose which approach to use:
Eclipse+ADT+NDK or
Android Studio + Gradle + NDK
With the second approach Gradle generates *.mk files automatically, although you can use your own files by preventing the auto-generation as per The new NDK support in Android Studio by ph0b.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
This post was edited and submitted for review 1 year ago and failed to reopen the post:
Original close reason(s) were not resolved
Improve this question
Some developers struggle with the complexity and performance of Gradle:
It can take a long time to build simple app.
It can takes a long time to build simple change in that app again.
It can be very difficult to debug build failures.
It is a large and complex system, with a steep learning curve.
It requires learning Groovy and a family of DSLs.
It is not easy to re-use build scripts across large projects.
So, is there an alternative to gradle for android application development?
Looking for a practical, easy to maintain build system which saves developers time.
I think every Android developer asked him/herself that question more than once.
However, Google puts all efforts into improving Gradle builds for Android. Since they are the inventors/owners of Android and a big big company too, I very much doubt, that there is any different building system that comes close to Gradle.
Additionally to Gradle and Google improving the build process with every new version of Gradle and/or Androidstudio, there are many ways to improve the building speed. Easiest one is to allow gradle to use more RAM.
But you can find a ton of information about that by searching the internet a bit.
You can build Android apps with maven or ant, from a shell. You'd have to create your own build scripts. A few years ago, when Google still supported the Eclipse plugin for Android, they used ant as the build tool.
However, it's my experience that gradle is not slower or faster than either maven or ant. There must be something else that slows your build process.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I have some Appium testing scripts that needed to be put through a repository for version control, mainly Git.
I looked through Google to figure out what is the best way to go about this if you have an Android App project in Andriod Studio that you're writing the tests for (which happens to be in it's own Git repository), and so far I haven't found anything in my search.
My question is: Would it be better if I include the test scripts inside the Android studio project in it's Git repository, or would it be better if I put the test scripts in their own repository? If putting the scripts in the Android project is better, where in the project's file structure should I include the test scripts?
Any input is greatly appreciated.
I put my autotests in separate repository just to have them safe from deleting from my work computer or something else.
When I'm sure that my tests are stable I clone dev branch of the main project and making a pull request including my tests. When my request is merged we have a project repository with autotests.
Don't know any better ways, but for me it works great and very comfortable.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
My company gave me a 4 year old Android Project that I have to fix. I've been used to working with IntelliJ and Android Studio for a while now. At first sight I saw this was an eclipse project and I've tried numerous things to get this to work on Android Studio, more specifically like the following.
I'm also trying to integrate Gradle in this project. But even after trial and error I do not get the expected result that I normally get with my own projects, note the arrows I usually get with my other projects. Now it looks totally different.
Any help or tips on how to get this old project back on its feet is highly appreciated.
This could help you a lot:
Migrating from Eclipse ADT
Another critical thing is that if you are a keyboard-oriented programmer, it will take some time to get used to Android Studio's shortcuts. Even though it has some eclipse shortcut support.
Which can be easily found in here:
Eclipse Shortcuts
Good luck.
You can follow the following steps, no need to export the projcet as Gradle, Android Studio (AS) provides this by default,
Go to File menu and select New -> Import Project
next from the File browser select your Eclipse Project folder,
click Next in the subsequent steps and lastly Finish to successfully import the project
There may be some dependncies of your project but you can read the instructions provided by the Android Studio import dialogs and handle them,
ask further if you need help.
In the worst case scenario, you can always make a project by the same name, copy the sources (and resources) into their corresponding package, move the relevant stuff from the old AndroidManifest to the new, and add the external dependencies (such as that Google Play Lib for example) through Gradle itself.
If the project uses NDK, then you're gonna have a bad time though, because that requires setting up the Gradle experimental branch.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
What are the main differences between using Eclipse with the Android plugin and the standard Android Studio?
Which one do you recommend? (I guess it varies with how we plan to use it).
Thank you in advance for the help
Please use Android Studio, Eclipse is no longer supported. You can import your Eclipse projects and use them in android studio. Also check the following questions:
Android Studio vs Eclipse with ADT (2015)
Which Android IDE is better - Android Studio or Eclipse?
Finally, I found the following two reasons to be great positives to use Android Studio:
It supports gradle (this allows you to really have control over the build, create different application flavors, different signing configurations and so on).
It feels better. From doing a refactoring (like renaming a method, to extracting a class) to viewing the Logcat. The refactoring seem more solid and the Logcat does not "disappear" as it happens in Eclipse.
Eclipse is basically for Java program development and used for Android with ADT, whereas Android Studio is available specifically for Android development and you will get a lot of help with it.
Studio is definitely better for designing layouts running emulators.
Studio provides better debugging and help popups when you start coding.
I would recommend you go ahead with Android Studio as it will prove to be helpful even if you stuck somewhere with the method names or anything else.
Eclipse sucks. Go for Android Studio which is based on the unbeatable Java IDE - IntelliJ Idea (known as JetBrains Idea these days).
Android Studio uses the dependency and gradle structure whereas eclipse do not use it.
I recommend you to use Android Studio. It is the Best for Android Programming. Some newer updates are not available in Eclipse. Android Studio does has.
These are few positives :
No R file errors, it gets generated at compile time and uses stub for development.
Very good and fast autocomplete feature
Preview of resources (Drawables, styles, etc) along side code
List of layouts used in a class file
Analyse code and fixes it using single click (LINT tool is used for this). This tool is very good, you also learn about your mistakes too
References of methods (shows parts of code from where a method is called)
Builtin support for ANT, Maven, gradle, git, svn, etc, etc
No need for extra plugins for Android
Better visual editor than Eclipse
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions concerning problems with code you've written must describe the specific problem — and include valid code to reproduce it — in the question itself. See SSCCE.org for guidance.
Closed 9 years ago.
Improve this question
today I've updated my Eclipse (Win7 x86_64) with latest android updates and it caused some errors. First of all, after cleaning project Eclipse didn't generate R files. I've tried to find any possible error in my xml files, although - there was none. I've copied my project and opened it with Eclipse without latest updates on Arch Linux - Eclipse generated R file and everything was OK. I think that's also important to mention, that after updating Eclipse on Windows the new code, that I've written didn't work - worked perfectly on Linux's instance. I've copied all R files and folders to Windows, yet couldn't run app, because my apk was missing and after that I've just gave up.
Anyone had similar problems or is there any possible solution?
i had experienced the same. For the new SDK(ver 22.0.1), we need to install a new tool Android SDK Build Tools.
After that, update the eclipse ADT.
Restart the eclipse.
Then clean and run the project.
I had a similar experience some versions back. The work-around I found was to setup an entirely new and separate IDE instance including a different SDK folder location. Install from scratch! Good luck ...