* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml
@ 2009-11-15 14:22 Alex Alexander (wired)
0 siblings, 0 replies; 11+ messages in thread
From: Alex Alexander (wired) @ 2009-11-15 14:22 UTC (permalink / raw
To: gentoo-commits
wired 09/11/15 14:22:33
Added: qt4-based-ebuild-howto.xml
Log:
qt4 ebuild how-to - copied from kde project space for now
Revision Changes Path
1.1 xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.1&content-type=text/plain
Index: qt4-based-ebuild-howto.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.1 2009/11/15 14:22:33 wired Exp $ -->
<guide link="/proj/en/desktop/kde/qt4-ebuild-howto.xml" lang="en">
<title>Qt4-based Ebuild HowTo</title>
<author title="Author">
<mail link="hwoarang@gentoo.org">Markos Chandras</mail>
</author>
<abstract>
This guide is intented to give an overview of how to create a Qt4-based ebuild. It will assist users to write proper ebuilds for Qt4 based packages. using Gentoos' qt4 eclass and splitted Qt4 dependencies
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
<version>0.4</version>
<date>2009-06-26</date>
<chapter>
<title>Choosing eclass and EAPI version</title>
<section>
<title>Valid EAPI version</title>
<body>
<p>The first step for your shiny Qt4-based ebuild, is to specify the right EAPI. Current eclass is EAPI 2 compatible,
so all you need to do is</p>
<pre caption="Specify correct EAPI version">
EAPI="2"
</pre>
<p>That was the most important step for your ebuild.</p>
</body>
</section>
<section>
<title>Inherit qt4 eclass</title>
<body>
<p>All qt4 based ebuilds, can use qt4 eclass which provides usefull tools and operation (listed below) for building qt4 applications.</p>
<pre caption="Inherit qt4 eclass">
inherit qt4
</pre>
</body>
</section>
</chapter>
<chapter>
<title>Dependencies and Use flags</title>
<section>
<title>Depend on qt4 split packages</title>
<body>
<p>Since Qt-4.4.0, Gentoo Qt team, splits monolithic Qt4 package into smaller packages. Those are</p>
<ul>
<li> x11-libs/qt-assistant</li>
<li> x11-libs/qt-core</li>
<li> x11-libs/qt-dbus</li>
<li> x11-libs/qt-demo</li>
<li> x11-libs/qt-gui</li>
<li> x11-libs/qt-opengl</li>
<li> x11-libs/qt-phonon</li>
<li> x11-libs/qt-qt3support</li>
<li> x11-libs/qt-script</li>
<li> x11-libs/qt-sql</li>
<li> x11-libs/qt-svg</li>
<li> x11-libs/qt-test</li>
<li> x11-libs/qt-webkit</li>
<li> x11-libs/qt-xmlpatterns</li>
</ul>
<p>Now all you need to do, is to specify the correct modules on DEPEND variable</p>
<pre caption="Simple example to demonstrate proper qt4 split dependencies usage">
DEPEND="x11-libs/qt-gui:4
x11-libs/qt-sql:4"
</pre>
<warn>
Even though there is a qt4 metapackage, you must NOT use it as a dependency.
</warn>
</body>
</section>
<section>
<title>Debug and Release scope</title>
<body>
<p>Qt offers you the ability to build your applications using two different modes:</p>
<ul>
<li>Release: Leads to smaller binaries, usefull for the production state.</li>
<li>Debug: Leads to bigger binaries, usefull for debugging during development process.</li>
</ul>
<p>Thus, qt4 eclass can use the 'debug' use flag in order to build your application with debug symbols.</p>
<pre caption="Add 'debug' use flag">
IUSE="debug"
</pre>
<p>In case 'debug' use flag is present on IUSE, you must adjust the qt dependencies accordingly</p>
<pre caption="Adjusted qt4 dependencies">
DEPEND="x11-libs/qt-gui:4[debug?]
x11-libs/qt-sql:4[debug?]"
</pre>
<impo>
'debug' use flag usage implies that you have already followed the <uri link="/proj/en/qa/backtraces.xml">
"How to get meaningful backtraces in Gentoo"</uri> tutorial.
</impo>
</body>
</section>
</chapter>
<chapter>
<title>Preparing the package</title>
<section>
<title>src_prepare function</title>
<body>
<p>EAPI2 introduced the src_prepare function which is executed right after src_unpack. The default implementation does nothing.
Most of the time, you wont need to use this function at all. Patches are applied automatically via autopatcher</p>
</body>
</section>
<section>
<title>Applying patches</title>
<body>
<p>Qt4 eclass uses the base eclass autopatcher in order to apply patches. All you have to do is to specify which patches
you want to apply using PATCHES variable</p>
<pre caption="Simple example for using PATCHES variable">
PATCHES=(
"${FILESDIR}/fixconfig.patch"
"${FILESDIR}/fixgui.patch"
)
</pre>
<impo>
Please note that PATCHES is an array, so you will always need to includes patches between parenthesis.
</impo>
</body>
</section>
</chapter>
<chapter>
<title>Configure the sources</title>
<section>
<title>The 'magic' eqmake4 tool</title>
<body>
<p>We provide a special function for configuring Qt4 project files. That is eqmake4 which is provided by qt4 eclass. It is based on qmake, plus it uses
default Qt variables for proper package configuration. Packages should be configured under src_configure function.</p>
<pre caption="Simple example for src_configure function">
src_configure() {
eqmake4
}
</pre>
<impo>
eqmake4 does not need a 'die' statement.
</impo>
<p>There are some rare occasions where eqmake4 fails, but qmake works. Please fill a <uri link="http://bugs.gentoo.org">bug</uri> about this in order to take care
of it</p>
</body>
</section>
</chapter>
<chapter>
<title>Installation</title>
<section>
<title>src_install function</title>
<body>
<p>Most Qt4 packages use INSTALL_ROOT variable instead of DESTDIR on their Makefiles. Make sure not to use DESTDIR on src_install,
otherwise you will end up with Access violation errors.
Below there is an example src_install for most Qt4 packages</p>
<pre caption="Simple example for src_install function">
src_install() {
emake INSTALL_ROOT="${D}" install || die "emake install failed"
dodoc README AUTHORS || die "dodoc failed"
}
</pre>
</body>
</section>
</chapter>
</guide>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml
@ 2009-12-20 19:28 Markos Chandras (hwoarang)
0 siblings, 0 replies; 11+ messages in thread
From: Markos Chandras (hwoarang) @ 2009-12-20 19:28 UTC (permalink / raw
To: gentoo-commits
hwoarang 09/12/20 19:28:18
Modified: qt4-based-ebuild-howto.xml
Log:
Update tutorial to match qt4-r2 eclass now
Revision Changes Path
1.2 xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?r1=1.1&r2=1.2
Index: qt4-based-ebuild-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- qt4-based-ebuild-howto.xml 15 Nov 2009 14:22:33 -0000 1.1
+++ qt4-based-ebuild-howto.xml 20 Dec 2009 19:28:18 -0000 1.2
@@ -1,45 +1,77 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.1 2009/11/15 14:22:33 wired Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.2 2009/12/20 19:28:18 hwoarang Exp $ -->
<guide link="/proj/en/desktop/kde/qt4-ebuild-howto.xml" lang="en">
-<title>Qt4-based Ebuild HowTo</title>
+<title>Qt4-based ebuild howto</title>
<author title="Author">
- <mail link="hwoarang@gentoo.org">Markos Chandras</mail>
+ <mail link="hwoarang" />
+</author>
+
+<author title="Author">
+ <mail link="ayoy" />
</author>
<abstract>
-This guide is intented to give an overview of how to create a Qt4-based ebuild. It will assist users to write proper ebuilds for Qt4 based packages. using Gentoos' qt4 eclass and splitted Qt4 dependencies
+This guide is intented to give an overview of how to create a Qt4-based ebuild. It will assist users to write proper ebuilds for Qt4 based packages using Gentoos' qt4-r2 eclass and split Qt4 dependencies.
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>0.4</version>
-<date>2009-06-26</date>
+<version>0.5</version>
+<date>2009-12-20</date>
<chapter>
- <title>Choosing eclass and EAPI version</title>
+ <title>Introduction</title>
+ <section>
+ <title>Purpose of this howto</title>
+ <body>
+ <p>The goal of this document is to introduce qt4-r2 eclass and provide basic instructions on writing ebuilds for applications that use Qt 4 qmake build system. If you're writing an ebuild for a Qt-based application that uses cmake as a build system, you would like to take a look at cmake-utils eclass instead.</p>
+ </body>
+ </section>
+</chapter>
+<chapter>
+ <title>Required variables, inheriting eclass and EAPI version</title>
+ <section>
+ <title>Inherit qt4-r2 eclass</title>
+ <body>
+ <p>All Qt 4 qmake-based ebuilds should use qt4-r2 eclass which provides usefull tools and features (listed below) for building Qt 4 applications.</p>
+ <pre caption="Inheriting qt4-r2 eclass">
+inherit qt4-r2</pre>
+ <warn>
+ There is an old qt4 eclass in the tree. It's deprecated since 15 December 2009. Please use qt4-r2 eclass instead since we plan to drop the old eclass. If you already maintain a Qt4 ebuild which uses qt4 eclass, please consider migrate to the new eclass as soon as possible.
+ </warn>
+ </body>
+ </section>
<section>
<title>Valid EAPI version</title>
<body>
- <p>The first step for your shiny Qt4-based ebuild, is to specify the right EAPI. Current eclass is EAPI 2 compatible,
- so all you need to do is</p>
+ <p>The next step for your shiny Qt4-based ebuild, is to specify the right EAPI. Current eclass is compatible with EAPI 2 <b>only</b>,
+ so you have to use it when inheriting qt4-r2 eclass.</p>
<pre caption="Specify correct EAPI version">
-EAPI="2"
- </pre>
+EAPI="2"</pre>
<p>That was the most important step for your ebuild.</p>
</body>
</section>
<section>
- <title>Inherit qt4 eclass</title>
+ <title>Language variables</title>
<body>
- <p>All qt4 based ebuilds, can use qt4 eclass which provides usefull tools and operation (listed below) for building qt4 applications.</p>
- <pre caption="Inherit qt4 eclass">
-inherit qt4
- </pre>
+ <p>
+ In case your ebuild provides translations, you should populate the IUSE variable with appropriate <c>linguas_*</c> USE flags. When writing ebuild it's common to group language codes that are parts of translation files' names in a variable that is later used to iterate over translations when configuring and/or installing the package.</p>
+ <p>qt4-r2 eclass provides two special variables for this purpose. <c>LANGS</c> and <c>LANGSLONG</c> are meant to ease up <c>linguas_*</c> USE flags population. All you have to do is set <c>LANGS</c> to a list of translations languages for your package (using language codes as specified in <path>${PORTDIR}/profiles/desc/linguas.desc</path>).</p>
+ <p>Some applications provide translation files with languages specified together with a country code (e.g. <path>myapp_de_DE.ts</path>). That's not always the proper solution from Gentoo point of view, since e.g. "de_DE" is an invalid <c>LINGUAS</c> member. If your package's translations files contain language codes incompatible with those used by Gentoo, the <c>LANGSLONG</c> variable might help you a bit. It will cut off the country code from the language when populating <c>linguas_*</c> IUSE. This way you can use an incompatible language code to refer to the translation file, but still you're sure that <c>linguas_*</c> use flag is specified correctly.</p>
+ <pre caption="Example of defining languages">
+LANGS="de es fr_CA hu pt_BR zh_CN"
+LANGSLONG="cs_CZ fr_FR pl_PL"</pre>
+ <p>This example results in the following IUSE set:</p>
+ <pre caption="Resulting IUSE">
+IUSE="linguas_cs linguas_de linguas_es linguas_fr linguas_fr_CA linguas_hu linguas_pl linguas_pt_BR linguas_zh_CN"</pre>
+ <impo>
+ In order for automatic <c>linguas_*</c> IUSE generation to work, <c>LANGS</c> and <c>LANGSLONG</c> <b>must</b> be set before inheriting qt4-r2 eclass.
+ </impo>
</body>
</section>
</chapter>
@@ -56,6 +88,7 @@
<li> x11-libs/qt-dbus</li>
<li> x11-libs/qt-demo</li>
<li> x11-libs/qt-gui</li>
+ <li> x11-libs/qt-multimedia</li>
<li> x11-libs/qt-opengl</li>
<li> x11-libs/qt-phonon</li>
<li> x11-libs/qt-qt3support</li>
@@ -69,10 +102,9 @@
<p>Now all you need to do, is to specify the correct modules on DEPEND variable</p>
<pre caption="Simple example to demonstrate proper qt4 split dependencies usage">
DEPEND="x11-libs/qt-gui:4
- x11-libs/qt-sql:4"
- </pre>
+ x11-libs/qt-sql:4"</pre>
<warn>
- Even though there is a qt4 metapackage, you must NOT use it as a dependency.
+ Even though there is a <c>x11-libs/qt</c> metapackage, you <b>must NOT</b> use it as a dependency.
</warn>
</body>
</section>
@@ -85,15 +117,9 @@
<li>Release: Leads to smaller binaries, usefull for the production state.</li>
<li>Debug: Leads to bigger binaries, usefull for debugging during development process.</li>
</ul>
- <p>Thus, qt4 eclass can use the 'debug' use flag in order to build your application with debug symbols.</p>
+ <p>Thus, qt4-r2 eclass can use the 'debug' use flag in order to build your application with debug symbols.</p>
<pre caption="Add 'debug' use flag">
- IUSE="debug"
- </pre>
- <p>In case 'debug' use flag is present on IUSE, you must adjust the qt dependencies accordingly</p>
- <pre caption="Adjusted qt4 dependencies">
- DEPEND="x11-libs/qt-gui:4[debug?]
- x11-libs/qt-sql:4[debug?]"
- </pre>
+IUSE="debug"</pre>
<impo>
'debug' use flag usage implies that you have already followed the <uri link="/proj/en/qa/backtraces.xml">
"How to get meaningful backtraces in Gentoo"</uri> tutorial.
@@ -101,6 +127,16 @@
</body>
</section>
+ <section>
+ <title> Package documentation</title>
+ <body>
+ <p>There is a special variable to use in case your package provides document files. <b>DOCS</b> variable can be used by the <uri link="#doc_chap5_pre1">default src_install function</uri> to install those documents. Normally the documents are located on "${S}" directory. If not, set the <b>DOCSDIR</b> variable to match the documents path. If you don't need to use DOCSDIR variable, then "${S} will be used by default.</p>
+ <pre caption="simple example of DOCS variable usage">
+DOCSDIR="${S}/docs/"
+DOCS="Authors ChangeLog Readme"</pre>
+ </body>
+ </section>
+
</chapter>
<chapter>
@@ -108,8 +144,7 @@
<section>
<title>src_prepare function</title>
<body>
- <p>EAPI2 introduced the src_prepare function which is executed right after src_unpack. The default implementation does nothing.
- Most of the time, you wont need to use this function at all. Patches are applied automatically via autopatcher</p>
+ <p>EAPI2 introduced the src_prepare function which is executed right after src_unpack. The default implementation does nothing.</p>
</body>
</section>
<section>
@@ -119,10 +154,9 @@
you want to apply using PATCHES variable</p>
<pre caption="Simple example for using PATCHES variable">
PATCHES=(
- "${FILESDIR}/fixconfig.patch"
- "${FILESDIR}/fixgui.patch"
-)
- </pre>
+ "${FILESDIR}/fixconfig.patch"
+ "${FILESDIR}/fixgui.patch"
+)</pre>
<impo>
Please note that PATCHES is an array, so you will always need to includes patches between parenthesis.
</impo>
@@ -135,17 +169,17 @@
<section>
<title>The 'magic' eqmake4 tool</title>
<body>
- <p>We provide a special function for configuring Qt4 project files. That is eqmake4 which is provided by qt4 eclass. It is based on qmake, plus it uses
- default Qt variables for proper package configuration. Packages should be configured under src_configure function.</p>
+ <p>We provide a special function for configuring Qt4 project files. That is eqmake4 which is provided by qt4-r2 eclass. It is based on qmake, plus it uses
+ default Qt variables for proper package configuration. Packages should be configured under src_configure function.
+ The <b>default src_configure phase</b> finds and configures project files ( *.pro files ) located on ${S} directory. If there are more than one project files in there, it will try to find the one named ${PN}.pro or $(basename ${PWD}).pro. In case, your package uses some weird file hieracy and you need to configure a project file on a subfolder, then you can specify the path as a parameter on eqmake4.</p>
<pre caption="Simple example for src_configure function">
src_configure() {
- eqmake4
-}
- </pre>
+ eqmake4 "${S}"/tool/foo.pro
+}</pre>
<impo>
eqmake4 does not need a 'die' statement.
</impo>
- <p>There are some rare occasions where eqmake4 fails, but qmake works. Please fill a <uri link="http://bugs.gentoo.org">bug</uri> about this in order to take care
+ <p>There are some rare occasions where eqmake4 fails, but qmake works. Please file a <uri link="http://bugs.gentoo.org">bug</uri> about this in order to take care
of it</p>
</body>
</section>
@@ -156,15 +190,32 @@
<section>
<title>src_install function</title>
<body>
- <p>Most Qt4 packages use INSTALL_ROOT variable instead of DESTDIR on their Makefiles. Make sure not to use DESTDIR on src_install,
- otherwise you will end up with Access violation errors.
- Below there is an example src_install for most Qt4 packages</p>
- <pre caption="Simple example for src_install function">
+ <p>
+ The <b>default src_install function</b> n qt4-r2 eclass is the following:</p>
+ <pre caption="default src_install function">
+qt4-r2_src_install() {
+ debug-print-function $FUNCNAME "$@"
+ emake INSTALL_ROOT="${D}" DESTDIR="${D}" install || die "emake install failed"
+ # install documentation
+ if [[ -n "${DOCS}" ]]; then
+ local dir=${DOCSDIR:-${S}}
+ for doc in ${DOCS}; do
+ dodoc "${dir}/${doc}" || die "dodoc failed"
+ done
+ fi
+}</pre>
+ <p>
+ This is the most popular method to install Qt4 packages and their documentation. Rarely you will need to override this
+ function. Usually, you write an extended version of this one, to support translations installation like the following case:</p>
+ <pre caption="extended src_install function">
src_install() {
- emake INSTALL_ROOT="${D}" install || die "emake install failed"
- dodoc README AUTHORS || die "dodoc failed"
-}
- </pre>
+ # do normal installation
+ qt4-r2_src_install
+ # Install translations
+ for X in ${LINGUAS}; do
+ for Z in ${LANGS}; do
+ ...
+ ...</pre>
</body>
</section>
</chapter>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml
@ 2010-03-25 21:25 Ben de Groot (yngwin)
0 siblings, 0 replies; 11+ messages in thread
From: Ben de Groot (yngwin) @ 2010-03-25 21:25 UTC (permalink / raw
To: gentoo-commits
yngwin 10/03/25 21:25:06
Modified: qt4-based-ebuild-howto.xml
Log:
Bring up to date with eapi-3, formatting and editting for grammar and style.
Revision Changes Path
1.3 xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?r1=1.2&r2=1.3
Index: qt4-based-ebuild-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- qt4-based-ebuild-howto.xml 20 Dec 2009 19:28:18 -0000 1.2
+++ qt4-based-ebuild-howto.xml 25 Mar 2010 21:25:06 -0000 1.3
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.2 2009/12/20 19:28:18 hwoarang Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.3 2010/03/25 21:25:06 yngwin Exp $ -->
<guide link="/proj/en/desktop/kde/qt4-ebuild-howto.xml" lang="en">
<title>Qt4-based ebuild howto</title>
@@ -13,6 +13,10 @@
<mail link="ayoy" />
</author>
+<author title="Editor">
+ <mail link="yngwin"/>
+</author>
+
<abstract>
This guide is intented to give an overview of how to create a Qt4-based ebuild. It will assist users to write proper ebuilds for Qt4 based packages using Gentoos' qt4-r2 eclass and split Qt4 dependencies.
</abstract>
@@ -21,67 +25,99 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>0.5</version>
-<date>2009-12-20</date>
+<version>0.6</version>
+<date>2010-03-25</date>
<chapter>
<title>Introduction</title>
<section>
<title>Purpose of this howto</title>
<body>
- <p>The goal of this document is to introduce qt4-r2 eclass and provide basic instructions on writing ebuilds for applications that use Qt 4 qmake build system. If you're writing an ebuild for a Qt-based application that uses cmake as a build system, you would like to take a look at cmake-utils eclass instead.</p>
+ <p>The goal of this document is to introduce the qt4-r2 eclass and provide
+ basic instructions on writing ebuilds for applications that use the Qt4
+ qmake build system. If you're writing an ebuild for a Qt-based
+ application that uses cmake as a build system, you should take a look
+ at the cmake-utils eclass instead.</p>
</body>
</section>
</chapter>
<chapter>
<title>Required variables, inheriting eclass and EAPI version</title>
<section>
+ <title>Valid EAPI version</title>
+ <body>
+ <p>The first step for your shiny Qt4-based ebuild is to specify the
+ right EAPI. The current eclass is compatible with EAPI 2 and 3
+ <b>only</b>, so you have to use one of these when inheriting qt4-r2
+ eclass.</p>
+ <pre caption="Specify correct EAPI version">
+EAPI="3"</pre>
+ </body>
+ </section>
+ <section>
<title>Inherit qt4-r2 eclass</title>
<body>
- <p>All Qt 4 qmake-based ebuilds should use qt4-r2 eclass which provides usefull tools and features (listed below) for building Qt 4 applications.</p>
+ <p>All Qt4 qmake-based ebuilds should use qt4-r2 eclass, which provides
+ usefull tools and features (listed below) for building Qt4 applications.
+ </p>
<pre caption="Inheriting qt4-r2 eclass">
inherit qt4-r2</pre>
<warn>
- There is an old qt4 eclass in the tree. It's deprecated since 15 December 2009. Please use qt4-r2 eclass instead since we plan to drop the old eclass. If you already maintain a Qt4 ebuild which uses qt4 eclass, please consider migrate to the new eclass as soon as possible.
+ There is an old qt4 eclass in the tree. It has been deprecated since
+ 15 December 2009. Please use the qt4-r2 eclass instead, since we plan
+ to drop the old eclass. If you already maintain a Qt4 ebuild which uses
+ the qt4 eclass, please consider migrating to the new eclass as soon as
+ possible.
</warn>
</body>
</section>
<section>
- <title>Valid EAPI version</title>
- <body>
- <p>The next step for your shiny Qt4-based ebuild, is to specify the right EAPI. Current eclass is compatible with EAPI 2 <b>only</b>,
- so you have to use it when inheriting qt4-r2 eclass.</p>
- <pre caption="Specify correct EAPI version">
-EAPI="2"</pre>
- <p>That was the most important step for your ebuild.</p>
- </body>
- </section>
- <section>
<title>Language variables</title>
<body>
<p>
- In case your ebuild provides translations, you should populate the IUSE variable with appropriate <c>linguas_*</c> USE flags. When writing ebuild it's common to group language codes that are parts of translation files' names in a variable that is later used to iterate over translations when configuring and/or installing the package.</p>
- <p>qt4-r2 eclass provides two special variables for this purpose. <c>LANGS</c> and <c>LANGSLONG</c> are meant to ease up <c>linguas_*</c> USE flags population. All you have to do is set <c>LANGS</c> to a list of translations languages for your package (using language codes as specified in <path>${PORTDIR}/profiles/desc/linguas.desc</path>).</p>
- <p>Some applications provide translation files with languages specified together with a country code (e.g. <path>myapp_de_DE.ts</path>). That's not always the proper solution from Gentoo point of view, since e.g. "de_DE" is an invalid <c>LINGUAS</c> member. If your package's translations files contain language codes incompatible with those used by Gentoo, the <c>LANGSLONG</c> variable might help you a bit. It will cut off the country code from the language when populating <c>linguas_*</c> IUSE. This way you can use an incompatible language code to refer to the translation file, but still you're sure that <c>linguas_*</c> use flag is specified correctly.</p>
+ In case your ebuild provides translations, you should populate the IUSE
+ variable with appropriate <c>linguas_*</c> USE flags. When writing
+ ebuilds it is common to group language codes that are part of
+ translation filenames in a variable that is later used to iterate over
+ translations when configuring and/or installing the package.</p>
+ <p>Our qt4-r2 eclass provides two special variables for this purpose.
+ <c>LANGS</c> and <c>LANGSLONG</c> are meant to ease up <c>linguas_*</c>
+ USE flags population. All you have to do is set <c>LANGS</c> to a list
+ of translation languages for your package (using language codes as
+ specified in <path>${PORTDIR}/profiles/desc/linguas.desc</path>).</p>
+ <p>Some applications provide translation files with languages specified
+ together with a country code (e.g. <path>myapp_de_DE.ts</path>). That
+ is not always the proper solution from a Gentoo point of view, since
+ e.g. "de_DE" is an invalid <c>LINGUAS</c> member. If your package's
+ translation files contain language codes incompatible with those used
+ by Gentoo, the <c>LANGSLONG</c> variable might help you a bit. It will
+ cut off the country code from the language when populating
+ <c>linguas_*</c> IUSE. This way you can use an incompatible language
+ code to refer to the translation file, but still you're sure that
+ <c>linguas_*</c> use flag is specified correctly.</p>
<pre caption="Example of defining languages">
LANGS="de es fr_CA hu pt_BR zh_CN"
LANGSLONG="cs_CZ fr_FR pl_PL"</pre>
- <p>This example results in the following IUSE set:</p>
+ <p>This example results in the following expanded IUSE set:</p>
<pre caption="Resulting IUSE">
-IUSE="linguas_cs linguas_de linguas_es linguas_fr linguas_fr_CA linguas_hu linguas_pl linguas_pt_BR linguas_zh_CN"</pre>
+IUSE="linguas_cs linguas_de linguas_es linguas_fr linguas_fr_CA linguas_hu
+linguas_pl linguas_pt_BR linguas_zh_CN"</pre>
<impo>
- In order for automatic <c>linguas_*</c> IUSE generation to work, <c>LANGS</c> and <c>LANGSLONG</c> <b>must</b> be set before inheriting qt4-r2 eclass.
+ In order for automatic <c>linguas_*</c> IUSE generation to work,
+ <c>LANGS</c> and <c>LANGSLONG</c> <b>must</b> be set before inheriting
+ qt4-r2 eclass.
</impo>
</body>
</section>
</chapter>
<chapter>
- <title>Dependencies and Use flags</title>
+ <title>Dependencies and USE flags</title>
<section>
- <title>Depend on qt4 split packages</title>
+ <title>Depend on Qt4 split packages</title>
<body>
- <p>Since Qt-4.4.0, Gentoo Qt team, splits monolithic Qt4 package into smaller packages. Those are</p>
+ <p>Since Qt-4.4.0 the Gentoo Qt team splits the monolithic Qt4 package
+ into smaller packages. Those are</p>
<ul>
<li> x11-libs/qt-assistant</li>
<li> x11-libs/qt-core</li>
@@ -99,12 +135,14 @@
<li> x11-libs/qt-webkit</li>
<li> x11-libs/qt-xmlpatterns</li>
</ul>
- <p>Now all you need to do, is to specify the correct modules on DEPEND variable</p>
+ <p>Now all you need to do, is to specify the correct modules in the DEPEND
+ variable:</p>
<pre caption="Simple example to demonstrate proper qt4 split dependencies usage">
DEPEND="x11-libs/qt-gui:4
x11-libs/qt-sql:4"</pre>
<warn>
- Even though there is a <c>x11-libs/qt</c> metapackage, you <b>must NOT</b> use it as a dependency.
+ Even though there is a <c>x11-libs/qt</c> metapackage, you <b>must NOT</b>
+ use it as a dependency. We have masked it to prevent that.
</warn>
</body>
</section>
@@ -112,17 +150,21 @@
<section>
<title>Debug and Release scope</title>
<body>
- <p>Qt offers you the ability to build your applications using two different modes:</p>
+ <p>Qt offers you the ability to build your applications using two different
+ modes:</p>
<ul>
- <li>Release: Leads to smaller binaries, usefull for the production state.</li>
- <li>Debug: Leads to bigger binaries, usefull for debugging during development process.</li>
+ <li>Release: Leads to smaller binaries, useful for the normal usage.</li>
+ <li>Debug: Leads to bigger binaries, useful for debugging during the
+ development process.</li>
</ul>
- <p>Thus, qt4-r2 eclass can use the 'debug' use flag in order to build your application with debug symbols.</p>
+ <p>Thus, qt4-r2 eclass can use the 'debug' use flag in order to build your
+ application with debug symbols.</p>
<pre caption="Add 'debug' use flag">
IUSE="debug"</pre>
<impo>
- 'debug' use flag usage implies that you have already followed the <uri link="/proj/en/qa/backtraces.xml">
- "How to get meaningful backtraces in Gentoo"</uri> tutorial.
+ 'debug' use flag usage implies that you have already followed the
+ <uri link="/proj/en/qa/backtraces.xml">"How to get meaningful backtraces in
+ Gentoo"</uri> tutorial.
</impo>
</body>
</section>
@@ -130,8 +172,13 @@
<section>
<title> Package documentation</title>
<body>
- <p>There is a special variable to use in case your package provides document files. <b>DOCS</b> variable can be used by the <uri link="#doc_chap5_pre1">default src_install function</uri> to install those documents. Normally the documents are located on "${S}" directory. If not, set the <b>DOCSDIR</b> variable to match the documents path. If you don't need to use DOCSDIR variable, then "${S} will be used by default.</p>
- <pre caption="simple example of DOCS variable usage">
+ <p>There is a special variable to use in case your package provides
+ documentation files. The <b>DOCS</b> variable can be used by the
+ <uri link="#doc_chap5_pre1">default src_install function</uri> to install
+ those documents. Normally the documents are located in the ${S} directory.
+ If not, set the <b>DOCSDIR</b> variable to match the documents path. If you
+ don't need to use DOCSDIR variable, then ${S} will be used by default.</p>
+ <pre caption="Simple example of DOCS variable usage">
DOCSDIR="${S}/docs/"
DOCS="Authors ChangeLog Readme"</pre>
</body>
@@ -144,21 +191,24 @@
<section>
<title>src_prepare function</title>
<body>
- <p>EAPI2 introduced the src_prepare function which is executed right after src_unpack. The default implementation does nothing.</p>
+ <p>EAPI2 introduced the src_prepare function which is executed right
+ after src_unpack. The default implementation does nothing.</p>
</body>
</section>
<section>
<title>Applying patches</title>
<body>
- <p>Qt4 eclass uses the base eclass autopatcher in order to apply patches. All you have to do is to specify which patches
- you want to apply using PATCHES variable</p>
- <pre caption="Simple example for using PATCHES variable">
+ <p>The qt4-r2 eclass uses the base eclass autopatcher in order to apply
+ patches. All you have to do is to specify which patches you want to apply
+ using the PATCHES array:</p>
+ <pre caption="Simple example for using the PATCHES array">
PATCHES=(
"${FILESDIR}/fixconfig.patch"
"${FILESDIR}/fixgui.patch"
)</pre>
<impo>
- Please note that PATCHES is an array, so you will always need to includes patches between parenthesis.
+ Please note that PATCHES is an array, so you will always need to
+ includes patches between parentheses.
</impo>
</body>
</section>
@@ -169,9 +219,16 @@
<section>
<title>The 'magic' eqmake4 tool</title>
<body>
- <p>We provide a special function for configuring Qt4 project files. That is eqmake4 which is provided by qt4-r2 eclass. It is based on qmake, plus it uses
- default Qt variables for proper package configuration. Packages should be configured under src_configure function.
- The <b>default src_configure phase</b> finds and configures project files ( *.pro files ) located on ${S} directory. If there are more than one project files in there, it will try to find the one named ${PN}.pro or $(basename ${PWD}).pro. In case, your package uses some weird file hieracy and you need to configure a project file on a subfolder, then you can specify the path as a parameter on eqmake4.</p>
+ <p>We provide a special function for configuring Qt4 project files.
+ That is eqmake4, which is provided by the qt4-r2 eclass. It is based on
+ qmake, plus it uses default Qt variables for proper package
+ configuration. Packages should be configured during the src_configure
+ phase. The <b>default src_configure phase</b> finds and configures
+ project files (.pro files) located in the ${S} directory. If there are
+ more than one project files in there, it will try to find the one named
+ ${PN}.pro or $(basename ${PWD}).pro. In case your package uses some
+ weird file hierarchy and you need to configure a project file in a
+ subdirectory, then you can specify the path as a parameter to eqmake4:</p>
<pre caption="Simple example for src_configure function">
src_configure() {
eqmake4 "${S}"/tool/foo.pro
@@ -179,8 +236,9 @@
<impo>
eqmake4 does not need a 'die' statement.
</impo>
- <p>There are some rare occasions where eqmake4 fails, but qmake works. Please file a <uri link="http://bugs.gentoo.org">bug</uri> about this in order to take care
- of it</p>
+ <p>There are some rare occasions where eqmake4 fails, but qmake works.
+ Please file a <uri link="http://bugs.gentoo.org">bug</uri> about this,
+ in order for us to possibly fix this.</p>
</body>
</section>
</chapter>
@@ -191,7 +249,7 @@
<title>src_install function</title>
<body>
<p>
- The <b>default src_install function</b> n qt4-r2 eclass is the following:</p>
+ The <b>default src_install</b> in qt4-r2 eclass is the following:</p>
<pre caption="default src_install function">
qt4-r2_src_install() {
debug-print-function $FUNCNAME "$@"
@@ -205,8 +263,10 @@
fi
}</pre>
<p>
- This is the most popular method to install Qt4 packages and their documentation. Rarely you will need to override this
- function. Usually, you write an extended version of this one, to support translations installation like the following case:</p>
+ This is the most popular method to install Qt4 packages and their
+ documentation. Rarely you will need to override this function. Usually,
+ you write an extended version of this one, to support translations
+ installation, like the following case:</p>
<pre caption="extended src_install function">
src_install() {
# do normal installation
^ permalink raw reply [flat|nested] 11+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml
@ 2010-07-13 22:42 Markos Chandras (hwoarang)
0 siblings, 0 replies; 11+ messages in thread
From: Markos Chandras (hwoarang) @ 2010-07-13 22:42 UTC (permalink / raw
To: gentoo-commits
hwoarang 10/07/13 22:42:12
Modified: qt4-based-ebuild-howto.xml
Log:
Add x11-libs/qt-declarative on qt modules list
Revision Changes Path
1.4 xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?r1=1.3&r2=1.4
Index: qt4-based-ebuild-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- qt4-based-ebuild-howto.xml 25 Mar 2010 21:25:06 -0000 1.3
+++ qt4-based-ebuild-howto.xml 13 Jul 2010 22:42:12 -0000 1.4
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.3 2010/03/25 21:25:06 yngwin Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.4 2010/07/13 22:42:12 hwoarang Exp $ -->
<guide link="/proj/en/desktop/kde/qt4-ebuild-howto.xml" lang="en">
<title>Qt4-based ebuild howto</title>
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>0.6</version>
-<date>2010-03-25</date>
+<version>0.6.1</version>
+<date>2010-07-14</date>
<chapter>
<title>Introduction</title>
@@ -122,6 +122,7 @@
<li> x11-libs/qt-assistant</li>
<li> x11-libs/qt-core</li>
<li> x11-libs/qt-dbus</li>
+ <li> x11-libs/qt-declarative</li>
<li> x11-libs/qt-demo</li>
<li> x11-libs/qt-gui</li>
<li> x11-libs/qt-multimedia</li>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml
@ 2010-08-15 22:28 Markos Chandras (hwoarang)
0 siblings, 0 replies; 11+ messages in thread
From: Markos Chandras (hwoarang) @ 2010-08-15 22:28 UTC (permalink / raw
To: gentoo-commits
hwoarang 10/08/15 22:28:22
Modified: qt4-based-ebuild-howto.xml
Log:
Don't link to kde page anymore
Revision Changes Path
1.5 xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.5&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.5&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?r1=1.4&r2=1.5
Index: qt4-based-ebuild-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- qt4-based-ebuild-howto.xml 13 Jul 2010 22:42:12 -0000 1.4
+++ qt4-based-ebuild-howto.xml 15 Aug 2010 22:28:22 -0000 1.5
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.4 2010/07/13 22:42:12 hwoarang Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.5 2010/08/15 22:28:22 hwoarang Exp $ -->
-<guide link="/proj/en/desktop/kde/qt4-ebuild-howto.xml" lang="en">
+<guide link="/proj/en/desktop/qt/qt4-ebuild-howto.xml" lang="en">
<title>Qt4-based ebuild howto</title>
<author title="Author">
^ permalink raw reply [flat|nested] 11+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml
@ 2012-02-02 19:15 Markos Chandras (hwoarang)
0 siblings, 0 replies; 11+ messages in thread
From: Markos Chandras (hwoarang) @ 2012-02-02 19:15 UTC (permalink / raw
To: gentoo-commits
hwoarang 12/02/02 19:15:25
Modified: qt4-based-ebuild-howto.xml
Log:
Update guide to EAPI4
Revision Changes Path
1.6 xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?r1=1.5&r2=1.6
Index: qt4-based-ebuild-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- qt4-based-ebuild-howto.xml 15 Aug 2010 22:28:22 -0000 1.5
+++ qt4-based-ebuild-howto.xml 2 Feb 2012 19:15:25 -0000 1.6
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.5 2010/08/15 22:28:22 hwoarang Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.6 2012/02/02 19:15:25 hwoarang Exp $ -->
<guide link="/proj/en/desktop/qt/qt4-ebuild-howto.xml" lang="en">
<title>Qt4-based ebuild howto</title>
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>0.6.1</version>
-<date>2010-07-14</date>
+<version>0.6.2</version>
+<date>2012-02-02</date>
<chapter>
<title>Introduction</title>
@@ -47,11 +47,9 @@
<title>Valid EAPI version</title>
<body>
<p>The first step for your shiny Qt4-based ebuild is to specify the
- right EAPI. The current eclass is compatible with EAPI 2 and 3
- <b>only</b>, so you have to use one of these when inheriting qt4-r2
- eclass.</p>
- <pre caption="Specify correct EAPI version">
-EAPI="3"</pre>
+ right EAPI. The current eclass is compatible with EAPI 2, 3 or 4,
+ so you have to use one of these when inheriting qt4-r2 eclass.</p>
+ <pre caption="Specify correct EAPI version">EAPI="4"</pre>
</body>
</section>
<section>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml
@ 2012-02-09 22:32 Markos Chandras (hwoarang)
0 siblings, 0 replies; 11+ messages in thread
From: Markos Chandras (hwoarang) @ 2012-02-09 22:32 UTC (permalink / raw
To: gentoo-commits
hwoarang 12/02/09 22:32:56
Modified: qt4-based-ebuild-howto.xml
Log:
Update guide. Misc improvements. Thanks to Michael (kensington) <gentoo@scribeofthenile.com>. Bug #399405
Revision Changes Path
1.7 xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.7&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.7&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?r1=1.6&r2=1.7
Index: qt4-based-ebuild-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- qt4-based-ebuild-howto.xml 2 Feb 2012 19:15:25 -0000 1.6
+++ qt4-based-ebuild-howto.xml 9 Feb 2012 22:32:56 -0000 1.7
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.6 2012/02/02 19:15:25 hwoarang Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.7 2012/02/09 22:32:56 hwoarang Exp $ -->
<guide link="/proj/en/desktop/qt/qt4-ebuild-howto.xml" lang="en">
<title>Qt4-based ebuild howto</title>
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>0.6.2</version>
-<date>2012-02-02</date>
+<version>0.6.3</version>
+<date>2012-02-09</date>
<chapter>
<title>Introduction</title>
@@ -56,7 +56,7 @@
<title>Inherit qt4-r2 eclass</title>
<body>
<p>All Qt4 qmake-based ebuilds should use qt4-r2 eclass, which provides
- usefull tools and features (listed below) for building Qt4 applications.
+ useful tools and features (listed below) for building Qt4 applications.
</p>
<pre caption="Inheriting qt4-r2 eclass">
inherit qt4-r2</pre>
@@ -140,7 +140,7 @@
DEPEND="x11-libs/qt-gui:4
x11-libs/qt-sql:4"</pre>
<warn>
- Even though there is a <c>x11-libs/qt</c> metapackage, you <b>must NOT</b>
+ Even though there is a <c>x11-libs/qt-meta</c> metapackage, you <b>must NOT</b>
use it as a dependency. We have masked it to prevent that.
</warn>
</body>
@@ -252,14 +252,14 @@
<pre caption="default src_install function">
qt4-r2_src_install() {
debug-print-function $FUNCNAME "$@"
+
emake INSTALL_ROOT="${D}" DESTDIR="${D}" install || die "emake install failed"
# install documentation
- if [[ -n "${DOCS}" ]]; then
- local dir=${DOCSDIR:-${S}}
- for doc in ${DOCS}; do
- dodoc "${dir}/${doc}" || die "dodoc failed"
- done
- fi
+
+ local dir=${DOCSDIR:-${S}}
+ for doc in ${DOCS}; do
+ dodoc "${dir}/${doc}" || die "dodoc failed"
+ done
}</pre>
<p>
This is the most popular method to install Qt4 packages and their
^ permalink raw reply [flat|nested] 11+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml
@ 2012-10-28 15:21 Sven Vermeulen (swift)
0 siblings, 0 replies; 11+ messages in thread
From: Sven Vermeulen (swift) @ 2012-10-28 15:21 UTC (permalink / raw
To: gentoo-commits
swift 12/10/28 15:21:01
Modified: qt4-based-ebuild-howto.xml
Log:
Removing link attribute from guides
Revision Changes Path
1.8 xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.8&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.8&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?r1=1.7&r2=1.8
Index: qt4-based-ebuild-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- qt4-based-ebuild-howto.xml 9 Feb 2012 22:32:56 -0000 1.7
+++ qt4-based-ebuild-howto.xml 28 Oct 2012 15:21:01 -0000 1.8
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.7 2012/02/09 22:32:56 hwoarang Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.8 2012/10/28 15:21:01 swift Exp $ -->
-<guide link="/proj/en/desktop/qt/qt4-ebuild-howto.xml" lang="en">
+<guide lang="en">
<title>Qt4-based ebuild howto</title>
<author title="Author">
^ permalink raw reply [flat|nested] 11+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml
@ 2013-08-19 14:50 Mikle Kolyada (zlogene)
0 siblings, 0 replies; 11+ messages in thread
From: Mikle Kolyada (zlogene) @ 2013-08-19 14:50 UTC (permalink / raw
To: gentoo-commits
zlogene 13/08/19 14:50:07
Modified: qt4-based-ebuild-howto.xml
Log:
update info: qt dependencies were moved to the new category
Revision Changes Path
1.9 xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.9&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.9&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?r1=1.8&r2=1.9
Index: qt4-based-ebuild-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- qt4-based-ebuild-howto.xml 28 Oct 2012 15:21:01 -0000 1.8
+++ qt4-based-ebuild-howto.xml 19 Aug 2013 14:50:07 -0000 1.9
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.8 2012/10/28 15:21:01 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.9 2013/08/19 14:50:07 zlogene Exp $ -->
<guide lang="en">
<title>Qt4-based ebuild howto</title>
@@ -17,6 +17,10 @@
<mail link="yngwin"/>
</author>
+<author title="Editor">
+ <mail link="zlogene"/>
+</author>
+
<abstract>
This guide is intented to give an overview of how to create a Qt4-based ebuild. It will assist users to write proper ebuilds for Qt4 based packages using Gentoos' qt4-r2 eclass and split Qt4 dependencies.
</abstract>
@@ -26,7 +30,7 @@
<license/>
<version>0.6.3</version>
-<date>2012-02-09</date>
+<date>2013-08-19</date>
<chapter>
<title>Introduction</title>
@@ -117,30 +121,30 @@
<p>Since Qt-4.4.0 the Gentoo Qt team splits the monolithic Qt4 package
into smaller packages. Those are</p>
<ul>
- <li> x11-libs/qt-assistant</li>
- <li> x11-libs/qt-core</li>
- <li> x11-libs/qt-dbus</li>
- <li> x11-libs/qt-declarative</li>
- <li> x11-libs/qt-demo</li>
- <li> x11-libs/qt-gui</li>
- <li> x11-libs/qt-multimedia</li>
- <li> x11-libs/qt-opengl</li>
- <li> x11-libs/qt-phonon</li>
- <li> x11-libs/qt-qt3support</li>
- <li> x11-libs/qt-script</li>
- <li> x11-libs/qt-sql</li>
- <li> x11-libs/qt-svg</li>
- <li> x11-libs/qt-test</li>
- <li> x11-libs/qt-webkit</li>
- <li> x11-libs/qt-xmlpatterns</li>
+ <li> dev-qt/assistant</li>
+ <li> dev-qt/qtcore</li>
+ <li> dev-qt/qtdbus</li>
+ <li> dev-qt/qtdeclarative</li>
+ <li> dev-qt/qtdemo</li>
+ <li> dev-qt/qtgui</li>
+ <li> dev-qt/qtmultimedia</li>
+ <li> dev-qt/qtopengl</li>
+ <li> dev-qt/qtphonon</li>
+ <li> dev-qt/qtqt3support</li>
+ <li> dev-qt/qtscript</li>
+ <li> dev-qt/qtsql</li>
+ <li> dev-qt/qtsvg</li>
+ <li> dev-qt/qttest</li>
+ <li> dev-qt/qtwebkit</li>
+ <li> dev-qt/qtxmlpatterns</li>
</ul>
<p>Now all you need to do, is to specify the correct modules in the DEPEND
variable:</p>
<pre caption="Simple example to demonstrate proper qt4 split dependencies usage">
-DEPEND="x11-libs/qt-gui:4
- x11-libs/qt-sql:4"</pre>
+DEPEND="dev-qt/qtgui:4
+ dev-qt/qtsql:4"</pre>
<warn>
- Even though there is a <c>x11-libs/qt-meta</c> metapackage, you <b>must NOT</b>
+ Even though there is a <c>dev-qt/qt-meta</c> metapackage, you <b>must NOT</b>
use it as a dependency. We have masked it to prevent that.
</warn>
</body>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml
@ 2013-08-19 15:43 Mikle Kolyada (zlogene)
0 siblings, 0 replies; 11+ messages in thread
From: Mikle Kolyada (zlogene) @ 2013-08-19 15:43 UTC (permalink / raw
To: gentoo-commits
zlogene 13/08/19 15:43:05
Modified: qt4-based-ebuild-howto.xml
Log:
update guide to EAPI=5
Revision Changes Path
1.10 xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.10&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.10&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?r1=1.9&r2=1.10
Index: qt4-based-ebuild-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- qt4-based-ebuild-howto.xml 19 Aug 2013 14:50:07 -0000 1.9
+++ qt4-based-ebuild-howto.xml 19 Aug 2013 15:43:05 -0000 1.10
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.9 2013/08/19 14:50:07 zlogene Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.10 2013/08/19 15:43:05 zlogene Exp $ -->
<guide lang="en">
<title>Qt4-based ebuild howto</title>
@@ -29,7 +29,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>0.6.3</version>
+<version>0.6.4</version>
<date>2013-08-19</date>
<chapter>
@@ -51,9 +51,9 @@
<title>Valid EAPI version</title>
<body>
<p>The first step for your shiny Qt4-based ebuild is to specify the
- right EAPI. The current eclass is compatible with EAPI 2, 3 or 4,
+ right EAPI. The current eclass is compatible with EAPI 2, 3, 4 or 5,
so you have to use one of these when inheriting qt4-r2 eclass.</p>
- <pre caption="Specify correct EAPI version">EAPI="4"</pre>
+ <pre caption="Specify correct EAPI version">EAPI="5"</pre>
</body>
</section>
<section>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml
@ 2013-08-20 7:45 Sergey Popov (pinkbyte)
0 siblings, 0 replies; 11+ messages in thread
From: Sergey Popov (pinkbyte) @ 2013-08-20 7:45 UTC (permalink / raw
To: gentoo-commits
pinkbyte 13/08/20 07:45:29
Modified: qt4-based-ebuild-howto.xml
Log:
Fix a typo in qt3support package name
Revision Changes Path
1.11 xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.11&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?rev=1.11&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml?r1=1.10&r2=1.11
Index: qt4-based-ebuild-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- qt4-based-ebuild-howto.xml 19 Aug 2013 15:43:05 -0000 1.10
+++ qt4-based-ebuild-howto.xml 20 Aug 2013 07:45:29 -0000 1.11
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.10 2013/08/19 15:43:05 zlogene Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/qt/qt4-based-ebuild-howto.xml,v 1.11 2013/08/20 07:45:29 pinkbyte Exp $ -->
<guide lang="en">
<title>Qt4-based ebuild howto</title>
@@ -130,7 +130,7 @@
<li> dev-qt/qtmultimedia</li>
<li> dev-qt/qtopengl</li>
<li> dev-qt/qtphonon</li>
- <li> dev-qt/qtqt3support</li>
+ <li> dev-qt/qt3support</li>
<li> dev-qt/qtscript</li>
<li> dev-qt/qtsql</li>
<li> dev-qt/qtsvg</li>
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2013-08-20 7:45 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-20 19:28 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/qt: qt4-based-ebuild-howto.xml Markos Chandras (hwoarang)
-- strict thread matches above, loose matches on Subject: below --
2013-08-20 7:45 Sergey Popov (pinkbyte)
2013-08-19 15:43 Mikle Kolyada (zlogene)
2013-08-19 14:50 Mikle Kolyada (zlogene)
2012-10-28 15:21 Sven Vermeulen (swift)
2012-02-09 22:32 Markos Chandras (hwoarang)
2012-02-02 19:15 Markos Chandras (hwoarang)
2010-08-15 22:28 Markos Chandras (hwoarang)
2010-07-13 22:42 Markos Chandras (hwoarang)
2010-03-25 21:25 Ben de Groot (yngwin)
2009-11-15 14:22 Alex Alexander (wired)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox