elkpi / libyuv

Automatically exported from code.google.com/p/libyuv
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Even when building for armv7, the output library is with arm64 architecture. #467

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. First use this command :
  GYP_DEFINES="OS=ios target_arch=armv7" GYP_CROSSCOMPILE=1 GYP_GENERATOR_FLAGS="output_dir=out_ios" ./gyp_libyuv -f ninja --depth=. libyuv.gyp 

2. Then, get the Release lib :  ninja -j7 -C out_ios/Release-iphoneos libyuv

3. Go to out_ios -> Release-iphoneos -> libyuv.a

4. Now when we get information about the library using this command : lipo 
-info libyuv.a 

we get, 
input file libyuv.a is not a fat file
Non-fat file: libyuv.a is architecture: arm64

What is the expected output? What do you see instead?
input file libyuv.a is not a fat file
Non-fat file: libyuv.a is architecture: armv7

What version of the product are you using? On what operating system?
Mac OS X Yosemite
libyuv version - 1444

Please provide any additional information below.

Original issue reported on code.google.com by mayurjos...@gmail.com on 15 Jul 2015 at 10:04

GoogleCodeExporter commented 9 years ago
Looking in common.gypi there is a behavior change for arch/subarch to default 
to arm64
Its not well documented, but you can determine the valid setting from this 
snippet:

            # Limit the valid architectures depending on "target_subarch".
            # This need to include the "arm" architectures but also the "x86"
            # ones (they are used when building for the simulator).
            ['target_subarch=="arm32"', {
              'VALID_ARCHS': ['armv7', 'i386'],
            }],
            ['target_subarch=="arm64"', {
              'VALID_ARCHS': ['arm64', 'x86_64'],
            }],
            ['target_subarch=="both"', {
              'VALID_ARCHS': ['arm64', 'armv7', 'x86_64', 'i386'],
            }],

for 32 bit arm
target_arch=armv7
target_subarch=arm32

Original comment by fbarch...@google.com on 15 Jul 2015 at 6:52

GoogleCodeExporter commented 9 years ago
Getting Started updated.  Thanks for the report.

Original comment by fbarch...@google.com on 15 Jul 2015 at 7:01