Installing DeSmuME from source on OS X

From DeSmuME
(Difference between revisions)
Jump to: navigation, search
(Build Compatibility)
m
(17 intermediate revisions by one user not shown)
Line 1: Line 1:
 
== About the Build Targets ==
 
== About the Build Targets ==
DeSmuME for OS X may be built using several different configurations. Each build configuration is listed in an Xcode project as a "build target." The Xcode project files (provided with the DeSmuME source,) provide several build targets to suit your needs. Many build targets are similar to each other, and so they have been organized into the following categories, based on what the build target produces.
+
DeSmuME for OS X may be built using several different configurations. Each build configuration is listed in an Xcode project as a "build target." The Xcode project files, provided with the DeSmuME source code, include several build targets to suit your needs. Many build targets are similar to each other, and so they have been organized into the following categories, based on what the build target produces.
  
  
Line 12: Line 12:
  
 
'''Advantages:'''
 
'''Advantages:'''
* Can be built on machines running OS X v10.5 or later, and Xcode 3.1.4 or later.
+
* Can be built on machines running OS X v10.5 or later, and Xcode v3.1.4 or later.
 
* Binaries can be configured to run in debug mode or in release mode.
 
* Binaries can be configured to run in debug mode or in release mode.
 
* Binaries can be configured for PowerPC or Intel compatibility.
 
* Binaries can be configured for PowerPC or Intel compatibility.
Line 21: Line 21:
  
  
=== OS X App (Final Release) ===
+
=== OS X App (dev+) ===
There is only one build target of this kind, and is only used for final release builds. It also produces an app bundle like the usual debug-and-test builds, but has the widest compatibility of all the builds.
+
This build target is just like the normal OS X App build, except it enables additional debugging features, such as the GDB remote stub. This build is meant for developer usage.
  
 
'''Build Target Goals:'''
 
'''Build Target Goals:'''
* Fully featured.
+
* Fully featured, and includes additional debugging features.
* Widest binary compatibility.
+
* Must be compatible with the latest version of Xcode running on the latest version of OS X.
* Fastest performance.
+
* Quick debug-and-test of code changes.
  
 
'''Advantages:'''
 
'''Advantages:'''
* Produces the fastest running binaries compared to all other build targets.
+
* Can be built on machines running Xcode v4.6.3 or later.
* Produces a universal binary that supports both 32-bit and 64-bit.
+
* Binaries can be configured to run in debug mode or in release mode.
 +
* Building the app is faster than the final release build.
  
 
'''Disadvantages:'''
 
'''Disadvantages:'''
* Must be built on a machine running the latest version of OS X and Xcode.
+
* Must be built on a machine running OS X v10.7 or later.
* Building the app for release takes more steps than other builds.
+
* Due to the additional debugging features, performance will be slightly lower compared to the other builds.
* Requires Xcode 3 to build.
+
  
  
=== OS X App (Legacy) ===
+
=== OS X App (Xcode 6 .XIB for v10.5 Leopard Release Build) ===
These build targets produce a self-contained OS X application package that uses our legacy OS X frontend to run the DeSmuME emulator. These build targets are deprecated, but continue to exist for historical reasons, and also for people who need an app bundle that can run on OS X v10.4.
+
This build target is a helper build target for producing final release builds of DeSmuME. It is used solely as an intermediate build step, and is not intended for normal usage. See [[#OS_X_App_Build_for_Final_Release]] for more details.
 +
 
 +
 
 +
=== OS X App (v10.5 Leopard Release Build) ===
 +
This build target is for producing final release builds of DeSmuME. These builds will use our official OS X frontend contained in an OS X app bundle, and are tuned for the fastest possible performance and the widest binary and OS compatibility.
  
 
'''Build Target Goals:'''
 
'''Build Target Goals:'''
* Binary compatibility with OS X v10.4.
+
* Fully featured.
* Retain legacy code for historical reference.
+
* Widest binary compatibility.
 +
* Widest OS compatibility.
 +
* Fastest performance.
  
 
'''Advantages:'''
 
'''Advantages:'''
* Can be built on machines running OS X v10.5 or later.
+
* Produces the fastest running binaries compared to all other build targets.
* The build app is backwards compatible with OS X v10.4.
+
* Produces a universal binary that supports both 32-bit and 64-bit.
* Binaries can be configured for PowerPC or Intel compatibility.
+
* Binaries are compatible with OS X v10.5 and later.
  
 
'''Disadvantages:'''
 
'''Disadvantages:'''
* These builds are deprecated. We no longer do any active development work on the legacy code.
+
* Must be built on a machine running the latest version of OS X and Xcode.
* Built applications use the legacy user interface, which does not expose all of DeSmuME's current features to the user.
+
* Building the app for release takes more steps than other builds.
* Requires Xcode 3 to build.
+
* Requires a separate Mac or virtual machine running OS X Mavericks in order to run Xcode v3.2.6 and Xcode v6.2 for the intermediate build steps.
* Produces the slowest running binaries compared to all other build targets.
+
  
  
Line 63: Line 68:
 
'''Build Target Goals:'''
 
'''Build Target Goals:'''
 
* Compatibility with OpenEmu.
 
* Compatibility with OpenEmu.
* Proving good code modularity in the source.
+
* Proving that the core source code is modular enough to be integrated with third-party frontends.
  
 
'''Advantages:'''
 
'''Advantages:'''
 
* Compatible with OpenEmu.
 
* Compatible with OpenEmu.
* Built plug-ins are much smaller in size than full application builds.
+
* Plug-ins are much smaller in size compared to full application builds.
  
 
'''Disadvantages:'''
 
'''Disadvantages:'''
* Must be built on a machine running OS X v10.7 or later.
+
* Must be built on a machine running OS X v10.11 or later.
* Binaries only run on machines with 64-bit Intel processors running OS X v10.7 or later.
+
* Binaries only run on machines with 64-bit Intel processors running OS X v10.11 or later.
 
* The frontend is handled by a third-party application, which will not expose all of DeSmuME's features to the user.
 
* The frontend is handled by a third-party application, which will not expose all of DeSmuME's features to the user.
 +
  
 
== Set Up the Build Environment ==
 
== Set Up the Build Environment ==
All DeSmuME build targets must be built using Apple's Xcode IDE. The Xcode project files, included in the desmume/src/cocoa directory of the source code, are supported for the following versions of Xcode:
+
All DeSmuME build targets must be built using Apple's Xcode IDE. The Xcode project files, included in the "desmume/src/frontend/cocoa" folder of the source code, are supported for the following versions of Xcode:
  
 
{| class="wikitable" style="text-align: center;"
 
{| class="wikitable" style="text-align: center;"
Line 84: Line 90:
 
| v3.1.4 (if running on Leopard); v3.2.6 (if running on Snow Leopard or later)
 
| v3.1.4 (if running on Leopard); v3.2.6 (if running on Snow Leopard or later)
 
|-
 
|-
| DeSmuME (Xcode 4).xcodeproj
+
| DeSmuME (Latest).xcodeproj
| v4.3 or later
+
| v4.6.3 or later
|-
+
| DeSmuME (Legacy).xcodeproj
+
| v3.1.4 (if running on Leopard); v3.2.6 (if running on Snow Leopard or later)
+
 
|}
 
|}
  
Line 97: Line 100:
 
You must use Xcode 3 if any of the following conditions apply:
 
You must use Xcode 3 if any of the following conditions apply:
 
* You are running OS X v10.5 or v10.6.
 
* You are running OS X v10.5 or v10.6.
* You are building a Legacy OS X App (can be configured to run on OS X v10.4).
 
 
* You are building an OS X App that runs on OS X v10.5.
 
* You are building an OS X App that runs on OS X v10.5.
 
* You are building an OS X App that runs on PowerPC processors.
 
* You are building an OS X App that runs on PowerPC processors.
Line 103: Line 105:
  
  
You must use Xcode 4 if any of the following conditions apply:
+
You must use Xcode 4 or later if any of the following conditions apply:
 
* You are running OS X v10.7 or later.
 
* You are running OS X v10.7 or later.
 
* You are building an OpenEmu Plug-in.
 
* You are building an OpenEmu Plug-in.
 
* You are building an OS X App for final release.
 
* You are building an OS X App for final release.
 +
 +
 +
'''Note:''' ''Xcode 3 is not compatible with OS X v10.10 Yosemite. If you require the use of Xcode 3, you will need to run it on an older version of OS X.''
  
  
Line 123: Line 128:
 
* Xcode v3.2.6 Direct Download Link (for Snow Leopard): http://adcdownload.apple.com/Developer_Tools/xcode_3.2.6_and_ios_sdk_4.3__final/xcode_3.2.6_and_ios_sdk_4.3.dmg
 
* Xcode v3.2.6 Direct Download Link (for Snow Leopard): http://adcdownload.apple.com/Developer_Tools/xcode_3.2.6_and_ios_sdk_4.3__final/xcode_3.2.6_and_ios_sdk_4.3.dmg
  
 +
If you will be building a Final Release build, then you also need Xcode 6.
 +
* Xcode v6.2 Direct Download Link (for Mavericks): http://download.developer.apple.com/Developer_Tools/Xcode_6.2/Xcode_6.2.dmg
 +
 +
==== Download the Latest Version of Xcode ====
 +
Downloading the latest version of Xcode is very easy! If you are running Lion or later and have any Apple ID, then you can download Xcode directly from the Mac App Store.
 +
* Xcode Mac App Store Link (for Lion or later): https://itunes.apple.com/us/app/xcode/id497799835?ls=1&mt=12
  
==== Download Xcode 4 ====
 
Downloading Xcode 4 is very easy! If you are running Lion or later and have any Apple ID, then you can download Xcode 4 directly from the Mac App Store.
 
* Xcode 4 Mac App Store Link (for Lion or later): http://itunes.apple.com/us/app/xcode/id497799835?ls=1&mt=12
 
  
 
==== Uninstall Previous Versions of Xcode ====
 
==== Uninstall Previous Versions of Xcode ====
Line 147: Line 155:
  
 
Once the installation list is shown, do the following:
 
Once the installation list is shown, do the following:
* If you are planning on making legacy builds, select the Mac OS X 10.4 SDK.
+
* Unless you are planning on building other software that must run on OS X v10.4, you may deselect the Mac OS X 10.4 SDK. (DeSmuME can only run on OS X v10.5 or later.)
* If you are planning on installing Xcode 4, then deselect the iOS SDK, which is listed under Essentials. Since Xcode 4 already has a newer version of the iOS SDK, installing the version included with Xcode 3 will be a waste of time and disk space.
+
* If you are planning on installing the latest version of Xcode alongside Xcode 3, then deselect "System Tools" and "Essentials > iOS SDK". Since the latest Xcode will already have the newest version of the iOS SDK, installing the version included with Xcode 3 will be a waste of time and disk space.
  
 
Continue the installation as normal and let the installation finish.
 
Continue the installation as normal and let the installation finish.
  
  
==== Set Up Xcode 4 ====
+
==== Set Up the Latest Version of Xcode ====
'''Note:''' ''When you download Xcode from the Mac App Store, Xcode should automatically install itself to the Applications folder once the download is complete. There are no additional steps. Pretty easy, right?''
+
When you download Xcode from the Mac App Store, Xcode should automatically install itself to the Applications folder once the download is complete. There are no additional steps. Pretty easy, right?
 +
 
  
 
== Download the DeSmuME Source Code ==
 
== Download the DeSmuME Source Code ==
The DeSmuME source code is managed using Subversion (SVN) and is hosted on SourceForge. In this section, we describe two of the most common methods for downloading the source code. (In reality, there are many methods for downloading the source code, but those methods are beyond the scope of this document.)
+
The DeSmuME source code is managed using git and is hosted on GitHub.
 +
* DeSmuME "master" Branch Download Link: https://github.com/TASVideos/desmume/archive/master.zip
  
=== Download via SourceForge Web Interface ===
 
These instructions will download the DeSmuME source code from the SourceForge Web Interface using your web browser.
 
  
1. Follow this link to DeSmuME's SourceForge Web Interface: http://desmume.svn.sourceforge.net/viewvc/desmume/
+
== Build the DeSmuME Source ==
 +
Regardless of which build target you will be using, you will need to use one of the Xcode project files provided with the DeSmuME source code. For most cases, you will want to build the latest revision. So from the source code folder, navigate to the "/desmume/src/frontend/cocoa" folder.
  
2. Click "Download GNU tarball" to start the download.
+
There should be two Xcode project files present in this folder:
 +
* DeSmuME (XCode 3).xcodeproj
 +
* DeSmuME (Latest).xcodeproj
  
=== Download via Command Line ===
 
These instructions will download the DeSmuME source code to your desktop.
 
  
1. Open Terminal.app.
+
=== OS X App Build ===
 +
This is the quickest and easiest way to get started with using a pre-release build of DeSmuME.  
  
2. In the command prompt, enter the following exactly as shown:
+
==== Building Using Xcode 3 ====
svn co https://desmume.svn.sourceforge.net/svnroot/desmume ~/Desktop/desmume
+
1. Open the "DeSmuME (XCode 3).xcodeproj" project file using Xcode 3.
'''Note:''' ''If you want to change the destination directory to a directory other than your desktop, change the "~/Desktop/desmume" part to the directory of your choice.''
+
  
3. At this point, the download should start. However, if instead there is a message about an untrusted certificate, enter the following exactly as shown:
+
2. In the Build Target menu (located in the upper-left corner of the project window), under Active Configuration, choose Release.
p
+
  
=== Download via Xcode 4 Organizer ===
+
3. In the Build Target menu, under Active Target, choose one of the four build targets.
These instructions are for Xcode 4 users that wish to use the Organizer for downloading the DeSmuME source code.
+
  
1. Open Xcode.app.
+
4. Choose Build > Build, and then wait for Xcode to finish building the app.
  
2. Choose Window > Organizer.
+
And you're done! The newly built app will be present in the "/desmume/src/frontend/cocoa/build/Release" folder. If you built the app using the "DeSmuME (XCode 3).xcodeproj" project file, then the built app will also include the current git commit number.
  
3. In the Organizer window, click Repositories.
+
==== Building Using the Latest Version of Xcode ====
 +
1. Open the "DeSmuME (Latest).xcodeproj" project file using Xcode.
  
4. In the bottom-left corner, click the + button, then choose Checkout or Clone Repository.
+
2. Choose Product > Scheme > DeSmuME (OS X App).
  
5. In the Location field, enter the following exactly as shown:
+
3. In Xcode, choose Product > Build For > Profiling, and then wait for Xcode to finish building the app.
https://desmume.svn.sourceforge.net/svnroot/desmume
+
  
6. After Xcode confirms that the host is reachable, click Checkout.
+
And you're done! The newly built app will be present in the "/desmume/src/frontend/cocoa/build/Release" folder.
  
7. In the file navigation sheet, choose a folder to save the source code to, then click Checkout.
 
  
== Build the DeSmuME Source ==
+
=== OS X App Dev+ Build ===
Regardless of which build target you will be using, you will need to use one of the Xcode project files provided with the DeSmuME source code. For most cases, you will want to build the latest revision. So from the source code folder, navigate to the "/trunk/desmume/src/cocoa" folder.
+
The steps here are similar to that of the normal OS X App build, but will produce the developer-oriented build instead. In addition, you must be using Xcode 4 or later to make this build.
  
There should be three Xcode project files present in this folder:
+
1. Open the "DeSmuME (Latest).xcodeproj" project file using Xcode.
* DeSmuME (Legacy).xcodeproj
+
* DeSmuME (XCode 3).xcodeproj
+
* DeSmuME (XCode 4).xcodeproj
+
  
 +
2. Choose Product > Scheme > DeSmuME (OS X App, dev+).
  
=== OS X App Build ===
+
''If you want to run dev+ build with Xcode's LLDB debugger:''
This is the quickest and easiest way to get started with using a pre-release build of DeSmuME.
+
  
==== Building Using Xcode 3 ====
+
3a. Click Run. This will build a Debug version of the app, which will automatically launch when finished.
1. Open the "DeSmuME (XCode 3).xcodeproj" project file using Xcode 3.
+
 
 +
And you're done! The newly built app will be present in the "/desmume/src/frontend/cocoa/build/Debug" folder.
 +
 
 +
''If you need to use the dev+ build without running the debugger:''
 +
 
 +
3b. In Xcode, choose Product > Build For > Profiling, and then wait for Xcode to finish building the app. (Note that this build does use program optimizations.)
 +
 
 +
And you're done! The newly built app will be present in the "/desmume/src/frontend/cocoa/build/Release" folder.
 +
 
 +
 
 +
=== OS X App Build for Final Release ===
 +
This is the process that we use for our official release builds. To make this build, you must meet the following requirements:
 +
* You must have both Xcode v3.2.6 and Xcode v6.2 installed on a system running OS X Mavericks v10.9.5.
 +
* You must have the latest version of Xcode running on the latest version of macOS. (At the time of this writing, the latest version of Xcode is v9.1, and the latest version of macOS is 10.13.1.)
 +
 
 +
1. Let's start with building on OS X Mavericks: Open the "DeSmuME (XCode 3).xcodeproj" project file using Xcode 3.
  
 
2. In the Build Target menu (located in the upper-left corner of the project window), under Active Configuration, choose Release.
 
2. In the Build Target menu (located in the upper-left corner of the project window), under Active Configuration, choose Release.
  
3. In the Build Target menu, under Active Target, choose one of the four build targets.
+
3. In the Build Target menu, under Active Target, choose the build target "DeSmuME (OS X App; PowerPC Release Build)".
  
''Note: If you have previously made the OS X App Legacy build, you MUST perform a project clean prior to building the standard OS X App build. To do this, perform steps 3.5 and 3.6.''
+
4. Choose Build > Clean All Targets.
  
3.5. Choose Build > Clean All Targets.
+
5. In the Clean All Targets sheet, check all options, then click Clean, and then wait for the clean process to finish.
  
3.6. If the Clean All Target sheet drops down, check all options, then click Clean.
+
6. Choose Build > Build, and then wait for the build process to finish. This will make a new app called "DeSmuME (PPC).app" in the "/desmume/src/frontend/cocoa/build/Release" folder.
  
4. Choose Build > Build, and then wait for Xcode to finish building the app.
+
7. While still on OS X Mavericks: Open the "DeSmuME (Latest).xcodeproj" project file using Xcode 6.2.
  
And you're done! The newly built app will be present in the "/trunk/desmume/src/cocoa/build/Release" folder.
+
8. Choose Product > Scheme > DeSmuME (OS X App; Xcode 6 .XIB for v10.5 Leopard Release Build).
  
==== Building Using Xcode 4 ====
+
9. Choose Product > Clean, and then wait for the clean process to finish.
1. Open the "DeSmuME (XCode 4).xcodeproj" project file.
+
  
2. Choose Product > Scheme > DeSmuME (OS X App).
+
10. Choose Product > Build, and then wait for the build process to finish. This will make a new app called "DeSmuME (Xcode 6).app" in the "/desmume/src/frontend/cocoa/build/Release" folder.
  
3. Click Run. This will build a Debug version of the app, which will automatically launch when finished.
+
11. Quit both Xcode 3 and Xcode 6 on OS X Mavericks.
  
4. After the app launches, go back to Xcode.
+
12. On the latest macOS: Open the "DeSmuME (Latest).xcodeproj" project file using the latest version of Xcode.
  
5. In Xcode, choose Product > Build For > Archiving.
+
13. Choose Product > Scheme > DeSmuME (OS X App; v10.5 Leopard Release Build).
  
6. Right-click the DeSmuME (Debug) app in the dock, and then choose Options > Show in Finder.
+
14. Choose Product > Clean, and then wait for the clean process to finish.
  
7. In the Finder window that appears, you should be in a folder named "Debug". Right-click the window title (which should read "Debug"), and then choose the "Products" folder underneath it.
+
15. Choose Product > Perform Action > Generate Optimization Profile.
  
8. Wait for Xcode to finish building the app.
+
16. In the Generate Optimization Profile sheet, ensure that Use Run Action is the selected option, and then click Run.
  
9. In the Finder, from the "Products" folder, open the "Release" folder.
+
17. Wait for Xcode to finish building the app. When Xcode finishes, DeSmuME.app will automatically launch.
  
And you're done! The newly built app will be present in the "Release" folder. You may quit the DeSmuME (Debug).app if you want.
+
18. Perform the recommended PGO exercises listed on this page: TBD
  
''Note: You may want to create an alias to this folder so that it is easier to access in the future.''
+
19. After all PGO exercises are complete, quit DeSmuME.app. Xcode should now report that it has generated an optimization profile.
  
 +
20. In Xcode, choose Product > Build For > Profiling, and then wait for Xcode to finish.
  
=== OS X App Build for Final Release ===
+
And you're done! The newly built app will be present in the "/desmume/src/frontend/cocoa/build/Merged Release" folder.
This is the process that we use for our official release builds. To make this build, you must meet the following requirements:
+
* You must have both Xcode 3.2.6 (this specific version) and the latest version of Xcode 4 installed.
+
* You must be running the latest version of OS X. At the time of this writing, the latest version is v10.8 Mountain Lion.
+
  
  
1. Open the "DeSmuME (XCode 3).xcodeproj" project file using Xcode 3.
+
=== OpenEmu Plug-in Build ===
 +
The DeSmuME OpenEmu plug-in is used as an extension to the OpenEmu application. Installing the plug-in involves building OpenEmuBase.framework from source, then moving the framework to the "desmume/src/frontend/cocoa/openemu" folder, then building the plug-in from source, and then finally placing the plug-in into the ~/Library/Application Support/OpenEmu/Cores folder.
  
2. In the Build Target menu (located in the upper-left corner of the project window), under Active Configuration, choose Release.
 
  
3. In the Build Target menu, under Active Target, choose the build target "DeSmuME (OS X App; PowerPC; LLVM-Clang)".
+
You can download the OpenEmu SDK source code from here:
 +
* OpenEmu SDK Download Link: https://github.com/OpenEmu/OpenEmu-SDK/archive/master.zip
  
''Note: If you have previously made the OS X App Legacy build, you MUST perform a project clean prior to building the standard OS X App build. To do this, perform steps 3.5 and 3.6.''
 
  
3.5. Choose Build > Clean All Targets.
+
==== Building and installing OpenEmuBase.framework from source ====
 +
1. Open the "OpenEmu-SDK.xcodeproj" project file using the latest version of Xcode.
  
3.6. If the Clean All Target sheet drops down, check all options, then click Clean.
+
2. Choose Product > Scheme > OpenEmuBase.
  
4. Choose Build > Build. This will make a new app called "DeSmuME (PPC).app" in the "/trunk/desmume/src/cocoa/build/Release" folder.
+
3. Click Run. This will build a Debug version of the framework.
  
5. Open the "DeSmuME (XCode 4).xcodeproj" project file.
+
4. After the build finishes, choose Product > Build For > Profiling. This will start building the Release version of the framework.
  
6. Choose Product > Scheme > DeSmuME (OS X App; v10.5 Leopard Release Build).
+
5. In the Xcode sidebar, expand the Products folder. This should show "OpenEmuBase.framework".
  
7. Choose Product > Build For > Archiving, and then wait for Xcode to finish building the app.
+
6. Click "OpenEmuBase.framework", and then choose File > Show in Finder.
  
And you're done! The newly built app will be present in the "/trunk/desmume/src/cocoa/build/Merged Release" folder.
+
7. In the Finder window that appears, you should be in a folder named "Debug". Right-click the window title (which should read "Debug"), and then choose the "Products" folder underneath it.
  
=== OS X App Legacy Build ===
+
8. Wait for Xcode to finish building the Release version framework.
1. Open the "DeSmuME (Legacy).xcodeproj" project file using Xcode 3.
+
  
2. In the Build Target menu (located in the upper-left corner of the project window), under Active Configuration, choose Release.
+
9. In the Finder, from the "Products" folder, open the "Release" folder.
  
3. In the Build Target menu, under Active Target, choose one of the four build targets.
+
10. Move OpenEmuBase.framework into the "desmume/src/frontend/cocoa/openemu" folder.
  
''Note: If you have previously made the standard OS X App build using Xcode 3, you MUST perform a project clean prior to building the OS X App Legacy build. To do this, perform steps 3.5 and 3.6.''
+
==== Building the OpenEmu plug-in ====
 +
'''Note:''' ''In order to build the OpenEmu plug-in, it is mandatory that OpenEmuBase.framework is present in the "desmume/src/frontend/cocoa/openemu" folder. Otherwise, the build will fail due to missing frameworks.''
  
''Note: You do NOT have to perform a project clean if you made the standard OS X App build using Xcode 4.''
+
1. Open the "DeSmuME (Latest).xcodeproj" project file using the latest version of Xcode.
  
3.5. Choose Build > Clean All Targets.
+
2. Choose Product > Scheme > DeSmuME (OpenEmu Plug-in).
  
3.6. If the Clean All Target sheet drops down, check all options, then click Clean.
+
3. Click Run. This will build a Debug version of the plug-in.
  
4. Choose Build > Build, and then wait for Xcode to finish building the app.
+
4. After the build finishes, choose Product > Build For > Profiling. This will start building the Release version of the plug-in.
  
And you're done! The newly built app will be present in the "/trunk/desmume/src/cocoa/build/Release" folder.
+
5. In the Xcode sidebar, expand the Products folder. This should show the "DeSmuME.oecoreplugin" bundle.
  
 +
6. Click "DeSmuME.oecoreplugin", and then choose Show in Finder.
 +
 +
7. In the Finder window that appears, you should be in a folder named "Debug". Right-click (or Control-click) the window title (which should read "Debug"), and then choose the "Products" folder underneath it.
 +
 +
8. Wait for Xcode to finish building the Release version plug-in.
 +
 +
9. In the Finder, from the "Products" folder, open the "Release" folder.
 +
 +
10. Choose New > New Finder Window.
 +
 +
11. With the new Finder window selected, choose Go > Go To Folder.
 +
 +
12. In the drop-down sheet, in the "Go to the folder" text field, enter the following exactly as shown:
 +
~/Library/Application Support/OpenEmu/Cores
 +
 +
13. Move the DeSmuME.oecoreplugin bundle from the Release folder into the Cores folder.
 +
 +
And that's it! The DeSmuME OpenEmu plug-in should now be installed. You should now be able to run NDS ROMs from within OpenEmu.app.
  
=== OpenEmu Plug-in Build ===
 
TBD
 
  
 
== Appendix A: Comparison Charts of Different Builds ==
 
== Appendix A: Comparison Charts of Different Builds ==
Line 304: Line 336:
 
=== Build Compatibility ===
 
=== Build Compatibility ===
 
The table below lists a summary of both binary and operating system compatibility for all possible builds.
 
The table below lists a summary of both binary and operating system compatibility for all possible builds.
 +
 +
'''Note:''' ''All binaries will not be compatible with OS X v10.4 (Tiger) or earlier.''
  
 
{| class="wikitable" style="text-align: center;"
 
{| class="wikitable" style="text-align: center;"
 
! scope="col" width="150" |
 
! scope="col" width="150" |
 
! scope="col" width="150" | OS X App
 
! scope="col" width="150" | OS X App
 +
! scope="col" width="150" | OS X App (dev+)
 
! scope="col" width="150" | OS X App (Final Release)
 
! scope="col" width="150" | OS X App (Final Release)
! scope="col" width="150" | OS X App (Legacy)
 
 
! scope="col" width="150" | OpenEmu Plug-in
 
! scope="col" width="150" | OpenEmu Plug-in
 
|-
 
|-
 
! scope="row" | PowerPC, 32-bit
 
! scope="row" | PowerPC, 32-bit
 
| Yes[1]
 
| Yes[1]
 +
| No
 
| Yes
 
| Yes
| Yes[1]
 
 
| No
 
| No
 
|-
 
|-
 
! scope="row" | PowerPC, 64-bit
 
! scope="row" | PowerPC, 64-bit
 
| Yes[1]
 
| Yes[1]
| Yes
+
| No
| Yes[1]
+
| No
 
| No
 
| No
 
|-
 
|-
Line 327: Line 361:
 
| Yes
 
| Yes
 
| Yes
 
| Yes
| Yes[1]
+
| Yes
 
| No
 
| No
 
|-
 
|-
Line 333: Line 367:
 
| Yes
 
| Yes
 
| Yes
 
| Yes
| Yes[1]
+
| Yes
 
| Yes
 
| Yes
 
|-
 
|-
! scope="row" | OS X v10.4 (Tiger)
+
! scope="row" | OS X v10.5 (Leopard)
 +
| Yes
 
| No
 
| No
 +
| Yes
 
| No
 
| No
| Yes[1]
+
|-
 +
! scope="row" | OS X v10.6 (Snow Leopard)
 +
| Yes
 +
| No
 +
| Yes
 
| No
 
| No
 
|-
 
|-
! scope="row" | OS X v10.5 (Leopard)
+
! scope="row" | OS X v10.7 (Lion)
 +
| Yes
 
| Yes
 
| Yes
 
| Yes
 
| Yes
| Yes[1]
 
 
| No
 
| No
 
|-
 
|-
! scope="row" | OS X v10.6 (Snow Leopard)
+
! scope="row" | OS X v10.8 (Mountain Lion)
 
| Yes
 
| Yes
 
| Yes
 
| Yes
Line 354: Line 394:
 
| No
 
| No
 
|-
 
|-
! scope="row" | OS X v10.7 (Lion)
+
! scope="row" | OS X v10.9 (Mavericks)
 
| Yes
 
| Yes
 
| Yes
 
| Yes
 
| Yes
 
| Yes
 +
| No
 +
|-
 +
! scope="row" | OS X v10.10 (Yosemite)
 
| Yes
 
| Yes
 +
| Yes
 +
| Yes
 +
| No
 
|-
 
|-
! scope="row" | OS X v10.8 (Mountain Lion)
+
! scope="row" | OS X v10.11 (El Capitan)
 +
| Yes
 +
| Yes
 +
| Yes
 +
| Yes
 +
|-
 +
! scope="row" | OS X v10.12 (Sierra)
 +
| Yes
 +
| Yes
 +
| Yes
 +
| Yes
 +
|-
 +
! scope="row" | OS X v10.13 (High Sierra)
 
| Yes
 
| Yes
 
| Yes
 
| Yes

Revision as of 01:07, 16 November 2017

Contents

About the Build Targets

DeSmuME for OS X may be built using several different configurations. Each build configuration is listed in an Xcode project as a "build target." The Xcode project files, provided with the DeSmuME source code, include several build targets to suit your needs. Many build targets are similar to each other, and so they have been organized into the following categories, based on what the build target produces.


OS X App

These build targets produce a self-contained OS X application package (or "app bundle"). These builds use our official OS X frontend to run the DeSmuME emulator, and are designed for the debugging and testing of pre-release builds. These app bundles are compatible with OS X v10.6 or later. (Also compatible with OS X v10.5 if building from the Xcode 3 project).

Build Target Goals:

  • Fully featured.
  • Widest build compatibility with Xcode versions running different OS X versions.
  • Quick debug-and-test of code changes.

Advantages:

  • Can be built on machines running OS X v10.5 or later, and Xcode v3.1.4 or later.
  • Binaries can be configured to run in debug mode or in release mode.
  • Binaries can be configured for PowerPC or Intel compatibility.
  • Building the app is faster than the final release build.

Disadvantages:

  • Binary compatibility with OS X v10.5 requires Xcode 3 to build.


OS X App (dev+)

This build target is just like the normal OS X App build, except it enables additional debugging features, such as the GDB remote stub. This build is meant for developer usage.

Build Target Goals:

  • Fully featured, and includes additional debugging features.
  • Must be compatible with the latest version of Xcode running on the latest version of OS X.
  • Quick debug-and-test of code changes.

Advantages:

  • Can be built on machines running Xcode v4.6.3 or later.
  • Binaries can be configured to run in debug mode or in release mode.
  • Building the app is faster than the final release build.

Disadvantages:

  • Must be built on a machine running OS X v10.7 or later.
  • Due to the additional debugging features, performance will be slightly lower compared to the other builds.


OS X App (Xcode 6 .XIB for v10.5 Leopard Release Build)

This build target is a helper build target for producing final release builds of DeSmuME. It is used solely as an intermediate build step, and is not intended for normal usage. See #OS_X_App_Build_for_Final_Release for more details.


OS X App (v10.5 Leopard Release Build)

This build target is for producing final release builds of DeSmuME. These builds will use our official OS X frontend contained in an OS X app bundle, and are tuned for the fastest possible performance and the widest binary and OS compatibility.

Build Target Goals:

  • Fully featured.
  • Widest binary compatibility.
  • Widest OS compatibility.
  • Fastest performance.

Advantages:

  • Produces the fastest running binaries compared to all other build targets.
  • Produces a universal binary that supports both 32-bit and 64-bit.
  • Binaries are compatible with OS X v10.5 and later.

Disadvantages:

  • Must be built on a machine running the latest version of OS X and Xcode.
  • Building the app for release takes more steps than other builds.
  • Requires a separate Mac or virtual machine running OS X Mavericks in order to run Xcode v3.2.6 and Xcode v6.2 for the intermediate build steps.


OpenEmu Plug-in

These build targets produce a plug-in bundle that is compatible with the OpenEmu application (http://openemu.org/). These build targets exist to prove that our DeSmuME source code is modular enough to be adapted easily into other applications. In this case, the plug-in contains the DeSmuME emulator backend, while OpenEmu acts as the frontend that runs the emulator.

Build Target Goals:

  • Compatibility with OpenEmu.
  • Proving that the core source code is modular enough to be integrated with third-party frontends.

Advantages:

  • Compatible with OpenEmu.
  • Plug-ins are much smaller in size compared to full application builds.

Disadvantages:

  • Must be built on a machine running OS X v10.11 or later.
  • Binaries only run on machines with 64-bit Intel processors running OS X v10.11 or later.
  • The frontend is handled by a third-party application, which will not expose all of DeSmuME's features to the user.


Set Up the Build Environment

All DeSmuME build targets must be built using Apple's Xcode IDE. The Xcode project files, included in the "desmume/src/frontend/cocoa" folder of the source code, are supported for the following versions of Xcode:

Project File Name Supported Xcode Version
DeSmuME (Xcode 3).xcodeproj v3.1.4 (if running on Leopard); v3.2.6 (if running on Snow Leopard or later)
DeSmuME (Latest).xcodeproj v4.6.3 or later

Xcode Setup

Refer to the following conditions to determine which Xcode version you need to install.


You must use Xcode 3 if any of the following conditions apply:

  • You are running OS X v10.5 or v10.6.
  • You are building an OS X App that runs on OS X v10.5.
  • You are building an OS X App that runs on PowerPC processors.
  • You are building an OS X App for final release.


You must use Xcode 4 or later if any of the following conditions apply:

  • You are running OS X v10.7 or later.
  • You are building an OpenEmu Plug-in.
  • You are building an OS X App for final release.


Note: Xcode 3 is not compatible with OS X v10.10 Yosemite. If you require the use of Xcode 3, you will need to run it on an older version of OS X.


Download Xcode 3

You can download Xcode 3 from the Apple Developer Connection website. Note that before you can download anything from the ADC website, you must log in using an Apple Developer ID. Once you are logged in, you may use the provided download links to download Xcode 3.


If you do not have an Apple Developer ID, you can register one for free.

If you are not already logged in to ADC, you can log in by accessing the ADC Downloads page.

Once you are logged in to ADC, you can use the following download links for Xcode 3.

If you will be building a Final Release build, then you also need Xcode 6.

Download the Latest Version of Xcode

Downloading the latest version of Xcode is very easy! If you are running Lion or later and have any Apple ID, then you can download Xcode directly from the Mac App Store.


Uninstall Previous Versions of Xcode

We highly recommend that you uninstall any previous versions of Xcode before you begin your installation. Doing so will better guarantee that you will have a clean build environment for DeSmuME. The easiest method for uninstalling Xcode is to use the uninstall-devtools script, located in the Library folder of your Xcode installation.

Note: You do not need to uninstall any versions of Xcode that are v4.3 or later. These versions of Xcode are self-contained application packages, which do not conflict with other Xcode versions.

To uninstall Xcode, open Terminal and type the following command into the command line:

sudo /Developer/Library/uninstall-devtools -mode=all

Note: You must be logged into an Administrator account to use this command.

Note: This command assumes that Xcode was installed at the default location, /Developer. The path to the uninstall-devtools script may be different if you did not use the default location when installing Xcode from before.


Set Up Xcode 3

Note: If you do not require the build options that Xcode 3 provides, then you may skip this step. See the Xcode Setup section for more details.

After Xcode 3 is downloaded, you will have a .dmg disk image containing a package installer. Start the Xcode 3 installation by opening the installer, and follow the onscreen instructions until you get to the installation list.

Once the installation list is shown, do the following:

  • Unless you are planning on building other software that must run on OS X v10.4, you may deselect the Mac OS X 10.4 SDK. (DeSmuME can only run on OS X v10.5 or later.)
  • If you are planning on installing the latest version of Xcode alongside Xcode 3, then deselect "System Tools" and "Essentials > iOS SDK". Since the latest Xcode will already have the newest version of the iOS SDK, installing the version included with Xcode 3 will be a waste of time and disk space.

Continue the installation as normal and let the installation finish.


Set Up the Latest Version of Xcode

When you download Xcode from the Mac App Store, Xcode should automatically install itself to the Applications folder once the download is complete. There are no additional steps. Pretty easy, right?


Download the DeSmuME Source Code

The DeSmuME source code is managed using git and is hosted on GitHub.


Build the DeSmuME Source

Regardless of which build target you will be using, you will need to use one of the Xcode project files provided with the DeSmuME source code. For most cases, you will want to build the latest revision. So from the source code folder, navigate to the "/desmume/src/frontend/cocoa" folder.

There should be two Xcode project files present in this folder:

  • DeSmuME (XCode 3).xcodeproj
  • DeSmuME (Latest).xcodeproj


OS X App Build

This is the quickest and easiest way to get started with using a pre-release build of DeSmuME.

Building Using Xcode 3

1. Open the "DeSmuME (XCode 3).xcodeproj" project file using Xcode 3.

2. In the Build Target menu (located in the upper-left corner of the project window), under Active Configuration, choose Release.

3. In the Build Target menu, under Active Target, choose one of the four build targets.

4. Choose Build > Build, and then wait for Xcode to finish building the app.

And you're done! The newly built app will be present in the "/desmume/src/frontend/cocoa/build/Release" folder. If you built the app using the "DeSmuME (XCode 3).xcodeproj" project file, then the built app will also include the current git commit number.

Building Using the Latest Version of Xcode

1. Open the "DeSmuME (Latest).xcodeproj" project file using Xcode.

2. Choose Product > Scheme > DeSmuME (OS X App).

3. In Xcode, choose Product > Build For > Profiling, and then wait for Xcode to finish building the app.

And you're done! The newly built app will be present in the "/desmume/src/frontend/cocoa/build/Release" folder.


OS X App Dev+ Build

The steps here are similar to that of the normal OS X App build, but will produce the developer-oriented build instead. In addition, you must be using Xcode 4 or later to make this build.

1. Open the "DeSmuME (Latest).xcodeproj" project file using Xcode.

2. Choose Product > Scheme > DeSmuME (OS X App, dev+).

If you want to run dev+ build with Xcode's LLDB debugger:

3a. Click Run. This will build a Debug version of the app, which will automatically launch when finished.

And you're done! The newly built app will be present in the "/desmume/src/frontend/cocoa/build/Debug" folder.

If you need to use the dev+ build without running the debugger:

3b. In Xcode, choose Product > Build For > Profiling, and then wait for Xcode to finish building the app. (Note that this build does use program optimizations.)

And you're done! The newly built app will be present in the "/desmume/src/frontend/cocoa/build/Release" folder.


OS X App Build for Final Release

This is the process that we use for our official release builds. To make this build, you must meet the following requirements:

  • You must have both Xcode v3.2.6 and Xcode v6.2 installed on a system running OS X Mavericks v10.9.5.
  • You must have the latest version of Xcode running on the latest version of macOS. (At the time of this writing, the latest version of Xcode is v9.1, and the latest version of macOS is 10.13.1.)

1. Let's start with building on OS X Mavericks: Open the "DeSmuME (XCode 3).xcodeproj" project file using Xcode 3.

2. In the Build Target menu (located in the upper-left corner of the project window), under Active Configuration, choose Release.

3. In the Build Target menu, under Active Target, choose the build target "DeSmuME (OS X App; PowerPC Release Build)".

4. Choose Build > Clean All Targets.

5. In the Clean All Targets sheet, check all options, then click Clean, and then wait for the clean process to finish.

6. Choose Build > Build, and then wait for the build process to finish. This will make a new app called "DeSmuME (PPC).app" in the "/desmume/src/frontend/cocoa/build/Release" folder.

7. While still on OS X Mavericks: Open the "DeSmuME (Latest).xcodeproj" project file using Xcode 6.2.

8. Choose Product > Scheme > DeSmuME (OS X App; Xcode 6 .XIB for v10.5 Leopard Release Build).

9. Choose Product > Clean, and then wait for the clean process to finish.

10. Choose Product > Build, and then wait for the build process to finish. This will make a new app called "DeSmuME (Xcode 6).app" in the "/desmume/src/frontend/cocoa/build/Release" folder.

11. Quit both Xcode 3 and Xcode 6 on OS X Mavericks.

12. On the latest macOS: Open the "DeSmuME (Latest).xcodeproj" project file using the latest version of Xcode.

13. Choose Product > Scheme > DeSmuME (OS X App; v10.5 Leopard Release Build).

14. Choose Product > Clean, and then wait for the clean process to finish.

15. Choose Product > Perform Action > Generate Optimization Profile.

16. In the Generate Optimization Profile sheet, ensure that Use Run Action is the selected option, and then click Run.

17. Wait for Xcode to finish building the app. When Xcode finishes, DeSmuME.app will automatically launch.

18. Perform the recommended PGO exercises listed on this page: TBD

19. After all PGO exercises are complete, quit DeSmuME.app. Xcode should now report that it has generated an optimization profile.

20. In Xcode, choose Product > Build For > Profiling, and then wait for Xcode to finish.

And you're done! The newly built app will be present in the "/desmume/src/frontend/cocoa/build/Merged Release" folder.


OpenEmu Plug-in Build

The DeSmuME OpenEmu plug-in is used as an extension to the OpenEmu application. Installing the plug-in involves building OpenEmuBase.framework from source, then moving the framework to the "desmume/src/frontend/cocoa/openemu" folder, then building the plug-in from source, and then finally placing the plug-in into the ~/Library/Application Support/OpenEmu/Cores folder.


You can download the OpenEmu SDK source code from here:


Building and installing OpenEmuBase.framework from source

1. Open the "OpenEmu-SDK.xcodeproj" project file using the latest version of Xcode.

2. Choose Product > Scheme > OpenEmuBase.

3. Click Run. This will build a Debug version of the framework.

4. After the build finishes, choose Product > Build For > Profiling. This will start building the Release version of the framework.

5. In the Xcode sidebar, expand the Products folder. This should show "OpenEmuBase.framework".

6. Click "OpenEmuBase.framework", and then choose File > Show in Finder.

7. In the Finder window that appears, you should be in a folder named "Debug". Right-click the window title (which should read "Debug"), and then choose the "Products" folder underneath it.

8. Wait for Xcode to finish building the Release version framework.

9. In the Finder, from the "Products" folder, open the "Release" folder.

10. Move OpenEmuBase.framework into the "desmume/src/frontend/cocoa/openemu" folder.

Building the OpenEmu plug-in

Note: In order to build the OpenEmu plug-in, it is mandatory that OpenEmuBase.framework is present in the "desmume/src/frontend/cocoa/openemu" folder. Otherwise, the build will fail due to missing frameworks.

1. Open the "DeSmuME (Latest).xcodeproj" project file using the latest version of Xcode.

2. Choose Product > Scheme > DeSmuME (OpenEmu Plug-in).

3. Click Run. This will build a Debug version of the plug-in.

4. After the build finishes, choose Product > Build For > Profiling. This will start building the Release version of the plug-in.

5. In the Xcode sidebar, expand the Products folder. This should show the "DeSmuME.oecoreplugin" bundle.

6. Click "DeSmuME.oecoreplugin", and then choose Show in Finder.

7. In the Finder window that appears, you should be in a folder named "Debug". Right-click (or Control-click) the window title (which should read "Debug"), and then choose the "Products" folder underneath it.

8. Wait for Xcode to finish building the Release version plug-in.

9. In the Finder, from the "Products" folder, open the "Release" folder.

10. Choose New > New Finder Window.

11. With the new Finder window selected, choose Go > Go To Folder.

12. In the drop-down sheet, in the "Go to the folder" text field, enter the following exactly as shown:

~/Library/Application Support/OpenEmu/Cores

13. Move the DeSmuME.oecoreplugin bundle from the Release folder into the Cores folder.

And that's it! The DeSmuME OpenEmu plug-in should now be installed. You should now be able to run NDS ROMs from within OpenEmu.app.


Appendix A: Comparison Charts of Different Builds

Build Compatibility

The table below lists a summary of both binary and operating system compatibility for all possible builds.

Note: All binaries will not be compatible with OS X v10.4 (Tiger) or earlier.

OS X App OS X App (dev+) OS X App (Final Release) OpenEmu Plug-in
PowerPC, 32-bit Yes[1] No Yes No
PowerPC, 64-bit Yes[1] No No No
Intel, 32-bit Yes Yes Yes No
Intel, 64-bit Yes Yes Yes Yes
OS X v10.5 (Leopard) Yes No Yes No
OS X v10.6 (Snow Leopard) Yes No Yes No
OS X v10.7 (Lion) Yes Yes Yes No
OS X v10.8 (Mountain Lion) Yes Yes Yes No
OS X v10.9 (Mavericks) Yes Yes Yes No
OS X v10.10 (Yosemite) Yes Yes Yes No
OS X v10.11 (El Capitan) Yes Yes Yes Yes
OS X v10.12 (Sierra) Yes Yes Yes Yes
OS X v10.13 (High Sierra) Yes Yes Yes Yes

1. Available only by configuration in Xcode 3.

Appendix B: Installing DeSmuME From Source (Legacy Instructions)

This is a document that described an older method for installing DeSmuME from the source code. It is now obsolete and no longer supported by the DeSmuME team. You can view it here: Installing DeSmuME from source on Mac OS X (Legacy Instructions)

Personal tools