Another thing to try (when 'clean' fails) is to edit the whitespace in main.xml, forcing Android to treat it as news. This in turn means 'rebuild R.java'. Usually, this works. I have seen it fail only rarely. Then I copy all my files to a safe place and create the project all over from scratch:(
On Jul 8, 12:42 pm, kypriakos <demet...@ece.neu.edu> wrote: > It seems that the gen dir is empty and that no generated java classes > are not being generated (no R.java etc.). I am assuming the Clean > Project > removed them (??). How can they be regenerated? > > Thanks again > > On Jul 8, 3:37 pm, kypriakos <demet...@ece.neu.edu> wrote:> Never mind - I > needed to manually clean up the build path file as well > > to > > match the fact that the lib didn't have those files anymore. So now I > > can > > compile the project with no errors either visible (with x next to the > > dir or > > any file in the project tree) or in the Error Log that Eclipse > > provides. > > However, still the plug in will complain when I try to run it with the > > same > > error msg 'The project contains errors ....' ... makes no sense. > > > On Jul 8, 3:18 pm, kypriakos <demet...@ece.neu.edu> wrote: > > > > David - thanks very much for the detailed and very informative > > > response. I appreciate it. > > > I looked into the Error Log of the IDE and I did see that certain > > > libraries (external libraries > > > that I needed to reference through my code, such as BouncyCastle etc.) > > > had also a txt > > > file with them that the Android plug in didn't like. By removing them > > > I was able to remove > > > those errors. However, what's interesting now is that after I also did > > > a Clean on the pioject, > > > all of the bin classes I had in the bin directory are not being > > > regenerated. I checked the IDE's > > > configuration and it does has the project to build automatically. I > > > can see the workspace > > > build progress flash at the bottom bar but no classes (even after > > > refreshing the view) generated > > > in the bin. This makes no sense unless those txt files are necessary > > > for using their corresponding > > > libs: > > > (1) if that is the case, where could I include those txt licenses in > > > the case of Android > > > (2) if not then what would cause the classes that about 10 mins were > > > generating output binaries > > > to do it now as we. > > > > Thanks aga > > > > On Jul 7, 7:03 am, "Bagatelle: David Lee Evans" <dle.ev...@gmail.com> > > > wrote: > > > > > On Jul 7, 1:07 am, Demetris <demet...@ece.neu.edu> wrote: > > > > > > Hi all, > > > > > > I generated a standard Android under Eclipse (using the plugin) and I > > > > > imported code from an existing project (J2SE-based). I was able to > > > > > iron out all the complaints from the Android SDK 2.1 (compile errors). > > > > > However, the runtime (emulator startup) the IDE displays a message > > > > > saying that the project contains errors, please fix them before > > > > > running > > > > > it. But all that there is there are warnings - is Android > > > > > "unforgiving" > > > > > about Java warnings or is there something else I should be looking > > > > > into > > > > > in there - no class has any compile errors. > > > > > > Thanks > > > > > Without seeing the exact Eclipse error output, I am assuming the > > > > following. > > > > When you view your project in the package explorer window, your > > > > project has > > > > an error X icon next to it, but looking at the project tree > > > > structure there is no offending > > > > error X icon next to any other directory. So I going to suggest a > > > > shotgun approach > > > > to fix your problem, probably all you have tried. > > > > > 1)The always first move that I always do is clean the project, > > > > sometimes the Eclipse ADT gets a little confuse about the state of the > > > > project. > > > > > 2) Since you imported the project from another source project, > > > > check the AndroidManifest.xml file for incompatibility problems > > > > makes sure is the attribute tag android:minSdkVersion if > > > > defined is appropriate for the project. > > > > > 3) Then there is the hidden .project file that ant uses to build > > > > the project, make sure that file exist because if it does not, > > > > it will give you the exact same symptoms that you have > > > > describe. It should have been create for you by the Eclipse IDE when > > > > you created an Android project. > > > > > And about Android warnings, my projects have a lot of them ;-) > > > > but this has never caused the emulator to start up, so unless > > > > you have some special flag set that I have never heard of I don't > > > > think that the warnings would abort an emulator launch. > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
