Package Details: apple-darwin-osxcross 325.16efae8-1

Package Base: apple-darwin-osxcross
Description: OS X cross toolchain for Linux, FreeBSD and NetBSD
Upstream URL:
Licenses: MIT
Conflicts: osxcross
Provides: osxcross
Submitter: Martchus
Maintainer: Martchus
Last Packager: Martchus
Votes: 4
Popularity: 0.000321
First Submitted: 2017-08-09 20:29
Last Updated: 2019-08-05 19:32

Dependencies (10)

Required by (1)

Sources (4)

Latest Comments

Martchus commented on 2019-08-05 19:58

I have updated this to a later commit and the MacOSX SDK 10.13. This was the latest SDK I was able to find. Updating the SDK is likely necessary to build the latest version of Qt.

I did not find any place which allows one to download XCode without Apple login. So instead of running the packaging scripts of osxcross I'm just copying over the header files from the libc++ package. I hope this breaks not everything.

Because I haven't had a good experience with it I removed the GCC build. Providing GCC as a separate package would make more sense anyways.

So far I only tested my simple c++utilities library which is using CMake and C++17. It worked quite well beside having to disable features relying on std::filesystem.

Like in the previous version executables are located under /opt/osxcross/bin. Additionally, it now uses dynamic libraries so one also needs to make sure finds them. The following exports should do it:

export PATH="/opt/osxcross/bin:$PATH"
export LD_LIBRARY_PATH="/opt/osxcross/lib"

Martchus commented on 2019-08-02 21:35

Because the package has been flagged: There are still TODOs that I haven't tackled yet:

But since my Syncthing Tray application saw some Mac OS fixes lately I'm actually looking forward to proceed with that apple-darwin packages. It will just take a little bit more time.

Martchus commented on 2019-05-23 13:46

I honestly can't remember that I filed the request but maybe I have. The idea was likely to rename the package. But yes, that doesn't make too much sense because as you say - those are different packages (on for the latest release and one for the Git master).

Speaking of names: It would still make sense to use a consistent prefix for those cross-compilation packages. For instance Android packages use android-$arch- and mingw-w64 packages use mingw-w64-. I propose to use apple-darwin- for Mac OS but maybe you have a better suggestion.

But I lost the motivation to work on Mac OS cross compilation anyways. I even managed to cross compile a static build of Qt 5 and link my own applications against it. However, I have no Mac OS system to debug runtime issues so the effort was quite pointless after all.

I merely got some experience and came to the conclusion that the packaging still needs to be improved to be useful:

emersion commented on 2019-05-23 13:29


You filled a merge request for osxcross-git. Sorry, this isn't how it works: creating a new package and requesting the deletion of the same one is not productive. Instead send patches there to improve the PKGBUILD.

Additionally, this isn't a -git package. Both packages (pinned and -git) are useful, merging those won't allow users to track the Git repo anymore.

net147 commented on 2018-07-24 11:37

$ makepkg


Martchus commented on 2017-08-11 14:13


There also exist a binary repository: