By the way, many of the .c files need to be compiled as .cpp.
For the ARM build, the Android.mk has
   LOCAL_CFLAGS += -x c++
which forces this.

On Dec 26 2010, 7:49 pm, Glenn Kasten <[email protected]> wrote:
> I am not aware of any ARM architecture assumptions, but I also have
> not tried building for other architectures such as x86. It sounds like
> the problem may be due to compiler toolchain version rather than the
> target architecture. If you do see any ARM architecture dependencies,
> please post here.
>
> On Dec 25, 8:20 pm, Oliver <[email protected]> wrote:
>
> > Hello. The link error is due to an compiler incompatible issue. I
> > encountered this problem when i use arm-eabi-gcc 4.2.1 to compile
> > gingerbread. When I switched my toolchain to arm-eabi-gcc 4.4.3. The
> > error went away.
>
> > On 12月26日, 上午5时20分, Bruce Beare <[email protected]> wrote:
>
> > > diff --git a/opensles/libopensles/Android.mk b/opensles/libopensles/
> > > Android.mk
> > > index 64e9b6f..f965d3e 100644
> > > --- a/opensles/libopensles/Android.mk
> > > +++ b/opensles/libopensles/Android.mk
> > > @@ -56,7 +56,7 @@ LOCAL_SRC_FILES:=                     \
> > >          CEngine.c                     \
> > >          COutputMix.c                  \
> > >          IAndroidConfiguration.c       \
> > > -        IAndroidEffect.c              \
> > > +        IAndroidEffect.cpp            \
> > >          IAndroidEffectCapabilities.c  \
> > >          IAndroidEffectSend.c          \
> > >          IBassBoost.c                  \
>
> > > On Dec 23, 6:36 pm, wallace <[email protected]> wrote:
>
> > > > I have encountered the same problem, waiting for solution.
>
> > > > On 12月24日, 上午5时19分, Bruce Beare <[email protected]> wrote:
>
> > > > > I'm having a bit of trouble building opensles for x86. According to
> > > > > some web searches... this is likely due to declaring but not defining
> > > > > a virtual function. From the messages (below), I am guessing that it
> > > > > has something to do with the SortedVector class. I suspect that it's
> > > > > actually something to do with KeyedVector since that is used in
> > > > > IAndroidEffect.
>
> > > > > out/target/product/generic_x86/obj/SHARED_LIBRARIES/
> > > > > libOpenSLES_intermediates/IAndroidEffect.o:
>
> > > > > (.data.rel.ro._ZTIN7android12SortedVectorINS_16key_value_pair_tImPNS_11Audi
> > > > >  -oEffectEEEEE
> > > > >     [typeinfo for
> > > > > android::SortedVector<android::key_value_pair_t<unsigned long,
> > > > > android::AudioEffect*> >]+0x0):
> > > > >    undefined reference to `vtable for
> > > > > __cxxabiv1::__vmi_class_type_info'
>
> > > > > out/target/product/generic_x86/obj/SHARED_LIBRARIES/
> > > > > libOpenSLES_intermediates/IAndroidEffect.o:
>
> > > > > (.data.rel.ro._ZTIN7android12SortedVectorINS_16key_value_pair_tImPNS_11Audi
> > > > >  -oEffectEEEEE
> > > > >     [typeinfo for
> > > > > android::SortedVector<android::key_value_pair_t<unsigned long,
> > > > > android::AudioEffect*> >]+0x10):
> > > > >    undefined reference to `typeinfo for android::SortedVectorImpl'
>
> > > > > I don't know why this isn't an issue for the ARM builds... /me shrug
> > > > > Anyone know what's going on here?
>
> > > > > Thanks,
> > > > > Bruce- Hide quoted text -
>
> > > > - Show quoted text -

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to