I’m using mingw-w64 to build Windows binaries and OSX Cross to build for OSX. The 64 bit Linux also runs first as it is the only build that will run the reflection preprocessor and other build time custom tools that generate code.

The 64 bit Linux build doesn’t need a toolchain file since the system is 64 bit and is configured to build by default using Clang 3.8. Bbuild/win32 -G Ninja -DCMAKE_BUILD_TYPE =Debug -DCMAKE_TOOLCHAIN_FILE =cmake/i686-w64-mingw32.cmakeĮach build, a part from the 64 bit Linux, has a toolchain file associated with it that specifies the compiler to use and the path to libraries and headers. Bbuild/linux32 -G Ninja -DCMAKE_BUILD_TYPE =Debug -DCMAKE_TOOLCHAIN_FILE =cmake/i686-linux.cmakeĬmake -H. Bbuild/win64 -G Ninja -DCMAKE_BUILD_TYPE =Debug -DCMAKE_TOOLCHAIN_FILE =cmake/x86_64-w64-mingw32.cmakeįi # 32 bit builds if thenĬFLAGS = -m32 CXXFLAGS = -m32 cmake -H. Bbuild/osx -G Ninja -DCMAKE_BUILD_TYPE =Debug -DCMAKE_TOOLCHAIN_FILE =cmake/x86_64-osx.cmakeĬmake -H. Bbuild/linu圆4 -G Ninja -DCMAKE_BUILD_TYPE =DebugĬmake -H. The setup step, that is run only once after a clean git clone, initializes Cmake for the 5 “platforms” like so: # 64 bit builds if thenĬmake -H. The cross compilation process is handled by a simple bash script. The build “server” is Mac Mini running a bare bones installation of Arch Linux. Whenever I push commits to the Github repository, an automated build triggers for the three platforms that Rival Fortress will ship on: Windows (32/64bits), Linux (32/64bits) and OSX(64bits). How did I ever get by without a tiling window manager!įanboyism aside, this week I finally finished the cross compiling setup that I started working on a while back. I’m in love! Linux is giving me even more freedom from clutter and OS annoyances than what OSX was giving me. I’ve moved permanently to Linux as my development platform.

Cross compile for mac on linux