libyuv_neon.a library build failed in ios building

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Follow build instructions from getting started.
Exact command lines:
GYP_DEFINES="OS=ios target_arch=arm64 target_subarch=arm64" GYP_CROSSCOMPILE=1 
GYP_GENERATOR_FLAGS="output_dir=out_ios" ./gyp_libyuv
 ninja -j7 -C out_ios/Debug-iphoneos libyuv_unittest
 ninja -j7 -C out_ios/Release-iphoneos libyuv_unittest
2.No error,no warning during the building

What is the expected output? What do you see instead?
library in out_ios/Release-iphoneos/libyuv.a  was build successfully,but 
libyuv_neon.a did not exist.
Error:"ld: library not found for -lyuv_neon" came out While execute 
./configure-iphone with "--with-libyuv=libyuv's directory" option.

What version of the product are you using? On what operating system?
ios 8  mac os 10.10 xcode 6.3.1

Please provide any additional information below.

Original issue reported on code.google.com by libinqua...@gmail.com on 18 Feb 2016 at 3:03

[GoogleCodeExporter]

libyuv_neon.a is not expected... the functions were moved into libyuv.a

Original comment by fbarch...@chromium.org on 18 Feb 2016 at 5:46

[GoogleCodeExporter]

For 64 bit, Neon is always available, so it didnt make sense to have 2 
libraries.

For 32 bit, there are legacy CPUs that never have Neon, but the vast majority 
do. The complexity of having 2 libraries, one built with neon and one without, 
was causing more performance problems than it was solving.  So now the library 
must be built entirely with Neon, or without.
The source code still allows the old way of building, if you want to roll your 
own build files.

Remove libyuv_neon.a from any links you do in your projects.

Original comment by fbarch...@google.com on 19 Feb 2016 at 1:48

• Changed state: Invalid