This happens to me very often. Every time I do a release build outside of Eclipse, when I go back into Eclipse, the build will fail every time. It will eventually work with no pattern that I could establish -- I need to clean/rebuild about 10 times and then it will build without errors and from then on it's ok until the next release build.
On Mar 6, 9:24 am, TreKing <treking...@gmail.com> wrote: > On Sat, Mar 5, 2011 at 6:50 PM, Nathan <critter...@crittermap.com> wrote: > > Now all my builds in Eclipse are broken. They have hundreds of > > errors saying that R cannot be resolved > > > I've already tried Project Clean, which is the only trick I know for weird > > build errors. > > > The projects include a library project and two projects which depend on it. > > > What magic do I have to do to make these things build again? > > Yeah, I'm noticing that if you do a clean on everything, it wipes the gen > folder completely and gets lost from Eclipse. What I do is clean everything > then refresh the "Root" library project (the one all others require to > build). That forces Eclipse to pick up the gen folder again, triggers > another build, and now all R references should resolve. > > Fun. > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices -- 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
