I am trying to create a LittleKT project in Visual Studio Code. I tried building a Gradle instance of the project but was told that I did not have an Android SDK. I installed the Android SDK Tools and got pretty far. I was unable to use a key emulator that I needed and was wondering if I could completely remove android support for my project.
Any advice pertaining to LittleKT or how to install the needed emulator I need would be greatly appreciated. I did not include many details as to doing that because that is not the point of this question. Plus, there are plenty of discussions pertaining to that issue.
Thanks
Related
Can Eclipse in conjunction with ADT still be used for Android Development (and if yes, how do I go about it) or should I just keep using Android Studio?
I tried setting up ADT on my Eclipse, but it wouldn't work (after many, many tries).
Any advice would be appreciated.
yes you can but the best practice for android development is by using Android Studio because linux users has also problem with eclipse. you can take help from below link
https://stuff.mit.edu/afs/sipb/project/android/docs/sdk/installing/installing-adt.html
but as per my suggestion you should use Android Studio because if you are using eclipse then you need to migrate the code also.
Can anyone help me with installing the correct version of eclipse to use for developing android mobile applications with the associated plug ins needed
These videos by me :) can help you to set up Android development environment using Eclipse.
Here's the link : Set up android.
Caution : If you have been using Eclipse with ADT, be aware that Android Studio is now the official IDE for Android, so you should migrate to Android Studio to receive all the latest IDE updates. For help moving projects, see Migrating to Android Studio.
As Petey suggested in his comment, I would recommend giving AndroidStudio a spin as it is very well suited to Android programming. However, take a look at the eclipse ADT plugin which can be installed via the eclipse marketplace or a direct download from Google (Google ADT page).
That should give you enough information to get things rolling, but again I would strongly recommend trying to switch over to AndroidStudio. I think you will find the entire experience easier to get into and enjoy.
Here is the link :)
P.S. Why do people still use Eclipse while there is a GREAT tool for developing Android applications?
I work as an android programmer for just under a year now, and I just started to learn about android game development. The framework I choose to work with is Cocos2d-x.
I have seen guides and tutorials on how to use Cocos2d-x with eclipse, but I'd really like to know if it's possible to be used with Android Studio.
From what I've read, it is now possible to build NDK projects with gradle in Android Studio, which is good news. Nevertheless, I have yet to find any information about C++ programming using Android Studio. Eclipse uses the CDC ( https://www.eclipse.org/cdt/ ) plugin to achieve this.
Is there anything similar to be used with Android Studio? I have found some C/C++ enabling plugins for the IntelliJ Platform, but they were no longer updated.
Has anyone else tried this before? Did it work? Can you provide a step-by-step guide, for a newbie like me, who's dealing with this kind of problems for the first time?
Thank you for you time,
haxm
Android Studio currently isn't well set-up for native programming. While the build system supports the NDK, there's no editor support for C++ files (it's not as if it won't work, but the IDE won't give you any editing assistance), and neither is there any debugging support. JetBrains has announced that they're working on new C++ support for IntelliJ, and this is something we're looking at for Android Studio, but it's not on the roadmap yet.
Recent version of cocos2dx v3 (from github for example)
have proj.android-studio project
At this moment I have no success to build it but maybe in future it will be fixed
I just went through the setup for this example code. The project compiles and has a ton of sample code. Scott Barta's answer still stands as an important caveat, but wanted to share the link in case it was useful.
I also found this useful for some NDK background/how-to.
I posted this question on the IntelliJ community forums but it seems as if they aren't very active so I'll just post it right here on S/O. I'm new to IntelliJ and I'm switching to use it from Eclipse which was really buggy and not useful to my needs. However, I'm attempting to build an Android project in IntelliJ Idea and it is only creating a .idea folder and the src directory without any inner files in them like it should. I've got the Android-SDK properly installed and I'm using JDK 1.7 and I'm even following the directions to properly start an Android project from the IntelliJ Wiki (found here) but it still leads me to no success. It seems as if I've got the Android Support plugin already installed with my program but then again I'm not really sure. Can I get some help please so I don't have to revert back to Eclipse again? Thanks.
Try to delete Android SDK and install it again, then download at least one Platform. IDEA runs SDK tools to create Android project template, for some reason it's failing on your system.
Check if it works better with JDK 1.6.
See the screencast that I've just recorded.
I'm recently started working on a school project using IntelliJ IDEA to develop an Android app. Most of the guys in my team (me included) are used to the way visual studio organizes project into .sln files. We've had all sorts of frustrations with IntelliJ mostly because we don't understand how IntelliJ organizes projects. We finally got the project to load reliably without having to make changes to each developers set up by following the steps here:
http://devnet.jetbrains.net/docs/DOC-1186. However, now anytime we get latest the Run/Debug configurations disappear. Anyone having the same problem?
Thanks,
Check this answer.
Make sure that you are sharing your configurations and files from the .idea/runConfigurations directory are added to the version control.