Note: This repository is no longer (or barely) maintained, as I am currently developing a native Swift alternative. While Avalonia is a powerful framework, it tends to cause excessive resource usage on macOS, leading to performance issues. That said, you are still welcome to use this project, everything should continue to function unless affected by future platform or dependency updates.
Powered by Avalonia UI and CUE4Parse
To build FortnitePorting from source, first clone the repository and all of its submodules.
git clone -b v3 https://github.com/iFloneUEFN/FortnitePortingMac --recursive
Then open the project directory in a terminal window and publish
For Mac Intel:
dotnet publish FortnitePorting -c Release --no-self-contained -r osx-x64 -o "./Release" -p:PublishSingleFile=true -p:DebugType=None -p:DebugSymbols=false -p:IncludeNativeLibrariesForSelfExtract=true
For Mac Apple Silicon:
dotnet publish FortnitePorting -c Release --no-self-contained -r osx-arm64 -o "./Release" -p:PublishSingleFile=true -p:DebugType=None -p:DebugSymbols=false -p:IncludeNativeLibrariesForSelfExtract=true
It is recommended to make a new folder in /Applications and put the .app in there to not encounter any permission issues further.
If you plan on making your own releases/fork, before releasing make sure you follow all those steps below:
Make sure to tell people to repair the damaged .app by using this command in a terminal window where <path_to_the_app> is the .app path:
xattr -c <path_to_the_app>
To mac an universal binary (so both Intel/Apple Silicon are compatible):
lipo -create \
/Users/<yourname>/Downloads/FortnitePortingX86 \
/Users/<yourname>/Downloads/FortnitePortingArm \
-output /Users/<yourname>/Downloads/FortnitePorting_Universal
You would also need to do that for dylib if necessary. To check if a dylib/executable is universal, you can use the command below in a terminal window:
file <path>