This is an NDK question, so I suggest taking it to the NDK group, not here.
groups.google.com/group/android-ndk Doug On Friday, June 15, 2012 2:26:03 AM UTC-7, WebShaker wrote: > > Hi. > > I've just bought an Intel Android smartphone ! > > I've change My Application.mk to add a plateforme > > APP_ABI := armeabi armeabi-v7a x86 > > And that works for Java a C code source. > > But I have a assembly file too. > For ARM I used to compile it whit some options > > Here is my Android.mk > > LOCAL_MODULE := engine > LOCAL_ARM_MODE := arm > LOCAL_CFLAGS := -mfpu=neon -march=armv6t2 -O9 > LOCAL_SRC_FILES := engine-arm.s > LOCAL_LDLIBS := -lm -llog -ljnigraphics > LOCAL_STATIC_LIBRARIES := cpufeatures > > Well now My problem is that I have another assembly file for the x86 > called "engine-x68.s" > > What I'd like to do is compiling it with some gcc options > -msse2 -m32 -masm=intel > > So My Android.mk file should be something like > > LOCAL_MODULE := engine > LOCAL_CFLAGS := -msse2 -m32 -masm=intel > LOCAL_SRC_FILES := engine-x86.s > LOCAL_LDLIBS := -lm -llog -ljnigraphics > LOCAL_STATIC_LIBRARIES := cpufeatures > > Finally my question is. > > How Can I compile engine-arm.s with the first Android.mk param and > compile engine-x68.s with the second one ? > My goal is to have only one module (engine) and let Android loading > the correct library ! -- 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
