Open main/Main.sln, select the Mac configuration, and run the Build command. When building MonoDevelop using MonoDevelop, be sure to select the Mac configuration, as this will enable building only the addins that work on Mac. /./extras//build/* MonoDevelop.app/Contents/MacOS/lib/monodevelop/AddIns// To include addins from extras, manually copy their build directories into the MonoDevelop.app directory, e.g. To build the app package, navigate to the macOS build directory: cd main/build/MacOSXįrom here, build the MonoDevelop.app using make app. Next, replace the line in profiles/default that begins with “main” with the one from profiles/mac, then run configure again using the default profile. To include additional addins from extras in the build, instead of using the Mac profile, use configure -select to select addins. export ACLOCAL_FLAGS="-I /Library/Frameworks/amework/Versions/Current/share/aclocal"Īdd the GTK+ libraries’ location to the Mac dynamic loader path: export DYLD_FALLBACK_LIBRARY_PATH=/Library/Frameworks/amework/Versions/Current/lib:/lib:/usr/lib Tell aclocal where to find the pkgconfig M4 macro (pkg.m4), e.g. Things you might have to do before running the configure script If you configured with a non-default prefix, then when you build an app bundle, the entire prefix will be merged into the app bundle. MonoDevelop will pick up libraries from the prefix automatically.
IMPORTANT: Do not install MonoDevelop into the install prefix. Instead edit profiles/mac manually to add any additional modules. NOTE: DO NOT use configure –select on Mac - the Mac profile passes adds required arguments to the configuration of main. NOTE: Please ensure that you have the very latest Mono MDK.Ĭheck out MD, configure using the Mac profile: git clone
If you have Xcode 4.3 or later, you will need to then install the Xcode Commandline tool from Xcode preferences, and install autoconf and automake from brew. Building using Makefiles Buildingįirst you will need Xcode installed. However, there are a few caveats, so this page explains the Mac build process in more detail. In general, the instructions in Development:Getting Started can be applied directly to building MD on macOS. macOSīuilding MonoDevelop from source on the Mac is straightforward when the latest Mono SDK package is installed. The configure script may fail because of missing dependencies install them, and re-run the command.Īfter this, you can build and install any of the additional tarballs using the same procedure.
You can get the tarballs from the Download page.įirst of all you have to configure and install the main tarball. MonoDevelop is split in several tarballs: one for the main application, and one for each optional add-in. It is a good idea to keep separate copies for using and developing. Since you’ll be working on the development version, it’s best not to install it instead, you can use make run Use the –help option to get information about available profiles and other build options. You can also configure a predefined list of modules by specifying a build profile using the –profile option. configure -selectįurther executions of the configure script will configure only the selected add-ins. You can select the list of extra add-ins to be built by running this command. This is very useful for development and testing. However, this script sets them up to build against the MonoDevelop in ‘main’, and ensures that they will be loaded when MonoDevelop is launched with ‘make run’ in this top-level directory. The ‘extras’ add-ins are designed to be built and distributed separately, and therefore build against your system-installed MonoDevelop by default. The MonoDevelop build system consists of a ‘main’ module, which contains the main distribution, and a number of additional add-ins in subdirectories of ‘extras’. This script allows selecting and configuring a set of MonoDevelop modules to be included in an integrated build. It may fail because of missing dependencies install them, and re-run the command.
Building from GitĪfter getting the source code from GitHub, run the following code in the root directory. See the section on MONO_GAC_PREFIX in the Parallel Mono Environment guide. Note that if your distro has sufficiently up-to-date Gtk# or Mono.Addins packages, you can configure a parallel Mono environment to use them instead of building them from source. Do not install anything to /usr or /usr/local unless you completely understand the implications of doing so. If not, you should use a Parallel Mono Environment. We strongly recommend you install everything from packages if possible. You can build them from git, source releases or, even easier, simply install the pre-built packages appropriate for your platform. MonoDevelop requires the following packages (or newer versions):