[opus] Help building OPUS library using FIXED_POINT option

Dubois-Rande, Antoine Antoine.Dubois-Rande at nuance.com
Thu Jul 18 11:51:49 PDT 2013

Thanks Ralph, it worked. I also updated our "make_build_config.py" to exclude those files so it correctly generates "build_config.py". We will look into automating this a bit more by parsing your .mk files.


-----Original Message-----
From: Ralph Giles [mailto:giles at thaumas.net] 
Sent: Thursday, July 18, 2013 1:40 PM
To: Dubois-Rande, Antoine
Cc: opus at xiph.org; Robitaille, Marc; Pham, Dan; Xu, Letian
Subject: Re: [opus] Help building OPUS library using FIXED_POINT option

On 13-07-18 8:12 AM, Dubois-Rande, Antoine wrote:

> C:/android/android-ndk-r8e/toolchains/arm-linux-androideabi-4.6/prebui
> lt/windows/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-li
> nux-androideabi/bin/ld.exe: ./obj/local/armeabi/lib0.a(analysis.o): in 
> function
> run_analysis:jni/src/libopus/src/analysis.c:636: error: undefined 
> reference to 'optimize_framesize'

Don't include analysis.c, mlp.c or mlp_data.c in the fixed point build.
Those files are float-only.

I'd recommend parsing *_sources.mk from the source tree and using that to construct your build dictionaries. That way you'll get an accurate source list and not have to track changes to the source file lists manually.


More information about the opus mailing list