[android-porting] The Binder header files moved: how to track them

2010-02-04 Thread Trey Boudreau
Howdy all, The binder got promoted to its own component between 1.x and 2.x, complete with a distinct library and include file location. If we want to have a single set of C++ sources, how should we check for the location in the makefiles? Thanks, -- Trey -- unsubscribe: android-porting+unsubs

Re: [android-porting] The Binder header files moved: how to track them

2010-02-04 Thread Dianne Hackborn
Unfortunately it isn't possible to have a single set of sources for things that are not in the SDK or NDK. We make sure to maintain compatibility with the official APIs, but with internal things like Binder they can change arbitrarily. I guess all you could do is a lot of makefile and #ifdef tric

Re: [android-porting] The Binder header files moved: how to track them

2010-02-04 Thread Trey Boudreau
Yeah, I figured as much, but do you have a recommendation as to what makefile variable (and perhaps its range of values) we should predicate on? Thanks again, -- Trey On Thu, Feb 4, 2010 at 2:12 PM, Dianne Hackborn wrote: > Unfortunately it isn't possible to have a single set of sources for thi

Re: [android-porting] The Binder header files moved: how to track them

2010-02-04 Thread Dianne Hackborn
Hm... not sure. Possibly you could use PLATFORM_SDK_VERSION which is the API version of the current platform (Cupcake was 3, Donut 4, Eclair 5 or I mean 6 no I mean 7). On Thu, Feb 4, 2010 at 12:16 PM, Trey Boudreau wrote: > Yeah, I figured as much, but do you have a recommendation as to what >