Xcode - Wikipedia has a complete compatibility listing for Xcode, what version works with which version of OS X. It also includes a listing of versions of Xcode’s support libraries for things like iOS and iWatch, for each version. The latest version of Xcode that can be used with El Capitan is 8.2.1 see: Note that you must have macOS El Capitan 11. Xcode has a project setting for 'iOS Deployment', where you can choose that same (Xcode max) or lower iOS version that app can support. Of course you'll need a device with that lower IOS in order to use an older Xcode. Details may be involved that require certain app specifics, tho, so be prepared to meet them. Download Xcode For Os X El Capitan 10 11 6 Double-click the downloaded file to open a window showing its contents. Then double-click the file within, named InstallMacOSX.pkg. Follow the onscreen instructions, which will guide you through the steps necessary to install. The last Xcode version compatible with El Capitan is Xcode 8.2.1. If you can't install it from within Apple App Store, visit Apple Developer and download the app there. An Apple ID is required. Xcode is provided as xip file (signed zip).
Compatible Mac OS for Xcode Installation: Apple Xcode software is compatible and supported with following macOS versions. Mac OS X 10.10+ Yosemite; Mac OS X 10.11+ El Capitan; macOS 10.12+ Sierra; macOS 10.13+ High Sierra; macOS 10.14+ Mojave; macOS 10.15+ Catalina; macOS 11+ Big Sur or latest version; How to Download Xcode DMG Installer Manually?
Apple's Xcode Developer Tools (version 12.2 or later for Big Sur, 11.3 or later for Catalina, 10.0 or later for Mojave, 9.0 or later for High Sierra, 8.0 or later for Sierra, 7.0 or later for El Capitan, 6.1 or later for Yosemite, 5.0.1 or later for Mavericks, 4.4 or later for Mountain Lion, 4.1 or later for Lion, 3.2 or later for Snow Leopard. Build your future. Whether you’re just entering the workforce or you‘re an experienced developer or entrepreneur, take advantage of free resources to gain skills that help you succeed in Apple’s growing app economy, which provides millions of jobs in technology across the globe. Build your apps using Xcode 12 GM seed, test them on devices running iOS 14 and iPadOS GM seed, and submit them for review. Starting April 2021, all iOS and iPadOS apps submitted to the App Store must be built with Xcode 12 and the iOS 14 SDK. Dear Twitpic Community - thank you for all the wonderful photos you have taken over the years. We have now placed Twitpic in an archived state.
Development Tools and Libraries
CRAN R 4.0.0 builds and higher no longer use any custom compilers and thus this directory is no longer relevant. We now use Apple Xcode 10.1 and GNU Fortran 8.2 from https://github.com/fxcoudert/gfortran-for-macOS/releases.For more details on compiling R, please see alsohttps://mac.R-project.org/tools/Previous tools
The following is provided as support of older versions of R. If you use R 4.0.0 or higher, please disregard and read the top section.R 3.5.0-3.6.3 El Capitan binaries and higer were using more recent Clang compiler and GNU Fortran 6.1 to provide OpenMP parallelization support and C++17 standard features. If you want to compile R packages from sources, please download GNU Fortran binary from the official GNU Fortran Binaries page - in particular OS X 10.11 gfortran 6.1. Alternatively, we are providing a copy here as well as Clang binaries for OS X 10.11 and higher - see below for the download links.
Files:
clang-8.0.0.pkg (OS X 10.11+, signed, 64-bit) MD5-hash: 664582b0722cb59802cb762b2ad7548b (ca. 482Mb) | Clang 8.0.0 for OS X 10.11 and higher, release build for x86_64, signed package, installs into /usr/local/clang8. To be used with El Capitan builds of R 3.7.0 and higher. It is an installer version of the official LLVM released binaries only modified to use the path above. |
clang-7.0.0.pkg (OS X 10.11+, signed, 64-bit) MD5-hash: cef3fd2a5c165d00f9941f64ea4024f7 (ca. 463Mb) | Clang 7.0.0 for OS X 10.11 and higher, release build for x86_64, signed package, installs into /usr/local/clang7. To be used with El Capitan builds of R 3.6.x. It is an installer version of the official LLVM released binaries only modified to use the path above. |
clang-6.0.0.pkg (OS X 10.11+, signed, 64-bit) MD5-hash: c29700c4e7b2914073ef7e741eb105bc (ca. 418Mb) | Clang 6.0.0 for OS X 10.11 and higher, static build for x86_64, signed package, installs into /usr/local/clang6. To be used with El Capitan builds of R 3.5.x. |
gfortran-6.1.pkg (OS X 10.11+, signed, 64-bit) MD5-hash: 201026216e8b373d9cd2efc0cc474bb8 (ca. 73Mb) | GNU Fortran 6.1 for OS X 10.11 and higher - a copy from GFortranBinaries pages for x86_64, signed package, installs into /usr/local/gfortran (identical content, re-packaged to a flat Installer package and signed). To be used with El Capitan builds of R. |
The following binaries are obsolete and only provided for historical reasons | |
gfortran-4.2.3.pkg (OS X 10.5+, signed, 64-bit driver) MD5-hash: 8783f803038abe6487a362ad5b8995ea (ca. 27MB) gfortran-4.2.3.dmg (OS X 10.4, 32-bit driver) MD5-hash: 9551fc46f55537dd1db581154daf27ef (ca. 27MB) | Universal GNU Fortran 4.2.3 for Mac OS X 10.4 and higher. It is necessary in order to build R packages from sources that contain Fortran code. Unlike many other builds, this is a fully universal build of GNU Fortran that uses Apple's driver and supports all target architectures (i386, ppc, x86_64 and ppc64). As such it fully supports compilation into fat files like gfortran -arch i386 -arch ppc -arch x86_64 -arch ppc64 t.f -o ton both Intel Macs and PowerPC Macs (32- and 64-bit). Dependent libraries are fat as well, avoiding problems known from other Fortran builds (such as those from HPC). It installs in /usr/local and comes with an uninstall-script. |
tcltk-8.5.5-x11.pkg (OS X 10.5+, signed) MD5-hash: e7c406d91762ffdc4539b23c5b5a3ab4 (ca. 9MB) tcltk-8.5.5-x11.dmg (OS X 10.4) MD5-hash: c32dda1b9f2c2776a02cec4e03befc76 (ca. 9MB) | Universal build of Tcl/Tk 8.5.5 for X11 (32-bit and 64-bit). This library is necessary in order to use the tcltk R package (for R 2.8.0 - 2.15.3 only!). It installs in /usr/local. Requires Mac OS X 10.4 (Tiger) or higher for 32-bit R and Mac OS X 10.5 (Leopard) or higher for 64-bit R. NOTE: R 3.0.0 and higher comes bundled with Tck/Tk 8.6.0 so you do not need this package |
For other (optional) 3rd party libraries for development see http://mac.R-project.org/libs/. The devpack has been superseded by those libraries. For R you may want to download and install libpng, libjpeg, readline, freetype, fontconfig, pixman and cairo.
Source code for all 3rd party libraries can be found at http://mac.R-project.org/src/
The dependency libraries used by the CRAN macOS build system are now managed by build recipes. Package authors wishing to add static dependendies can create a pull request to add a dependency.
Subdirectories:
old | Previous versions of tools as supplied with legacy R versions. |
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.
El Capitan Full Download
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! The page also contains links to experimental builds as such 64-bit R for OS X.
Link to corresponding sources: http://mac.R-project.org/src/
Last modified: 2020/04/24, by Simon Urbanek
macOS Big SurBoot from pendrive mac. takes the most advanced operating system in the world to a whole new level of power and beauty, and makes your apps look better than ever. Widgets and the widget gallery help you deliver more value to your users. Adding intelligence to your apps with machine learning is simple with extensive tools, models, training capabilities, and APIs. You can create more powerful Mac versions of your iPad apps with Mac Catalyst. And you can easily bring your extensions to Safari — and to the App Store.
All-new Interface
macOS Big Sur brings a new design that’s been finely tuned for the powerful features that make a Mac a Mac. Core features, such as the menu bar and Dock, take advantage of the large Mac display, with translucent backings and spacious pull-down menus. The new Control Center, designed just for Mac, provides quick access to controls while keeping the menu bar clutter-free. Notification Center puts recent notifications and powerful new widgets together in a single view for at-a-glance information as you work. And a streamlined new design for apps features full-height sidebars and integrated toolbar buttons.
Widgets
Easily build widgets using the WidgetKit framework and the new widget API for SwiftUI. Widgets now come in multiple sizes, and users can visit the new widget gallery to search, preview sizes, and add them to Notification Center to access important details at a glance.
Safari Extensions
With support for the popular WebExtension API, it’s even easier to bring powerful extensions to Safari. Xcode 12 even includes a porting tool to streamline the process.
The new Extensions category on the Mac App Store showcases Safari extensions, with editorial spotlights and top charts to help users discover and download great extensions from the developer community.
Machine Learning
With macOS Big Sur, creating apps that leverage the power of machine learning is even easier and more extensive with additional tools in Core ML for model deployment, new models and training capabilities in Create ML, more APIs for vision and natural language, and improved resources for training on Mac and converting models to Core ML format.
Mac Catalyst
Create even more powerful Mac versions of your iPad apps. Apps built with Mac Catalyst now take on the new look of macOS Big Sur and help you better define the look and behavior of your apps. You can choose to turn off automatic scaling of iPad controls and layout, allowing you to precisely place every pixel on the screen. Provide full control of your app using just the keyboard, take advantage of the updated Photos picker, access more iOS frameworks, and more.
User privacy on the App Store
The Mac App Store helps users better understand apps’ privacy practices. You’ll need to enter your privacy practice details into App Store Connect for display on your product page.
El Capitan Xcode Version 10.13
Tools and resources
Mac El Capitan Xcode Version
Use Xcode 12 and these resources to build apps for macOS Big Sur.
Quickstart
- Install Xcode and the Xcode Command Line Tools
- Agree to Xcode license in Terminal:
sudo xcodebuild -license
- Install MacPorts for your version of the Mac operating system:
Installing MacPorts
MacPorts version 2.7.1 is available in various formats for download and installation (note, if you are upgrading to a new major release of macOS, see the migration info page):
- “pkg” installers for Big Sur, Catalina, and Mojave, for use with the macOS Installer. This is the simplest installation procedure that most users should follow after meeting the requirements listed below. Installers for legacy platforms High Sierra, Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion, Lion, Snow Leopard, Leopard and Tiger are also available.
- In source form as either a tar.bz2 package or a tar.gz one for manual compilation, if you intend to customize your installation in any way.
- Git clone of the unpackaged sources, if you wish to follow MacPorts development.
- The selfupdate target of the port(1) command, for users who already have MacPorts installed and wish to upgrade to a newer release.
Checksums for our packaged downloads are contained in the corresponding checksums file.
The public key to verify the detached GPG signatures can be found under the attachments section on jmr's wiki page. (Direct Link).
Please note that in order to install and run MacPorts on macOS, your system must have installations of the following components:
Apple's Xcode Developer Tools (version 12.2 or later for Big Sur, 11.3 or later for Catalina, 10.0 or later for Mojave, 9.0 or later for High Sierra, 8.0 or later for Sierra, 7.0 or later for El Capitan, 6.1 or later for Yosemite, 5.0.1 or later for Mavericks, 4.4 or later for Mountain Lion, 4.1 or later for Lion, 3.2 or later for Snow Leopard, or 3.1 or later for Leopard), found at the Apple Developer site, on your Mac operating system installation CDs/DVD, or in the Mac App Store. Using the latest available version that will run on your OS is highly recommended, except for Snow Leopard where the last free version, 3.2.6, is recommended.
With Xcode 4 and later, users need to accept the Xcode EULA by either launching Xcode or running:
Apple's Command Line Developer Tools, which can be installed on recent OS versions by running this command in the Terminal:
Older versions are found at the Apple Developer site, or they can be installed from within Xcode back to version 4. Users of Xcode 3 or earlier can install them by ensuring that the appropriate option(s) are selected at the time of Xcode's install ('UNIX Development', 'System Tools', 'Command Line Tools', or 'Command Line Support').
- (Optional) The X11 windowing environment, for ports that depend on the functionality it provides to run. You have multiple choices for an X11 server:
- Install the xorg-server port from MacPorts (recommended).
- The XQuartz Project provides a complete X11 release for macOS including server and client libraries and applications.
- Apple's X11.app is provided by the “X11 User” package on older OS versions. It is always installed on Lion, and is an optional installation on your system CDs/DVD with previous OS versions.
macOS Package (.pkg) Installer
The easiest way to install MacPorts on a Mac is by downloading the pkg or dmg for Big Sur, Catalina, Mojave, High Sierra, Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion, Lion, Snow Leopard, Leopard or Tiger and running the system's Installer by double-clicking on the pkg contained therein, following the on-screen instructions until completion.
This procedure will place a fully-functional and default MacPorts installation on your host system, ready for usage. If needed your shell configuration files will be adapted by the installer to include the necessary settings to run MacPorts and the programs it installs, but you may need to open a new shell for these changes to take effect.
The MacPorts “selfupdate” command will also be run for you by the installer to ensure you have our latest available release and the latest revisions to the “Portfiles” that contain the instructions employed in the building and installation of ports. After installation is done, it is recommended that you run this step manually on a regular basis to to keep your MacPorts system always current:
At this point you should be ready to enjoy MacPorts!
Type “man port” at the command line prompt and/or browse over to our Guide to find out more information about using MacPorts. Help is also available.
Source Installation
If on the other hand you decide to install MacPorts from source, there are still a couple of things you will need to do after downloading the tarball before you can start installing ports, namely compiling and installing MacPorts itself:
- “cd” into the directory where you downloaded the package and run “tar xjvf MacPorts-2.7.1.tar.bz2” or “tar xzvf MacPorts-2.7.1.tar.gz”, depending on whether you downloaded the bz2 tarball or the gz one, respectively.
- Build and install the recently unpacked sources:
- cd MacPorts-2.7.1
- ./configure && make && sudo make install
- cd ../
- rm -rf MacPorts-2.7.1*
These steps need to be perfomed from an administrator account, for which “sudo” will ask the password upon installation. This procedure will install a pristine MacPorts system and, if the optional steps are taken, remove the as of now unnecessary MacPorts-2.7.1 source directory and corresponding tarball.
To customize your installation you should read the output of “./configure --help | more” and pass the appropriate options for the settings you wish to tweak to the configuration script in the steps detailed above.
You will need to manually adapt your shell's environment to work with MacPorts and your chosen installation prefix (the value passed to configure's --prefix flag, defaulting to /opt/local):
- Add ${prefix}/bin and ${prefix}/sbin to the start of your PATH environment variable so that MacPorts-installed programs take precedence over system-provided programs of the same name.
- If a standard MANPATH environment variable already exists (that is, one that doesn't contain any empty components), add the ${prefix}/share/man path to it so that MacPorts-installed man pages are found by your shell.
- For Tiger and earlier only, add an appropriate X11 DISPLAY environment variable to run X11-dependent programs, as Leopard takes care of this requirement on its own.
Lastly, you need to synchronize your installation with the MacPorts rsync server:
Upon completion MacPorts will be ready to install ports!
It is recommended to run the above command on a regular basis to keep your installation current. Type “man port” at the command line prompt and/or browse over to our Guide to find out more information about using MacPorts. Help is also available.
Git Sources
If you are developer or a user with a taste for the bleeding edge and wish for the latest changes and feature additions, you may acquire the MacPorts sources through git. See the Guide section on installing from git.
El Capitan Download Apple
Purpose-specific branches are also available at the https://github.com/macports/macports-base/branches url.
Alternatively, if you'd simply like to view the git repository without checking it out, you can do so via the GitHub web interface.
Selfupdate
If you already have MacPorts installed and have no restrictions to use the rsync networking protocol (tcp port 873 by default), the easiest way to upgrade to our latest available release, 2.7.1, is by using the selfupdate target of the port(1) command. This will both update your ports tree (by performing a sync operation) and rebuild your current installation if it's outdated, preserving your customizations, if any.
Other Platforms
Running on platforms other than macOS is not the main focus of The MacPorts Project, so remaining cross-platform is not an actively-pursued development goal. Nevertheless, it is not an actively-discouraged goal either and as a result some experimental support does exist for other POSIX-compliant platforms such as *BSD and GNU/Linux.
The full list of requirements to run MacPorts on these other platforms is as follows (we assume you have the basics such as GCC and X11):
- Tcl (8.4 or 8.5), with threads.
- mtree for directory hierarchy.
- rsync for syncing the ports.
- cURL for downloading distfiles.
- SQLite for the port registry.
- GNUstep (Base), for Foundation (optional, can be disabled via configure args).
- OpenSSL for signature verification, and optionally for checksums. libmd may be used instead for checksums.
Xcode For El Capitan Download
Normally you must install from source or from an git checkout to run MacPorts on any of these platforms.
Help
Apple Download El Capitan Installer
Help on a wide variety of topics is also available in the project Guide and through our Trac portal should you run into any problems installing and/or using MacPorts. Of particular relevance are the installation & usage sections of the former and the FAQ section of the Wiki, where we keep track of questions frequently fielded on our mailing lists.
Xcode El Capitan Download Dmg
If any of these resources do not answer your questions or if you need any kind of extended support, there are many ways to contact us!
Comments are closed.