[X2Go-Commits] page changed: wiki:development:build-howto-macos:x2goclient

[wiki-admin at x2go.org]

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2013/09/26 12:04
Browser     : Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Firefox/23.0
IP-Address  : 188.195.64.106
Hostname    : 188-195-64-106-dynip.superkabel.de
Old Revision: http://wiki.x2go.org/doku.php/wiki:development:build-howto-macos:x2goclient?rev=1380189691
New Revision: http://wiki.x2go.org/doku.php/wiki:development:build-howto-macos:x2goclient
Edit Summary: removed my name from homebrew section, cleaned up macports section
User        : neverpanic

@@ -1,66 +1,62 @@
  ====== Building X2Go Client on Mac OS ======
  
  ===== Build/Install X2Go Client using Homebrew =====
  
- As X2Go Client and it's dependencies are already in Homebrew (thanks to Clemens Lang and Eugene San).
+ As X2Go Client and it's dependencies are already in Homebrew (thanks to Eugene San).
  
  We assume you've already installed Homebrew.
  If not please invoke:<code>$ ruby -e "$(curl -fsSL
https://raw.github.com/mxcl/homebrew/go)"</code>
  For more information regarding Homebrew head to http://brew.sh
  
  It is possible to install X2goClient in one command: <code>$ brew install x2goclient</code>
  
- ===== Build X2Go Client using Mac Ports =====
+ ===== Build X2Go Client using MacPorts =====
  
- As X2Go Client is already in Mac Ports (thanks to Clemens Lang) it is possible to install all dependencies via Mac Ports.
+ X2Go Client is available from MacPorts, maintained by Clemens Lang, who currently also build the official X2Go Client DMGs.
+ 
+ If you just want to get a working version of X2Go Client you can run <code>$ sudo port install x2goclient</code>.
+ 
+ If you want to build a re-distributable DMG image such as the one available from the website, follow these steps (assuming you already have MacPorts installed):
  
  **Steps summarized:**
  
-   - Install Mac Ports on your Mac OS system
-   - Take a look at the dependency list (in a terminal shell)
-   - And
install those dependencies
-   - Install dylibbundler
+   - Install the dependencies for X2Go Client
+   - Install the build-time dependency dylibbundler
    - Get X2Go Client from X2Go Git
-   - Build X2Go Client
+   - Build X2Go Client DMG image
  
- So, first install the X2Go Client dependencies:
+ So, first install the X2Go Client dependencies and dylibbundler:
  
  <code>
- $ port echo depof:x2goclient
- $ sudo port install depof:x2goclient
- </code>
- 
- Then install dylibbundler:
- 
- <code>
- $ sudo port install dylibbundler
+ $ sudo port install depof:x2goclient dylibbundler
  </code>
  
  Once the dependencies are installed, tweak some file permissions:
  
  <code>
  $ sudo chmod u+w /opt/local/lib/libcrypto.1.0.0.dylib /opt/local/lib/libssl.1.0.0.dylib
  </code>
  
- If you omit the file permission tweak, dylibbundler will fail to build/bundle X2Go Client.
+ If you omit the file permission tweak, dylibbundler will fail to bundle OpenSSL with X2Go Client.
  
  At last,
checkout X2Go Client from Git:
  <code>
  $ git clone git://code.x2go.org/x2goclient.git
  </code>
  
  If you want to build a specific version of X2Go Client, select that version with ''git checkout <version>''. If you want to look around what versions are available, use ''git tag'' which will present you a list of valid version tags to use for checkout.
-       
- In the X2Go Client source directory, simply run the ''macbuild.sh'' script:
+ 
+ In the X2Go Client source directory, simply run the ''macbuild.sh'' script. Depending on your OS and your needs, you might want to adjust the lines mentioning <code>QMAKE_MAX_SDK</code>, <code>QMAKE_MACOSX_DEPLOYMENT_TARGET</code> and the <code>CONFIG</code> line that contains the target architectures. Once done, run
  
  <code>
  $ ./macbuild.sh
  </code>
  
+ to generate <code>x2goclient.dmg</code>.
       
  ===== Build X2Go Client from Scratch (w/o Mac Ports) =====
-                    
+ 
  ==== Variables ====
  
  This document makes
use of several variables to address paths in a generic, but distinct way. They are not meant to be used via shell, but for human parsing. No program of the x2go suite actually uses them for anything. You may "set" them to whatever value you want to (in your head), just don't change them half-way through the building process. The "default value" is merely a suggestion.
  



-- 
This mail was generated by DokuWiki at
http://wiki.x2go.org/