I thought the previous build config was compared and 'installclean' was run when the variant was changed.
>From cleanbuild.mk ---- # Since products and build variants (unfortunately) share the same # PRODUCT_OUT staging directory, things can get out of sync if different # build configurations are built in the same tree. The following logic # will notice when the configuration has changed and remove the files # necessary to keep things consistent. ---- Do you see prints like "*** Build configuration changed: ..." when you build with a different variant? On Jan 4, 7:27 pm, Pierre <[email protected]> wrote: > Hello, > > some of our developer have put this code in one of our Android.mk > > ifeq ($(TARGET_BUILD_VARIANT),eng) > LOCAL_CFLAGS += -DDEBUG > endif > > if one do: > lunch myboard-eng > make > lunch myboard-userdebug > make > > The result is the the userdebug build still gets the DEBUG binaries in > it. > Rootcause is that my module's object does not depend on the > TARGET_BUILD_VARIANT, so that they are not rebuilt, if I only change > the variant. > > Any idea on how to resolve this issue in an elegant way? > > Pierre -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
