[MacPorts] KDEProblems/KDEMacPortsCI/Status modified
MacPorts
noreply at macports.org
Thu May 22 16:25:45 PDT 2014
Page "KDEProblems/KDEMacPortsCI/Status" was changed by mk at macports.org
Diff URL: <https://trac.macports.org/wiki/KDEProblems/KDEMacPortsCI/Status?action=diff&version=3>
Revision 3
Comment: Restructuring page for use of sections instead of ordered list
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: KDEProblems/KDEMacPortsCI/Status
=========================================================================
--- KDEProblems/KDEMacPortsCI/Status (version: 2)
+++ KDEProblems/KDEMacPortsCI/Status (version: 3)
@@ -1,30 +1,62 @@
= Current status of setting up the CI system (still hanging on OSX up to now) =
-This is what has to be done to get a KDE/CI system up and running on OSX (partially by also using MacPorts):
+This page shall describe what has to be done to get a KDE/CI system up and running on OSX. Partially this is achieved by using a few port from MacPorts.
+
+
- A) Start with fresh Mavericks install and make sure your disk has at least 20G free space left
+== Start with fresh Mavericks install ==
- B) Install MacPorts 2.2.1 using the official PKG
+ * make sure your disk has at least 20G free space left
- C) Install ports for bash use:
+
+
+== Install MacPorts ==
+
+ * currently using the official PKG for MacPorts version 2.2.1
+
+
+
+== bash and environment ==
+
+Install ports for MacPorts' bash
{{{
$ sudo port install bash bash-completion
}}}
+and set up the [https://projects.kde.org/projects/playground/sdk/macports-kde/repository/revisions/master/show/contrib/user-setup bash environment for MacPorts use] regarding search paths (PATH, MANPATH)
- D) Set up [https://projects.kde.org/projects/playground/sdk/macports-kde/repository/revisions/master/show/contrib/user-setup bash environment for MacPorts use] regarding search paths (PATH, MANPATH)
- E) Install Xcode from AppStore (and agree actively to the developer license agreement)
- F) Install developer command line tools and install some of MacPorts' ports needed for later
+== Apple developer tools ==
+
+Install
+ * Xcode from AppStore (and agree actively to the developer license agreement)
+ * developer command line tools
{{{
$ xcode-select --install
+}}}
+
+
+
+== Tools already present on OSX ==
+
+Some tools are already installed on OSX due to Xcode (like git, svn, ssh, rsync, make, clang etc.) they don't need to be installed via MacPorts for now.
+Should a more up-to-date version of any one of these be necessary for the CI system it could be added later.
+
+
+
+== Some of more software supplied by MacPorts ==
+
+Install ports needed for the CI scripts:
+{{{
$ sudo port install py27-lxml bazaar mercurial wget automake autoconf
}}}
- Installing bazaar brings the also needed port gnutar into the system!
+Installing bazaar brings the also needed port gnutar into the system!
- G) Since some tools are already installed on OSX due to Xcode (like git, svn, ssh, rsync, make, clang etc.) they don't need to be installed via MacPorts for now
- H) Create some folders, clone and update KDE's CI system (assuming a user "kdeci" with its home directory "/Users/kdeci"):
+
+== Basic setup of CI system ==
+
+Create some folders, clone and update KDE's CI system (assuming a user "kdeci" with its home directory "/Users/kdeci"):
{{{
$ cd
$ mkdir -p WC/KDECI-build;
@@ -34,9 +66,15 @@
$ git checkout production
$ ./update-setup.sh # Ignore 404 occurring due to error cloning ECMA262 by hg
}}}
- The update shell script created a folder {{{~/scripts}}} in which subsequent commands will have to be executed.
+The update shell script created a folder {{{~/scripts}}} in which subsequent commands will have to be executed.
- I) Prepare environment for Qt5 build (set correct path to kde install directory in config/build/darwin-mavericks.cfg):
+
+== 1st step: Qt5 build ==
+
+
+=== Prepare environment for Qt5 build ===
+
+Install additional ports specific for Qt5, set correct path to KDE-install directory in config/build/darwin-mavericks.cfg:
{{{
$ sudo port install dbus libmng libpng mysql55 pkgconfig sqlite2 tiff
$ sudo port uninstall cmake # Remove MacPorts' cmake (which came into the system as build-dependency for mysql55)
@@ -55,20 +93,24 @@
$
}}}
- J) Set up build environment:
+
+
+=== Set up build environment for Qt5 ===
+
+Make sure all libs can be found by adding search paths and avoid inclusion of MacPorts' glib2:
{{{
$ cd ~/scripts; cat config/build/qt5/darwin-mavericks.cfg
[Build]
-configureCommand=%(configureExecutable)s -release -system-zlib -system-libpng -system-libjpeg -system-sqlite -dbus -plugin-sql-mysql -nomake examples -confirm-license -opensource -prefix {instPrefix} -no-framework -v -I/opt/local/include -L/opt/local/lib
+configureCommand=%(configureExecutable)s -release -system-zlib -system-libpng -system-libjpeg -system-sqlite -dbus -plugin-sql-mysql -nomake examples -confirm-license -opensource -prefix {instPrefix} -no-framework -v -I/opt/local/include -L/opt/local/lib -no-glib
}}}
- Consider here the use of options "{{{-debug -separate-debug-info}}}" instead of "{{{-release}}}".
+Consider here the use of options "{{{-debug -separate-debug-info}}}" instead of "{{{-release}}}".
- K) Include MySQL's binary path into PATH (assuming /opt/local as MacPort's prefix):
+Include MySQL's binary path into PATH e.g. in {{{.macports/profile}}} (assuming /opt/local as MacPort's prefix):
{{{
export PATH=/opt/local/lib/mysql55/bin:$PATH
}}}
- L) Set up SSH for rsync access to build host, then start building Qt5:
+Set up SSH for rsync access to build host, then start building Qt5:
{{{
$ cat ~/.ssh/config
Host build.kde.org
@@ -78,7 +120,11 @@
...
}}}
- M) Proceed with installation of cmake (needs manual checkout of sources):
+
+
+== Installation of cmake ==
+
+Cmake needs a manual checkout of its sources:
{{{
$ python2.7 tools/prepare-environment.py --project cmake --branchGroup kf5-qt5 --platform darwin-mavericks --sources ~/WC/KDECI-build/cmake
...
@@ -87,21 +133,23 @@
...
}}}
- N) Installation of other projects and KDE frameworks:
- The various frameworks have to be handled by replacing "PROJECT" with the framework's project name:
+
+== Installation of other projects and KDE frameworks ==
+
+The various frameworks have to be handled by replacing "PROJECT" with the framework's project name:
{{{
$ python2.7 tools/prepare-environment.py --project PROJECT --branchGroup kf5-qt5 --platform darwin-mavericks --sources ~/WC/KDECI-build/PROJECT
...
$ python2.7 tools/perform-build.py --project PROJECT --branchGroup kf5-qt5 --platform darwin-mavericks --sources ~/WC/KDECI-build/PROJECT
...
}}}
- which has been successfully done so far for:
+which has been successfully done so far for:
{{{
- extra-cmake-modules
}}}
- Problems currently appear for:
+Problems currently appear for:
{{{
- polkit-qt-1 (still fails due to inability to find package Polkit - this is still Linux-specific and needs to be fixed for use on OSX):
}}}
-------8<------8<------8<------8<------8<------8<------8<------8<--------
--
Page URL: <https://trac.macports.org/wiki/KDEProblems/KDEMacPortsCI/Status>
MacPorts <http://www.macports.org/>
Ports system for OS X
This is an automated message. Someone added your email address to be
notified of changes on 'KDEProblems/KDEMacPortsCI/Status' page.
If it was not you, please report to .
More information about the macports-changes
mailing list