Fulldecent (Talk | contribs) |
Fulldecent (Talk | contribs) (→Choosing the Right KDE Setup) |
||
| Line 51: | Line 51: | ||
==Choosing the Right KDE Setup== | ==Choosing the Right KDE Setup== | ||
| − | <table width="100%" | + | <table border="1" width="100%" cellpadding="5"> |
<tr> | <tr> | ||
<td width="25%" style="background: #FFEFD3">'''Official Release''' | <td width="25%" style="background: #FFEFD3">'''Official Release''' | ||
| − | <td width="25%" style="background: #FFFEE4">''' | + | <td width="25%" style="background: #FFFEE4">'''Nightly Build''' |
| − | <td width="25%" style="background: #D0ECEA">''' | + | <td width="25%" style="background: #D0ECEA">'''Stable from Source''' |
<td width="25%" style="background: #9FD6D2">'''Trunk''' | <td width="25%" style="background: #9FD6D2">'''Trunk''' | ||
<tr> | <tr> | ||
| Line 63: | Line 63: | ||
<td>''For developers working on core KDE SC functionality'' | <td>''For developers working on core KDE SC functionality'' | ||
<tr> | <tr> | ||
| − | <td rowspan= | + | <td rowspan=2>See [[Distributions with KDE]], this will install all prerequisites and a fully functional KDE system. Most distributions also have "developer packages" so you can compile KDE software. |
| + | <td>Install [[build requirements]] from your distribution | ||
| + | |||
| + | <tr> | ||
| + | <td>Download and setup KDE SC easily using [[Getting_Started/Using Project Neon to contribute to KDE|Project Neon]] | ||
</table> | </table> | ||
I am interested in compiling KDE SC on a stock ubuntu-server distribution in under 7 days, and then updating the documentation so that a new contributor to KDE can do this in under 6 days. I think the huge up-front commitment to build from trunk is a barrier to entry for new contributors.
Here is a list of documentation that I am consulting and working on. They are listed in order from http://kde.org/community/getinvolved/, a place where new contributors can start, and is hierarchal based on hyper links. Action that is required is also included on this list. Ultimately, this should result in a runnable system.
Contents |
Kernel panic during git update on qt-copy
I also read that you wanted to know how long the build process takes for new comers. In that regard, I had a very hard and long time at first understanding the process of building trunk besides my stable KDE. I tried building it several times, but every time it gave some compilation errors in different pieces of codes. This was may be because of wrong bashrc that I used for settings the env variables for KDE_SRC and KDE_BUILD.
But after I got that clear (a friend helped me through), the cmakekde on kdesupport+kdelibs+phonon+kdebase took about an hour and a half, excluding the source-code download time (it took really long due to my slow internet connection).
Glad I could help! Considering the ENTIRE time, it took me about a month (I know its too long but I gave up every time it gave errors, and did not try again till a week or so) to setup KDE from trunk. And of course, I don't mind my response being put on the wiki if it helps. Actually, I just posted a small and simple walkthrough on my blog for building KDE from trunk beside the stable distro-provided KDE. Take a look, if it helps either, http://31shebang.wordpress.com/2010/09/23/kde-from-the-trunk/
-- Viranch
| Official Release | Nightly Build | Stable from Source | Trunk |
| For the casual user, or a developer who is working on applications outside of KDE SC | For application developers or package managers who are not modifying the core of KDE SC | For core KDE developers that want to spend less time compiling | For developers working on core KDE SC functionality |
| See Distributions with KDE, this will install all prerequisites and a fully functional KDE system. Most distributions also have "developer packages" so you can compile KDE software. | Install build requirements from your distribution | ||
| Download and setup KDE SC easily using Project Neon |