[Speex-dev] Cross-compiling speex

[Ben Leslie]

Hi Jean-Marc,

That is the exact thing I'm looking for, but it doesn't appear to
exist in speex1.2rc1. Am I missing something?

Thanks,

Benno

On Wed, Oct 21, 2009 at 4:19 AM, Jean-Marc Valin
<jean-marc.valin at usherbrooke.ca> wrote:
> Try adding --without-lobogg to the configure script. Otherwise, just
> ignore the error because the important part (libspeex/) has already been
> built when the error is reported.
>
>        Jean-Marc
>
>
>
> Ben Leslie a écrit :
>> Hi all,
>>
>> I'm cross-compiling speex for a GNU/Linux ARM target.
>>
>> I want to compile only the libraries, and not the speex executables.
>>
>> I don't have a libogg cross-compiled, and would prefer the need to
>> have to set it up.
>>
>> Unfortunately:
>>
>> 1/ the speex executables depend on libogg header files,
>>
>> although, the speex executables are only compiled if the libogg header
>> files are available
>>
>> 2/ the libogg check is only done when cross-compiling
>>
>> 3/ libogg is assume to exist when cross-compiling
>>
>> Obviously it is the third thing here that gets me. I confess to being
>> completely useless
>> with atuo*, so my 'fix' was simply to change #3, so that configure
>> assumed that libogg
>> _did not_ exist when cross-compiling. This is obviously a crappy solution.
>>
>> I think it would be nice if there was a flag to pass to configure
>> which disabled compiling
>> of the binaries explicitly. Unfortunately I don't grok auto* enough to
>> work out how to
>> do this.
>>
>> Finally, my questions:
>>
>> 1/ Am I doing something completely broken/unsupported here?
>>
>> 2/ Is explicitly having a way to not compile the binaries useful/acceptable?
>>
>> 3/ Any pointers on how I would go about implementing that?
>>
>> Thanks,
>>
>> Benno
>> _______________________________________________
>> Speex-dev mailing list
>> Speex-dev at xiph.org
>> http://lists.xiph.org/mailman/listinfo/speex-dev
>>
>>
>