First post, by emendelson
EDIT At Dominus's suggestion, I'll stop updating the code in this post, and update the script on Github instead, here:
https://github.com/emendelson/OneStopDOSBoxOS … topDOSBoxOSX.sh
First, everything important in this was provided by Dominus, who has spent years fine-tuning his method of building static-linked DOSBox under OS X. All I did was combine the bits that he suggested into a single script.
If all you need is a current SVN build of DOSBox, you don't need this script. This script is designed for anyone who wants to modify DOSBox and create a custom build (or build Wengier's LFN-and-clipboard-enabled variant). You can always download Dominus's up-to-date OS X build from here:
http://dl.dropbox.com/u/7737184/Dosbox/Dosbox-Snapshot.dmg
But if you want to build your own DOSBox, here is a script that I call OneStopDOSBoxOSX.sh. It offers to download the latest dosbox source code, and then offers to install all the libraries needed to build static-linked DOSBox in OS X; then it offers to build a dynamic-linked version (usable only on your own current system); then it offers to build a static-linked version that can work on other people's system as well as on yours; then it offers to create an OS X app from whichever version of the executable you created. (The OS X app is incomplete - it lacks an icon - but at least it will run. See below for more details.)
EDIT: The script now prompts you to install Xcode and the Xcode command-line tools if they're not already on your system. If these are not already installed. If you install Xcode when prompted, you must run Xcode once and accept the license agreement before running the script.
I can confirm that this script works perfectly in a new, clean OS X El Capitan system.
The script can go anywhere (I think), but I put it in ~/Development for easy access to all related folders. Of course you'll need to run chmod +x OneStopDOSBoxOSX.sh before you can run ./OneStopDOSBoxOSX.sh in the terminal.
By default, it downloads the source code and builds the executable in ~/Development/dosbox but you can change this by changing a variable at the top of the script. If you use the script to download the code, the resulting build will identify itself as DOSBox CVS, but (as qbix confirms in another thread) it will otherwise be identical to a build made from code downloaded from SourceForge SVN (and that SVN-based build will identify itself as DOSBox SVN).
When the script runs, it displays a zillion warnings, but it should not produce any errors. If it does, please let me know. When you build the static-linked version, you may be prompted to press Enter after the Makefile gets patched by the script - this prompt is there to make certain that the patch succeeded; if it works on your system, feel free to remove the line that does the prompting. (EDIT: As Dominus points out in a message below, you ONLY need to static-link if you are creating a build that needs to run on someone else's machine! You don't need to bother with static-linking if you are creating a build for your current system only.)
In case you see error messages when building: Exit the script; in the terminal, navigate to the folder with the source of the library or dosbox that is causing the errors; copy he block of lines with OPTs and EXPORTS from the script into the terminal; then enter these commands, and then run the script again:
autoheader -fautoconf -fautomake -fchmod +x *.shchmod configure
Except for that one "Press Enter to continue" prompt, all prompts default to "No." Press Y repeatedly the first time you run the script to build the environment and install the needed libraries.
The script builds Wengier's LFN-and-clipboard-enabled source code (you'll have to download that on your own). EDIT Wengier has updated his code so that it now works perfectly with this script. If you want the clipboard feature, you will need to add --enable-clipboard to the ./configure commands for dosbox. (This applies to Wengier's version only!)
About the part of the script that creates a MyDOSBox.app: If you add a dosbox.icns icon (perhaps from Dominus's build) to the src folder, you can uncomment the line in the script that copies dosbox.icns into the app, and that should create a complete OS X app; though possibly it won't display the right icon until you Get Info or logout, etc.
Again, all the intelligent parts of this script are the work of Dominus. All I did was automate it by putting it into one enormous script.
EDIT: I've removed the actual script code, because the current version is at the GitHub address at the top of the post.
