Compile Universal Binary For Mac

This directory contains binaries for a base distribution and packages to run on Mac OS X (release 10.6 and above). Mac OS 8.6 to 9.2 (and Mac OS X 10.1) are no longer supported but you can find the last supported release of R for these systems (which is R 1.7.1) here. Releases for old Mac OS X systems (through Mac OS X 10.5) and PowerPC Macs can be found in the old directory.

Note: CRAN does not have Mac OS X systems and cannot check these binaries for viruses.Although we take precautions when assembling binaries, please use the normal precautions with downloaded executables.

Apple's new Universal 2 file format One way to offer apps for two separate CPU designs is to compile an app with multiple executables inside using the Universal binary format. For instance, the app.

Package binaries for R versions older than 3.2.0 are only available from the CRAN archive so users of such versions should adjust the CRAN mirror setting (https://cran-archive.r-project.org) accordingly.

Compile Universal Binary For Mac Torrent

  • To create a universal binary for your project, merge the resulting executable files into a single executable binary using the lipo tool. For makefiles you create outside of Xcode, pass the appropriate architecture values to the compiler using the -target option.
  • This may be a very silly question, but I'm new to developing on Macs and am having a hard time with the universal binaries. I've got an application that I'm compiling in QT Creator, which according to lipo is producing i386 architecture outputs. As I understand it, that means it is producing Mac OS X 32 bit outputs.
  • This may be a very silly question, but I'm new to developing on Macs and am having a hard time with the universal binaries. I've got an application that I'm compiling in QT Creator, which according to lipo is producing i386 architecture outputs. As I understand it, that means it is producing Mac OS X 32 bit outputs.

R 4.0.3 'Bunny-Wunnies Freak Out' released on 2020/10/10

Please check the MD5 checksum of the downloaded image to ensure that it has not been tampered with or corrupted during the mirroring process. For example type
openssl sha1 R-4.0.3.pkg
in the Terminal application to print the SHA1 checksum for the R-4.0.3.pkg image. On Mac OS X 10.7 and later you can also validate the signature using
pkgutil --check-signature R-4.0.3.pkg

Latest release:

R-4.0.3.pkg (notarized and signed)
SHA1-hash: 8402f586aef1fdb12c6e34c73b286f87318fb1be
(ca. 85MB)
R 4.0.3 binary for macOS 10.13 (High Sierra) and higher, signed and notarized package. Contains R 4.0.3 framework, R.app GUI 1.73 in 64-bit for Intel Macs, Tcl/Tk 8.6.6 X11 libraries and Texinfo 6.7. The latter two components are optional and can be ommitted when choosing 'custom install', they are only needed if you want to use the tcltk R package or build package documentation from sources.

Note: the use of X11 (including tcltk) requires XQuartz to be installed since it is no longer part of OS X. Always re-install XQuartz when upgrading your macOS to a new major version.

Important: this release uses Xcode 10.1 and GNU Fortran 8.2. If you wish to compile R packages from sources, you will need to download and GNU Fortran 8.2 - see the tools directory.

NEWS (for Mac GUI)News features and changes in the R.app Mac GUI
Mac-GUI-1.73.tar.gz
SHA1-hash: 7f4b1d050757ce78545bdeb9d178a69d13046aa1
Sources for the R.app GUI 1.73 for Mac OS X. This file is only needed if you want to join the development of the GUI, it is not intended for regular users. Read the INSTALL file for further instructions.
Note: Previous R versions for El Capitan can be found in the el-capitan/base directory.

Binaries for legacy OS X systems:

R-3.6.3.nn.pkg (signed)
SHA1-hash: c462c9b1f9b45d778f05b8d9aa25a9123b3557c4
(ca. 77MB)
R 3.6.3 binary for OS X 10.11 (El Capitan) and higher, signed package. Contains R 3.6.3 framework, R.app GUI 1.70 in 64-bit for Intel Macs, Tcl/Tk 8.6.6 X11 libraries and Texinfo 5.2. The latter two components are optional and can be ommitted when choosing 'custom install', they are only needed if you want to use the tcltk R package or build package documentation from sources.
R-3.3.3.pkg
MD5-hash: 893ba010f303e666e19f86e4800f1fbf
SHA1-hash: 5ae71b000b15805f95f38c08c45972d51ce3d027

(ca. 71MB)
R 3.3.3 binary for Mac OS X 10.9 (Mavericks) and higher, signed package. Contains R 3.3.3 framework, R.app GUI 1.69 in 64-bit for Intel Macs, Tcl/Tk 8.6.0 X11 libraries and Texinfo 5.2. The latter two components are optional and can be ommitted when choosing 'custom install', it is only needed if you want to use the tcltk R package or build package documentation from sources.

Note: the use of X11 (including tcltk) requires XQuartz to be installed since it is no longer part of OS X. Always re-install XQuartz when upgrading your OS X to a new major version.

R-3.2.1-snowleopard.pkg
MD5-hash: 58fe9d01314d9cb75ff80ccfb914fd65
SHA1-hash: be6e91db12bac22a324f0cb51c7efa9063ece0d0

(ca. 68MB)
R 3.2.1 legacy binary for Mac OS X 10.6 (Snow Leopard) - 10.8 (Mountain Lion), signed package. Contains R 3.2.1 framework, R.app GUI 1.66 in 64-bit for Intel Macs.
This package contains the R framework, 64-bit GUI (R.app), Tcl/Tk 8.6.0 X11 libraries and Texinfop 5.2. GNU Fortran is NOT included (needed if you want to compile packages from sources that contain FORTRAN code) please see the tools directory.
NOTE: the binary support for OS X before Mavericks is being phased out, we do not expect further releases!
Mac universal binaryThe new R.app Cocoa GUI has been written by Simon Urbanek and Stefano Iacus with contributions from many developers and translators world-wide, see 'About R' in the GUI.

Subdirectories:

toolsAdditional tools necessary for building R for Mac OS X:
Universal GNU Fortran compiler for Mac OS X (see R for Mac tools page for details).
baseBinaries of R builds for macOS 10.13 or higher (High Sierra)
contribBinaries of package builds for macOS 10.13 or higher (High Sierra)
el-capitanBinaries of package builds for OS X 10.11 or higher (El Capitan build)
mavericksBinaries of package builds for Mac OS X 10.9 or higher (Mavericks build)
oldPreviously released R versions for Mac OS X

You may also want to read the R FAQ and R for Mac OS X FAQ. For discussion of Mac-related topics and reporting Mac-specific bugs, please use the R-SIG-Mac mailing list.

Information, tools and most recent daily builds of the R GUI, R-patched and R-devel can be found at http://mac.R-project.org/. Please visit that page especially during beta stages to help us test the Mac OS X binaries before final release!

Package maintainers should visit CRAN check summary page to see whether their package is compatible with the current build of R for Mac OS X.

Binary libraries for dependencies not present here are available from http://mac.R-project.org/libs and corresponding sources at http://mac.R-project.org/src.

Last modified: 2020/10/10, by Simon Urbanek

I’ve put together an Xcode template for creating Universal Binary Mach-O plugins for REALbasic. The template will compile a dylib for PPC, and a bundle for Universal Binary – and put these in a plugin folder ready for conversion to a .rbx file.
Updated 3/10/08 for version 1.4 of the template.
Updated 8/1/07 for version 1.3 of the template.
Updated 26/8/06 for version 1.2 of the template.
Updated 23/8/06 for version 1.1 of the template.

To use this template, start by downloading my template files (.zip format, 27KB), and unzip the downloaded template files archive.

Then, do the following:

  1. Make sure you have Xcode installed. You can download it for free from Apple by signing up for a free Apple Developer Connection Online membership. This template has been tested with Xcode 3.1.1. When you install Xcode, be sure to install the “Mac OS X 10.3.9 package” (it isn’t selected by default), or the plugin template won’t work.
  2. Make sure you are using REALbasic 2006r4 or later for Mac OS X. 2006r4 was the first version to support Universal Binary builds, and so you’ll need this version or later to test your Universal Binary plugin.
  3. Make sure you use the latest REALbasic Plugin SDK (included in the REALbasic download for Mac OS X, in the “/Extras/Plugins SDK/” folder).
  4. Copy the folder “REALbasic”, from the downloaded template files, to “/Developer/Library/Xcode/Project Templates/” (which is where Xcode keeps its project templates).
  5. Launch Xcode.
  6. Select “File > New Project…”.
  7. Select the REALbasic category under the Mac OS X category, and then select the “REALbasic Universal Binary Mach-O Plugin”. Click “Choose…” to use this template.
  8. Give the project a name. This will also be the name of your plugin, and the folder the project lives in. By default the new folder will be created in your home folder, but you can change this to another location.
  9. Click “Finish”. A new project will open, and a new project folder will be created on your hard disk, wherever you chose above.
  10. Find this folder on your hard disk, and copy the “Glue Code” and “Includes” folders from the latest Plugins SDK into the root level of your new project’s folder. Switch back to Xcode, and you should see that the “Glue Code” and “Includes” folders and files in the Xcode file list have turned from red text to black text.
  11. By default, the plugin contains one global method, called CurrentArchitecture. You can now compile your plugin, and give this method a test! Just select “Build > Build” in Xcode (or press Apple-B), and both the PPC and Universal Binary dylibs will be built.
  12. The first time you build the project, you will get four warnings that build folders do not exist. Ignore these warnings – they’re just caused by Xcode creating the folder structure for your plugin.
  13. Once you have built the empty plugin, you’ll find that a new folder will have be created by Xcode in your project folder. It will have the same name as the project. This folder is the skeleton structure of your plugin. It will contain one folder, called “Build Resources”. “Build Resources” will contain two folders: “Mac Carbon Mach-O”, containing the PPC dylib, and “Mac Carbon Mach-O Universal”, containing the Universal Binary bundle.
  14. To make these two files into a plugin (also known as a .rbx file), you’ll need to use the “Plugin Converter” from the REALbasic Plugins SDK. Open the “Plugin converter.rb” project, and build the project. This will build an application called “RB Plugin Converter”.
  15. Run this application, and click on the “Convert Folder” button. Find your project folder, and select the subfolder with the same name (you’re selecting the folder that contains the “Build Resources” folder). Click on “Choose”.
  16. The Plugin Converter will prompt you to select where you want to save the built plugin. Select your REALbasic Plugins folder (something like “/Applications/REALbasic 2008r4/Plugins/”, and click “Save”. A file called “YourProjectName.rbx” will be created in the Plugins folder. This is your plugin!
  17. Your plugin is now ready to go. Launch REALbasic, open the sample project included with the template download – “PluginTest.rbp” – and build the project. It will build as a Universal Binary application called “PluginTest.app”. If you run “PluginTest.app” on a PowerPC Mac, it will use the CurrentArchitecture global method to display a message saying that it is running the PowerPC code. The same goes for if you run the app under Rosetta on an Intel Mac. If you run “PluginTest.app” natively on an Intel Mac, then it will say it is running the Intel plugin code.
  18. Once you have finished developing and testing your plugin, switch Xcode to use the “Deployment” build configuration. You can do this from Xcode’s “Project > Set Active Build Configuration” menu. Build the plugin again. The Deployment build configuration strips out any unused code and symbols, and results in a much smaller plugin file. Use this version of the plugin in any applications you distribute.

Version 1.4, 3/10/08

Updated the instructions for REALbasic 2008r4 and Xcode 3.1.1.

Version 1.3, 8/1/07

Changed the Universal Binary part of the plugin to be a bundle rather than a dynamic library. Sabroe smc 116 manual online. This will take advantage of a new feature in future versions of REALbasic, where the Universal Binary part of the plugin will be loaded directly into memory and not written out to disk.

Changed the target order to ensure that “Build All” is the default.

Version 1.2, 26/8/06

Added in an exports file to the Deployment build configuration for both PPC and UB, and set this build configuration to use Dead Code Stripping. This reduces the size of the built Deployment plugin considerably.

Changed the SDKs and Mac OS X Deployment Targets to build for 10.3.9 with GCC 3.3 for the PPC target and the PPC part of the UB target; and to build for 10.4u with GCC 4.0 for the i386 part of the UB target. This means that 10.3 can be supported for backwards compatability.

Disabled Prebinding for the i386 part of the UB target, as it is 10.4 only and therefore doesn’t need prebinding.

Removed the unused “Default” build configuration.

Version 1.1, 23/8/06

Compile Universal Binary For Machine Learning

Compile

The PowerPC dylib is now built as a PowerPC target when compiled on an Intel machine. Previously it was being compiled as $(NATIVE_ARCH), which would build as PPC on PPC, and Intel on Intel. Thanks to Philippe Rigaux for spotting this error.

The UB dylib now compiles against the 10.4u SDK, at /Developer/SDKs/MacOSX10.4u.sdk/. This means that it will actually compile :-)

A sample global method, CurrentArchitecture, is now included in the plugin template.

A few other compile settings have been moved from being Target settings to being Project settings, to avoid duplication.

Compile Universal Binary For Macro

Version 1.0, 21/8/06

Mac Universal Binary

Initial release.