Databases
StackOverflow2013
Postsdbo
PO
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You're missing a few steps. First of all you don't want to build the frontend at all since you'll only be able to use LAME as a library anyhow. You also have to build the library statically otherwise you won't be able to build it into your project.</p> <p>Basically, you have to setup the source tree and compile it four times, once for the simulator (i686), iPhone (armv6), iPad (armv7) and iPhone 5 (armv7s) then lipo the .a files together into a universal library. The Xcode linker will sort everything else out for you when you compile the rest of your project.</p> <p>I used this shell script to build a universal libmp3lame.a file. Note this uses Xcode 4.3 paths and iOS 5.1 compilers.</p> <pre><code>#!/bin/bash SDK_VERSION="5.1" mkdir build function build_lame() { make distclean ./configure \ CFLAGS="-isysroot /Applications/Xcode.app/Contents/Developer/Platforms/${SDK}.platform/Developer/SDKs/${SDK}${SDK_VERSION}.sdk" \ CC="/Applications/Xcode.app/Contents/Developer/Platforms/${SDK}.platform/Developer/usr/bin/gcc -arch ${PLATFORM}" \ --prefix=/Users/mcrute/Desktop/lame \ --host="arm-apple-darwin9" \ --disable-shared \ --enable-static \ --disable-decoder \ --disable-frontend make cp "libmp3lame/.libs/libmp3lame.a" "build/libmp3lame-${PLATFORM}.a" } PLATFORM="i686" SDK="iPhoneSimulator" build_lame PLATFORM="armv6" SDK="iPhoneOS" build_lame PLATFORM="armv7" build_lame PLATFORM="armv7s" build_lame lipo -create build/* -output build/libmp3lame.a </code></pre> <p>Take the libmp3lame.a file from ./build along with the lame.h file from the include directory and drop them in your Xcode project and you should be ready to use lame in either the simulator or a real device.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload