lukeweber
commented
11 years ago I've done a first pass and gotten an xcode project to be generated for IOS.
It's still a ways from compiling, but you can mess around with it but running this command, and then opening up the xcode project.
./build/gyp_chromium --depth=. -DOS=ios -Dtarget_arch=arm -Dinclude_tests=0 -Denable_protobuf=0 -Denable_video=0 webrtcjingle.gyp
Refactor codebase to support an IPhone build.
voice-client-core/jni/tuenti/ is mostly the client core, which could be reused as an interface on IPhone as well.
Android specific files in tuenti directory that would need to be moved, probably up to jni voice-client-core/jni/tuenti/helpers.cc voice-client-core/jni/tuenti/threadpriorityhandler.cc
General movement might be: voice-client-core/jni/tuenti/ => /src or /core voice-client-core => android/core (Have to think about this a bit more as we have (voice-client-aidl, voice-client-example) new directory iphone/core? (Not sure if we'll even need this new directory iphone/example
./tools/ => Probably we would create additional tools to build iphone here, and rename others to make it clear they're for android.
Please comment if anyone has an idea how this should be managed.