Question

I am trying to compile GMock from sources for iOS. I want to compile it as an archive so that multiple iOS projects can use it. I am using cmake to build this module (the existing build system uses cmake to build GMock as dylibs, so its easier if I could use the same method). I had to add the following in CMakeLists.txt to build it as an archive.

set(BUILD_SHARED_LIBS OFF)

The archives are created but the problem is some of the tests (in gtest_build_tests) are failing.

The following tests FAILED:
 22 - gtest-filepath_test (SEGFAULT)
 51 - gtest_filter_unittest (Failed)
 54 - gtest_output_test (Failed)
 58 - gtest_xml_outfiles_test (Failed)
 59 - gtest_xml_output_unittest (Failed)
Errors while running CTest

Has anyone successfully built GMock as archive for iOS ?? If so how did you guys do it ?? Also I have to manage the build process from terminal without using Xcode or xcodebuild command.

Thanks, Abhinay

Answer 1

Building GMock for iOS can indeed be a challenge due to the platform s specific requirements. If you re seeing test failures after building as a static library, it could be due to various reasons, including compilation settings, system configurations, or compatibility issues between GMock and the iOS platform.

Here s a general guideline on how you might approach building GMock for iOS from the terminal, making sure you set the right compiler and flags:

Ensure that you have the correct version of iOS SDK installed on your machine. Also, make sure you have Xcode command line tools installed even though you are not using Xcode directly. They provide necessary compilers and libraries for building code for iOS.
While configuring the build with CMake, you need to specify the toolchain file for the iOS platform. Here is an example of how you might set up the command:

cmake -H. -Bbuild -DCMAKE_TOOLCHAIN_FILE=/path/to/ios-cmake/toolchain.cmake -DIOS_PLATFORM=OS

Replace /path/to/ios-cmake/toolchain.cmake with the actual path to your iOS toolchain file. This toolchain file is responsible for setting up the right environment for iOS build.

After configuration, start the build process using the following command:

cmake --build build --config Release

Remember that in this process, you are not only compiling GMock but also its dependency GoogleTest. If GoogleTest has any issues with the iOS platform, they might be the cause of your test failures.

If the test failures persist after following these steps, try to dig into the failure messages more. This could provide clues about what s causing the issues. Maybe there s a need for a patch to the source code, or there might be missing or incorrect flags in your build process.

Also, make sure you re using a version of GMock that s compatible with your iOS version. It might be helpful to check the GMock s issue tracker and user groups to see if others have encountered similar problems, as they might have found a solution or workaround.

Please note that the toolchain file can usually be found in a package like ios-cmake, which provides a toolchain file specifically tailored to iOS builds. You might need to download and install such a package if you haven t done so already.

Remember that GMock is primarily designed and tested for desktop platforms. While it usually works on mobile platforms like iOS, there can be unforeseen compatibility issues. If you continue encountering problems, it might be worth considering other testing frameworks that are explicitly designed to support iOS.

友情链接