Comments (8)
No. Not yet.
For now you can use https://github.com/tpoechtrager/cctools-port/tree/master/usage_examples/ios_toolchain
Fur future visitors: You can find an explanation on how to setup an iOS toolchain with 64-bit support here and here.
from osxcross.
I am not sure if I should really add iOS support to OSXCross, all the OS ifs, e.g.:
if iOS {
// iOS
} else if OSX {
// OS X
}
are... annoying.
And I am not sure what tools like xcrun
should do by default when both
toolchains are installed, etc. etc..
To the watchers: is there any interest for iOS support in OSXCross? And does
someone of you own a jailbroken iOS ARM64 device who could possibly do some testing?
from osxcross.
If it helps, we need it for doing Godot builds, but not necessarily want to use it for Jailbroken devices. Godot will export an XCode project with the precompiled binaries so actual developers with a mac can build and deploy legally. The problem is that creating those binaries in an automated system that is cloud hosted is impossible due to no (cheap at last) access to macs, which is a problem given we are quite a popular opensource project.
So being able to just build the binaries for OSX and iOS on a regular linux machine would be priceless for us.
from osxcross.
Well, tbh, I have no clue how iOS code signing works, so no idea how to make the binaries run/work on non-jailbroken devices.
Do you need more than what https://github.com/tpoechtrager/cctools-port/tree/master/usage_examples/ios_toolchain provides?
from osxcross.
@reduz there are some instructions here xchain, but it is ancient and unmaintained though.
from osxcross.
I guess this could be closed, as we do cross-compile Godot to iOS from Linux using osxcross. Here's the Dockerfile for our iOS build container: https://github.com/godotengine/build-containers/blob/master/Dockerfile.ios
Do you need more than what https://github.com/tpoechtrager/cctools-port/tree/master/usage_examples/ios_toolchain provides?
That's indeed what we use and it seems to work fine.
from osxcross.
Well, tbh, I have no clue how iOS code signing works, so no idea how to make the binaries run/work on non-jailbroken devices.
Do you need more than what https://github.com/tpoechtrager/cctools-port/tree/master/usage_examples/ios_toolchain provides?
This message is old, but really codesign is unnecessary as long as the binary is otherwise working. Once built code signing can still be managed on a Mac. Building the software in the cloud would be a major win.
from osxcross.
I don't think any of this is needed anymore since clang
and lld
are already cross compilers/linkers. You can cross compile to mac/ios using a recent clang/lld
. As for other stuff you'd want to do like codesigning, notarization and building dmgs, it's all possible from linux using [0]. If you're trying to cross compile rust you might find [1] more convenient, which handles downloading the ios/macos sdks, setting all the correct flags for cargo/rust/clang/lld and then codesigning/notarizing/packaging the result.
- [0] https://github.com/indygreg/apple-platform-rs/tree/main/apple-codesign
- [1] https://github.com/cloudpeers/xbuild
from osxcross.
Related Issues (20)
- Arm64e (more a question than an issue) HOT 1
- Your manual isn't clear... HOT 2
- Minor Documentation Edit -- Tarball doc misses a few packages HOT 1
- Not an issue: osxcross can also be used to cross-compile to macOS using Visual Studio and WSL
- Allow building MacPorts packages.
- gen_sdk_package error in xcode14 HOT 6
- Unpacking XCode CLI Tools 14.2 fails HOT 1
- Building compiler-rt with `build_compiler_rt.sh` fails
- "mv: cannot stat" error on extracting macOS SDK HOT 1
- Using gcc assembler HOT 2
- GCC Built by ./build_gcc.sh o32-gcc and o32-g++ only target x86_64 HOT 1
- Can't pass -Wl,--allow-multiple-definition HOT 3
- osxcross-macports infinite loops when installing install curl-ca-bundle HOT 5
- build_gcc.sh does not install needed prerequisites. HOT 2
- flang support HOT 1
- Add FAQ HOT 3
- error in osxcross build HOT 5
- RFE: macports variants
- stdlib.h missing from xar/lib/linuxattr.c HOT 2
- install_name_tool doesn't adjust ad-hoc code signatures HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from osxcross.