Remove the unused ENABLE_BITCODE xcconfig, which cause issue for watchOS platform. Even without this xcconfig, all 4 platforms build product have the correct bitcode support

This commit is contained in:
DreamPiggy 2019-03-27 22:07:42 +08:00
parent 110b49633f
commit c292fcccc4
4 changed files with 0 additions and 14 deletions

View File

@ -6,6 +6,3 @@
// If enabled, only the active architecture is built. // If enabled, only the active architecture is built.
ONLY_ACTIVE_ARCH = YES ONLY_ACTIVE_ARCH = YES
// Activating this setting indicates that the target or project should generate bitcode during compilation for platforms and architectures that support it. For Archive builds, bitcode will be generated in the linked binary for submission to the App Store. For other builds, the compiler and linker will check whether the code complies with the requirements for bitcode generation, but will not generate actual bitcode.
ENABLE_BITCODE = NO

View File

@ -15,9 +15,6 @@ ENABLE_NS_ASSERTIONS = YES
// When this setting is activated, the product will be built with options appropriate for running automated tests, such as making private interfaces accessible to the tests. // When this setting is activated, the product will be built with options appropriate for running automated tests, such as making private interfaces accessible to the tests.
ENABLE_TESTABILITY = YES ENABLE_TESTABILITY = YES
// Activating this setting indicates that the target or project should generate bitcode during compilation for platforms and architectures that support it. For Archive builds, bitcode will be generated in the linked binary for submission to the App Store. For other builds, the compiler and linker will check whether the code complies with the requirements for bitcode generation, but will not generate actual bitcode.
ENABLE_BITCODE = NO
// Specifies the degree to which the generated code is optimized for speed and binary size. // Specifies the degree to which the generated code is optimized for speed and binary size.
GCC_OPTIMIZATION_LEVEL = 0 GCC_OPTIMIZATION_LEVEL = 0

View File

@ -109,11 +109,6 @@ DYLIB_CURRENT_VERSION = 1
// Sets the base value for the internal `install path` (`LC_ID_DYLIB`) in a dynamic library. This will be combined with the `EXECUTABLE_PATH` to form the full install path. // Sets the base value for the internal `install path` (`LC_ID_DYLIB`) in a dynamic library. This will be combined with the `EXECUTABLE_PATH` to form the full install path.
DYLIB_INSTALL_NAME_BASE = @rpath DYLIB_INSTALL_NAME_BASE = @rpath
// Activating this setting indicates that the target or project should generate bitcode during compilation for platforms and architectures that support it. For Archive builds, bitcode will be generated in the linked binary for submission to the App Store. For other builds, the compiler and linker will check whether the code complies with the requirements for bitcode generation, but will not generate actual bitcode.
ENABLE_BITCODE = YES
// Mac OS X does not support bitcode.
ENABLE_BITCODE[sdk=macosx*] = NO
// Controls whether `objc_msgSend` calls must be cast to the appropriate function pointer type before being called. // Controls whether `objc_msgSend` calls must be cast to the appropriate function pointer type before being called.
ENABLE_STRICT_OBJC_MSGSEND = YES ENABLE_STRICT_OBJC_MSGSEND = YES

View File

@ -6,6 +6,3 @@
// If enabled, only the active architecture is built. // If enabled, only the active architecture is built.
ONLY_ACTIVE_ARCH = YES ONLY_ACTIVE_ARCH = YES
// Activating this setting indicates that the target or project should generate bitcode during compilation for platforms and architectures that support it. For Archive builds, bitcode will be generated in the linked binary for submission to the App Store. For other builds, the compiler and linker will check whether the code complies with the requirements for bitcode generation, but will not generate actual bitcode.
ENABLE_BITCODE = NO