opus - May 2016 - Opus library build for decode only?

Hi all,

I would like a makefile or makefile option which excludes the encode source 
code from the Opus build.

The reason I want this is that I am developing an embedded application which 
requires decoding Opus but not encoding.  A decode-only build should be 
much smaller than a full Opus build, which is an important consideration 
for resource-limited platforms.

As someone pointed out on IRC, it's possible to link the application with 
the static library and (using gcc tools) discard most of the unreferenced 
object files.  However, the application needs to build cross platform (for 
example, iOS and Android).

If anyone has thoughts or has worked on this, could you please let me know?

Thank you!

-Ross

Hello Ross

I am using static library on an eclipse based compiler. The size of the decoder
( minus the file io) is approximately 100kb. The linker removed the unused code
when the option is set. Should be the case on gcc as well

Regards
Amit Ashara
> On May 12, 2016, at 11:29 AM, Ross Wille <opus at cornerbrick.com>
wrote:
> 
> Hi all,
> 
> I would like a makefile or makefile option which excludes the encode source
> code from the Opus build.
> 
> The reason I want this is that I am developing an embedded application
which
> requires decoding Opus but not encoding.  A decode-only build should be 
> much smaller than a full Opus build, which is an important consideration 
> for resource-limited platforms.
> 
> As someone pointed out on IRC, it's possible to link the application
with
> the static library and (using gcc tools) discard most of the unreferenced 
> object files.  However, the application needs to build cross platform (for 
> example, iOS and Android).
> 
> If anyone has thoughts or has worked on this, could you please let me know?
> 
> Thank you!
> 
> -Ross
> _______________________________________________
> opus mailing list
> opus at xiph.org
> http://lists.xiph.org/mailman/listinfo/opus