I recently started using eclipse to compile my Android code (which I'm also pretty new at) and I tried to download another eclipse.exe that was supposed to be for C++. Anyways, I don't know if that would be the cause of my problems but I noticed that after I tried to give myself the option of compiling C++, just the main file in my Android project gave me the error "cannot create extension." Anyone know how I can fix this? Again, it's just in the one file so i wouldn't think it's a setting issue but I'm not really sure.
This is what my window looks like
TIA
Related
I am a complete newbie who has just about started android app. development using Xamarin Forms and VS2012. Only about 20-21 days of exposure I have got. I am trying to learn along the way through writing an imaginary practice app. But there are some errors I am getting. You can see them in the picture.
http://imagebin.ca/v/29PeHoLhwW1i
Can someone direct me what exactly it is saying and what I need to do in order to rectify them?Is there something wrong with the installation/environment or like some update? Or is it something else? What's with the "unzipping failed" message?
Some one kindly help me out here please. Facing great deal of difficulty in tackling this.
Many Thanks in advance.
As the error message says (see the third error message ), you need to install the "Android Support Repository" from the Android SDK manager.
The errors are telling you that Xamarin is looking for the support library, but that it cannot find the support library and thus the build failed.
#Tanis.7x and #Jason.
Just an update I want to post:
I went about reproducing this scenario: creating a new project, do some primary simple code, add 1,2 layouts et all. When I build the new project, these 9 errors don't appear. This is strange to me. Because: this is exactly what had happened to my main work also. These errors were not there. Something, somewhere happened along the line, due to which they started appearing suddenly; out of the blue. I remember, I had updated Xamarin version, also just added some packages like JSON.Net and it is only after that this error list appeared. Not before that, if I remember correctly. Which is weird to me. If you try to recreate by creating a brand new project these 9 errors won't appear. I tried recreating this twice; no errors.
Yes, I'm manually downloading the zip file. Hopefully this makes the compiler happy. I'll keep posted about the updates.
Thanks All!
I ran my program just fine a few minutes ago, and when I added more functionality now it is telling me "The JRE Instance Default XSLT processor does not support debugging_ Would you like to debug using the default Xalan 2.7.1 processor instead?"
I did restart Eclipse maybe that has something to do with it? :/
It's my first times writing an app so if I have to set something in eclipse each time maybe that's why? and what is it if that is the case.
Thanks!
You were in an XML file when you hit debug, I would bet. Happens to me all the time. For some annoying reason it does something entirely different that I don't understand when you do that. Delete the .out.xml that should probably have been created, open a .java file, and try to debug again. Another way is to just right-click your project and do Run As > Android Application.
I am very new to Android and Eclipse. I find very difficult to fix up the errors in Eclipse. Android emulator keeps crashing, even for few lines of codes. Is there any tutorial or video tutorial available, that can help me to spot errors on looking at the error log.
Here is a basic tutorial that will get you familiar with Android Debugging and Logcat : Debugging in Android using Eclipse . Also you can set breakpoints and debug as you would for any other Eclipse project. The logging of errors, its different tough, using Logcat.
Yes, you can open DDMS perspective and LogCat window to view logs and can see what is the original issue.
When it crashes, check the LogCat. It contains the stack trace with the exception, and is often enough to see what went wrong and fix it. It can be browsed directly in Eclipse (don't know exactly how, I'm using IntelliJ).
Also, you can use normal debugging on your Android project, exactly the same way you would on a Java (non-Android) project.
I've decided to start learning Renderscript as a possible solution to my next project. However, I'm having trouble even getting Eclipse to run the thing. I'm importing the examples that come with the SDK 11. It seems to have trouble importing the headers. Eclipse doesn't recognize the directives like pragma or extern. Also, whenever I include a required file such as rs_core.h a message pops up stating llvm-rs-cc.exe has stopped working. I assume there's some sort of setup that I'm missing, but I can't find anywhere on the web that explains it.
"Replace /platforms/android-[11|12|13]/renderscript with the version located at /platforms/android-14/renderscript" see this question.
I relatively new to using Eclipse with the Android SDK. Whenever I encounter an error/force close, Eclipse displays a page showing "Source not found"
Is it possible to get it to show the error that is causing this? I assume this is achieved by somehow linking to the android source code. Is this mistaken?
Basically, I am struggling to identify the source of my error, and am hoping eclipse can offer more information than at present.
Appreciate any help with this,
Venatu
Source not found because the Exception is raised from something that you don't have source code, (e.g. Android SDK). You should always refer to the LogCat (Window -> Show View -> Other -> Android -> LogCat) to get the extended information about your exceptions.
Reference: http://developer.android.com/guide/developing/debugging/debugging-projects.html
Yes, most likely eclipse tries to access the android code, which isnt possible since its a library. If you get a force close or any other crash it's always a good idea to take a look inside the logcat, Android prints the stacktrace there. You can usually see exactly which function and codeline causes the issue.
Open the logcat either inside Eclipse via Window->Show View->Other->Log cat
or by starting the ddms application inside the android-sdk/tools directory.