Author Topic: HOW TO build Wineskin engines on El Capitan  (Read 4921 times)

Offline Brainzyy

  • Global Moderator
  • Porter
  • *****
  • Posts: 94
HOW TO build Wineskin engines on El Capitan
« on: September 03, 2016, 05:54:23 PM »

Building Wineskin (32bit only) engines on OS X El Capitan.


- Wineskin Winery (latest version) installed.
- Latest Wrapper version
- Latest Master Engine version
- Xcode installed (latest 7.x version for El Capitan)
- Latest Xcode command line tools installed (for Xcode 7.x)
- Agreed to the Xcode TOS (go to Terminal and type "sudo xcodebuild -license")
- Ran Xcode at least once
- Downloaded the wine source that you want to use to create your engine

Preparing Xcode:

Step 1: Download the OS X 10.6 and OS X 10.8 SDK's and unzip them
Step 2: Right-click Xcode and select "Show Package Contents"
Step 3: Go to "Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs" and put the unzipped 10.6 and 10.8 SDK folder in there
Step 4: Go back to the "MacOSX.platform" folder and open info.plist in a text editor
Step 5: Use CMD + F and find the line where it says "MinimumSDK" and replace 10.11 with 10.6 and save the file

Disabling SIP:

Step 1: Boot up your mac while holding down CMD + R.
Step 2: Once you have booted into your recovery partition, click on "Utilities" from the menu at the top of the screen
Step 3: Select "Terminal"
Step 4: In the Terminal window type in "sudo csrutil disable" and press enter.
Step 5: Type in "reboot" and press enter, your mac will now reboot into your normal Mac OS X partition

Building the engine:

Step 1: Open Wineskin Winery and click and the + button
Step 2: Select "Custom Build and Engine"
Step 3: Browse to your wine source folder and select it
Step 4: (VERY IMPORTANT) Make sure that where it says "Minimum OS Version" that you put it to 10.6
Step 5: Type in a name for you engine and press "Build!"

It could be that there are some instructions in the Terminal window to install gcc if you've never built an engine before.
Just follow the instructions on the screen and everything will be alright.

(Pictures can be added later if needed)

DISCLAIMER: I am not responsible for any damage done by disabling SIP. Disabling SIP allows Administrators on your system to modify system files that they otherwise would not have been able to. I have done this numerous times and nothing bad has happened. If you want, you can enable SIP again by rebooting while holding CMD+R and typing in the Terminal window "csrutil enable".
« Last Edit: September 04, 2016, 02:45:31 PM by Brainzyy »