search

ericmckean / webm

Automatically exported from code.google.com/p/webm
0 stars 0 forks source link

Support iOS simulator #672

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Build with optimizations for the simulator.

CC'ing a few people who may have some ideas or suggestions about how to go 
about this. Feel free to un-cc yourself if you're not interested.

Original issue reported on code.google.com by johannko...@google.com on 22 Nov 2013 at 9:49

GoogleCodeExporter commented 9 years ago 
Chromium and WebRtc support iOS and simulator builds via GYP.
I've only tried ios, but its basically the same

Native is:
GYP_DEFINES="OS=ios target_arch=armv7" GYP_CROSSCOMPILE=1 
GYP_GENERATOR_FLAGS="output_dir=out_ios" ./build/gyp_chromium -f ninja 
--depth=. libyuv_test.gyp 
ninja -j7 -C out_ios/Debug-iphoneos 
ninja -j7 -C out_ios/Release-iphoneos 

I'd guess simulator is 
GYP_DEFINES="OS=ios"
ninja -j7 -C out_ios/Debug
ninja -j7 -C out_ios/Release

So you could try that and see what it does.

Original comment by fbarch...@google.com on 23 Nov 2013 at 11:07

GoogleCodeExporter commented 9 years ago 
libyuv has a similar issue
https://code.google.com/p/libyuv/issues/detail?id=308

Best to check target_arch or the neon flags.
       [ '(target_arch == "armv7" or 'target_arch == "armv8" or (target_arch == "arm" and arm_version >= 7)) and (arm_neon == 1 or arm_neon_optional == 1))', {

or that its not intel
'target_arch != "ia32"

Original comment by fbarch...@google.com on 5 Feb 2014 at 11:51

GoogleCodeExporter commented 9 years ago 
Tom: in your iOS work, did you run into any issues with the simulator?

Original comment by johannko...@google.com on 6 Nov 2014 at 1:25

GoogleCodeExporter commented 9 years ago 
Um... Why do we think the simulator builds are unoptimized? The sim targets are 
all x86 and x86_64. They just change add ios version stuff to the build 
settings. Otherwise they (_should_ be) identical to normal darwin builds.

Oh, wait... I just typed that and now I see how old the original bug is. Uh, 
anyway, what I said above, but with less confusion. :)

Original comment by tomfine...@google.com on 6 Nov 2014 at 1:36

GoogleCodeExporter commented 9 years ago 
So your ios scripts build a working/optimized simulator library? Then this can 
be closed. Otherwise I'll look into adding iOS targets.

Original comment by johannko...@google.com on 6 Nov 2014 at 1:41

GoogleCodeExporter commented 9 years ago 
Yes, build/make/iosbuild.sh builds framework that includes x86 and x86_64 
simulator targets. They can be build directly using the targets 
x86-iphonesimulator-gcc and x86_64-iphonesimulator-gcc.

Original comment by tomfine...@google.com on 6 Nov 2014 at 1:45

GoogleCodeExporter commented 9 years ago 
Fabulous

Original comment by johannko...@google.com on 6 Nov 2014 at 1:50