Jason, Perfect! I don't know how I missed that. I'm glad a configurable option was able to fix it. I just tested and things seem to be working correctly again.
Thanks for figuring it out! On Aug 28, 5:33 am, Jason <[email protected]> wrote: > Hi, > > I am one of the elusive few running this exact setup, and I too have > been a bit annoyed by this "feature". > > I did just find this: > > Window->Preferences->C/C++ > > There is a checkbox option entitled: > > "Build configurations only when there are Eclipse resource changes > within the project and its references" > > I tried checking this at it seemed to eliminate these extra builds. > > I also tried making a small change to a C++ source file in my project > and it picked up the change when I ran the app.. so seems to work. > > On Aug 28, 12:29 pm, Robert Green <[email protected]> wrote: > > > > > Hey guys, > > > I doubt there are too many people who run CDT in eclipse for native > > apps also with ADT installed for Android, but in the off-chance that > > someone here knows anything about this, my problem is that any time I > > run any android app, my C builder kicks in for projects totally > > unrelated. I have no idea why and have been digging through settings > > on everything, unable to find out why. All I can think is that the > > ADT pre-launch process triggers it via a refresh or some kind of catch- > > all type call in eclipse API land that I'm unaware of. > > > Does anyone know anything about this? It's very annoying to have a C > > builder run for a different project than the one you're working on > > every time you launch the app. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
