ios-cmake
ios-cmake copied to clipboard
leetal
A CMake toolchain file for iOS/iPadOS, visionOS, macOS, watchOS & tvOS C/C++/Obj-C++ development
**Describe the bug** When building SDL2 the process will fail due to CMake seeing the host system iconv lib, and then failing to find a proper lib to link with...
**Describe the bug** When i use -DPLATFORM=OS64COMBINED and generate Xcode project, it only create the project with BASE SDK equal iOS. **To Reproduce** Steps to reproduce the behavior: `cmake -B...
**Describe the bug** Sets ENABLE_STRICT_TRY_COMPILE `OFF` default, will lead cmake generate incorrect native project for dynamic libraries. **To Reproduce** Steps to reproduce the behavior: 1. https://github.com/axys1/axys/runs/8269974724?check_suite_focus=true 2. **Expected behavior** Generate...
**Describe the bug** The [README](https://github.com/leetal/ios-cmake/blame/master/README.md#L34) file states the `OS64COMBINED` flag builds a fat lib including `iphoneOS` and `iphoneOS Simulator`, but in the [toolchain file](https://github.com/leetal/ios-cmake/blob/master/ios.toolchain.cmake#L61) the statement is completely different. **To...
I have tweaked the CMakeLists.txt from the example in order to link to OpenCV. This seems to work for ios and mac. I can run the toy code on the...
**Describe the bug** When building the example library with PLATFORM=OS64COMBINED, a binary containing only arm64 is produced. I was also unable to manually persuade Xcode to build a fat archive...
Hi, Im trying build for mac catalyst with x86_64 arch, but it "understand" that is for macOS: ``` cmake -S . -B /Users/paulo/Developer/workspaces/cpp/xplpc/build/swift-ios/mac-catalyst/x86_64 -GXcode -DCMAKE_TOOLCHAIN_FILE=/Users/paulo/Developer/workspaces/cpp/xplpc/cmake/ios.toolchain.cmake -DCMAKE_BUILD_TYPE=Release -DXPLPC_TARGET=swift -DXPLPC_ADD_CUSTOM_DATA=ON -DXPLPC_DEPENDENCY_TOOL=conan -DXPLPC_TARGET_GROUP=mac-catalyst...
Resolves #146. This seems like an optimisation (it should be fine, though suboptimal, to sometimes run the toolchain twice) that breaks some use-cases (different people complained in #146). I therefore...
