Install Xquartz Homebrew

Posted onby admin

How use lidar data with QGIS for Mac with the LASTools package This tutorial presupposes you have installed QGIS for Mac. If not, full instructions and downloads are available on the KyngChaos page. Any one guide me, How install Homebrew on windows OS, following command is not work on window terminal ruby -e '$(curl -fsSL https://raw.githubus. I just bought MechaNika today and as soon as I started it, a message popped up from X11 saying 'To open 'MechaNika,' you need to install X11. Would you like to install X11 now?' I was confused at. 我正在尝试在OS X上安装Homebrew。根据Homebrew网站,我应该键入brew install wget,而我得到的只是-bash:brew:命令未找到,所以我搜索了StackOverflow并找到了.

About the App

  • App name: XQuartz
  • App description: xquartz (App: XQuartz.pkg)
  • App website: http://xquartz.macosforge.org/

Install the App

  1. Press Command+Space and type Terminal and press enter/return key.
  2. Run in Terminal app:
    ruby -e '$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)' < /dev/null 2> /dev/null ; brew install caskroom/cask/brew-cask 2> /dev/null
    and press enter/return key.
    If the screen prompts you to enter a password, please enter your Mac's user password to continue. When you type the password, it won't be displayed on screen, but the system would accept it. So just type your password and press ENTER/RETURN key. Then wait for the command to finish.
  3. Run:
    brew cask install xquartz

Done! You can now use XQuartz.

Similar Software for Mac

IMPORTANT: This page might be obsolete. Please refer to https://www.enlightenment.org/distros/osx-start for an up-to-date documentation.

The Enlightenment Foundation's projects mostly targets Linux platforms, therefore not everything work on Mac OS X (Darwin kernel) works the first time. This is due to:

  • the specificities of the OS
  • there are a very few Enlightened OS X users :'(

This document explains how to install the EFL/Elementary which are key projects to install anything else made by the Enlightenment Foundation. It also shows what does not work on OS X that does on Linux.

Issues (non-exhaustive list)

Install X11 Mac

  • Cserve is disabled (untested?)
  • OpenSSL is deprecated (http://stackoverflow.com/questions/7406946/why-is-apple-deprecating-openssl-in-macos-10-7-lion)
  • Eeze is not compatible OS X (because it relies on udev)
  • E cannot complete its initialization

Packaging

Set the environment up

You need to have the OS X CLT (Command-Line Tools) first, then install the dependancies. The easiest way is by using a package manager. There are (mostly) two flavours about package managers on OS X: macports and homebrew. You should choose only one of them, it is not recommended to use both.

NOTE: I personally recommend homebrew over macports (more flexible, easier to use, less conflicts — imho).

Command-Line Tools (CTL)

WARNING: The CTL are not directly installed with Xcode.
  • Download the latest version of Xcode on the Mac App Store.
  • Run xcode-select --install in a terminal to install the CLT.

XQuartz

Since OSX 10.7, Apple does not support X11, therefore you have to download it by yourself: download the .dmg at http://xquartz.macosforge.org/landing/ and follow the installation procedure. Currently, the EFL do not fully support the native Cocoa display; it is therefore necessary to use X11 for the moment.

Install in one go from a package manager

Since mid-April 2015, Leif Middelschulte provided Homebrew formulas for :

  • EFL 1.14.0
  • Elementary 1.14.0
  • evas-generic-loaders 1.14.0

If you want to install these stable versions peacefully, this is the solution you are looking for.

See at http://brew.sh how to install Homebrew if it isn't already installed.
Then, just execute :

Build code from sources

If you want to have the very latest (maybe unstable) version of EFL, Elementary, here is the procedure :

  • how to install the dependancies;
  • how to configure the source;
  • how to compile the sources and install them.

Dependancies with macports

A standard usage of Macports makes the configure options --disable-lua-old and --enable-nls fail! The following has been experienced using the macports procedure by using luajit (2.0.3) and the option --enable-nls. During the make update-po, the xgettext_wrapper.sh scripts launches a lua program with Elua. It exits with error 141. The problem is fixed by using lua instead of luajit (--enable-lua-old). For now, I recommend to disable nls (--disable-nls) if you don't need it.
Homebrew

I would recommand to set some environment variables as it follows (I assume you will use a standard installation of macports then):

If you don't know what to do with these variables, just add them at the end of your ~/.profile file.

To install macports, just go here: https://www.macports.org/install.php and download the .pkg for your version of OSX. Follow the installation procedure, and restart your terminal if it was open (or do a source ~/.profile).

Let's update macports first:

Xquartz
IMPORTANT: If lua is already installed with macports (and with default settings), you may not want to install luajit in the following list. Indeed, by default, the lua package has the brilliant (yes, this is sarcasm) idea to install its headers in the ${MACPORTS_ROOT}/include/ directory whereas luajit is installed in ${MACPORTS_ROOT}/include/luajit-${luajit-version}. Since their headers have the same names, lua is always used in place of luajit, and eventually, a linker error occurs...

Then, let's install everything in one go:

Install Xquartz Homebrew

During the process, macports installs also dbus. To activate dbus at startup, just run (as macports suggests):

Dependancies with Homebrew

See the installation procedure here: http://brew.sh.
It is not recommended to install the packages as root (but homebrew will make you know it).

Then, launch dbus:

Install Xquartz Homebrew

You need to add autopoint to your $PATH if you want to use gettext:

Install the EFL

Installing dependancies on OS X is painful, but now you did it (congrats'), you can grab the sources from the git repository:

Standard installation

You will have a safe (understand working out of the box) installation if you run (of course, after a cd /where/you/have/downloaded/efl):

NOTE: Be aware that all files to be installed will be located in /usr. Btw, it seems homebrew does not really like when you put your files in /usr/local (its default root).
IMPORTANT: On OS X El Capitan (10.11), you can not use --prefix=/usr (use --prefix=/usr/local instead). This is due to the 'System Integrity Protection' (https://support.apple.com/en-us/HT204899). It is discouraged to disable this.

Cocoa port

To render windows and stuff, the EFL use Engines written in the Ecore library. The Ecore_Cocoa engine aims at using the Cocoa environment to create the GUI. It is under developement for now, and at a very early stage, so the applications will not be functional. If you would like to contribute to it (or just to test it), then you are welcome to configure the sources as it follows by adding --enable-cocoa flags to your ./autogen.sh or ./configure. Note that you can disable X11 by using the flag --with-x11=none.

Compile and install

If everything went OK, you should be able to compile the sources:

or to do it way, way faster:

then, if once again, everything went OK, install:

Enlightenment (E)

E cannot yet be run (can be compiled though) on OS X. XComposite is not available with XQuartz; therefore, init fails when compositor is queried.

Enlightenment relies on Eeze, but this dependency can be skipped.
First init the autotools:

Then compile:

Extras

This section is not specific to OS X. However, these are good basis to try out the Ecore_Cocoa engine.

Terminology

You might want to give a try to this terminal emulator (http://enlightenment.org/p.php?p=about/terminology&l=en).

Runtime engine selection

If you decided to support Ecore_Cocoa for development purpose (God bless you), it will be used by default when running a graphical application (unless stated otherwise in the elementary_config program). You can select the engine in an environment variable: