https://techbase.kde.org/api.php?action=feedcontributions&user=AaronPeterson&feedformat=atomKDE TechBase - User contributions [en]2024-03-19T01:49:23ZUser contributionsMediaWiki 1.40.2https://techbase.kde.org/index.php?title=Projects/Usability/HIG/Organization&diff=84472Projects/Usability/HIG/Organization2014-12-19T04:42:33Z<p>AaronPeterson: /* Context Structure */</p>
<hr />
<div>=Organization=<br />
The organizational model, also called the information architecture, describes how the system’s content and functionality are ordered and categorized. It is made up of the command structure and content structure of the application.<br />
<br />
==Command Structure==<br />
A command is any function performed by the application based on user input. Commands that perform similar functions may be grouped together. The collection of commands and command groups make up the command structure of the application. The command structure of KDE applications fall into three categories:<br />
* '''Simple''' - When there are relatively few globally applicable commands (~ less than 10) and command groups (~ less than 4). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_simple_command_structure|command patterns for a simple command structure]]. Plasmoids should use a simple command structure.<br />
* '''Complex''' - When there are several globally applicable commands and command groups and relatively few frequently used commands (~ less than 8). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_complex_command_structure|command patterns for a complex command structure]].<br />
* '''Very complex''' - When there are many globally applicable commands and command groups and many frequently used commands. Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_very_complex_command_structure|command patterns for a very complex command structure]].<br />
<br />
<br />
If it is unclear what the command structure of a new application should be, start by assuming a simple command structure and select an associated command pattern. As the design evolves, if the selected pattern becomes inadequate then consider a pattern for a more complex command structure.<br />
<br />
==Content Structure==<br />
The content structure depends on how the underlying content of the application is organized. The content of KDE applications fall into 4 categories:<br />
* '''Flat''' - When the pieces of application content are not grouped. E.g. a playlist, a slideshow or a list of documents or contacts. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_flat_content_structure|navigation patterns for a flat content structure]]. Plasmoids may use a flat content structure.<br />
* '''2-deep''' - When all application content are grouped into top-level categories. E.g. picture albums, music albums, email folders or tags. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_2-deep_content_structure|navigation patterns for a 2-deep content structure]] . Plasmoids should use no more than a 2-deep content structure.<br />
* '''3 deep''' - When all application content are grouped into categories, which are themselves be grouped into top-level categories. E.g. a music or video library. Content structures this deep should generally be avoided where possible. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_3-deep_content_structure|navigation patterns for a 3-deep content structure]].<br />
* '''n-deep''' - When content is infinitely groupable. Examples include file systems and archives. Content structures this deep should be avoided where possible since it is difficult for the user to maintain awareness of their location in content structure. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_n-deep_content_structures|navigation patterns for a n-deep content structure]].<br />
<br />
==Context Structure==<br />
* What (specific) activity or problem is the user currently involved with solving<br />
* What user interface does the user have available to them?<br />
* Where is the user? (Location)<br />
* How to manage assumptions, and ask graciously what context the user is in.<br />
* How familiar is the user with the program.<br />
* What environment has the user come from? <br />
* accessibility<br />
* Administration How similar must this instance be to other instances? <br />
* Who should have access to this program or adjustment capability.<br />
* What other terms or alternate wordings might the user already know about solving this problem (search)<br />
* What is the cost of a failure vs cost of success?<br />
* Who dictated the work to be done? (workflow)<br />
* Who is the recipient of the work? (workflow)<br />
<br />
{{Prevnext2|prevpage=Projects/Usability/HIG/Concept|prevtext=Concept|nextpage=Projects/Usability/HIG#Behaviour|nexttext=Next Section: Behaviour|index=Projects/Usability/HIG#Getting_Started|indextext=Back to Getting Started}}</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Projects/Usability/HIG/Organization&diff=84471Projects/Usability/HIG/Organization2014-12-19T04:24:17Z<p>AaronPeterson: /* Context Structure */</p>
<hr />
<div>=Organization=<br />
The organizational model, also called the information architecture, describes how the system’s content and functionality are ordered and categorized. It is made up of the command structure and content structure of the application.<br />
<br />
==Command Structure==<br />
A command is any function performed by the application based on user input. Commands that perform similar functions may be grouped together. The collection of commands and command groups make up the command structure of the application. The command structure of KDE applications fall into three categories:<br />
* '''Simple''' - When there are relatively few globally applicable commands (~ less than 10) and command groups (~ less than 4). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_simple_command_structure|command patterns for a simple command structure]]. Plasmoids should use a simple command structure.<br />
* '''Complex''' - When there are several globally applicable commands and command groups and relatively few frequently used commands (~ less than 8). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_complex_command_structure|command patterns for a complex command structure]].<br />
* '''Very complex''' - When there are many globally applicable commands and command groups and many frequently used commands. Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_very_complex_command_structure|command patterns for a very complex command structure]].<br />
<br />
<br />
If it is unclear what the command structure of a new application should be, start by assuming a simple command structure and select an associated command pattern. As the design evolves, if the selected pattern becomes inadequate then consider a pattern for a more complex command structure.<br />
<br />
==Content Structure==<br />
The content structure depends on how the underlying content of the application is organized. The content of KDE applications fall into 4 categories:<br />
* '''Flat''' - When the pieces of application content are not grouped. E.g. a playlist, a slideshow or a list of documents or contacts. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_flat_content_structure|navigation patterns for a flat content structure]]. Plasmoids may use a flat content structure.<br />
* '''2-deep''' - When all application content are grouped into top-level categories. E.g. picture albums, music albums, email folders or tags. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_2-deep_content_structure|navigation patterns for a 2-deep content structure]] . Plasmoids should use no more than a 2-deep content structure.<br />
* '''3 deep''' - When all application content are grouped into categories, which are themselves be grouped into top-level categories. E.g. a music or video library. Content structures this deep should generally be avoided where possible. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_3-deep_content_structure|navigation patterns for a 3-deep content structure]].<br />
* '''n-deep''' - When content is infinitely groupable. Examples include file systems and archives. Content structures this deep should be avoided where possible since it is difficult for the user to maintain awareness of their location in content structure. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_n-deep_content_structures|navigation patterns for a n-deep content structure]].<br />
<br />
==Context Structure==<br />
* What (specific) activity or problem is the user currently involved with solving<br />
* What user interface does the user have available to them?<br />
* Where is the user? (Location)<br />
* How to manage assumptions, and ask graciously what context the user is in.<br />
* How familiar is the user with the program.<br />
* What environment has the user come from? <br />
* accessibility<br />
* Administration How similar must this instance be to other instances? <br />
* Who should have access to this program or adjustment capability.<br />
* What other terms or alternate wordings might the user already know about solving this problem (search)<br />
* What is the cost of a failure vs cost of success?<br />
<br />
{{Prevnext2|prevpage=Projects/Usability/HIG/Concept|prevtext=Concept|nextpage=Projects/Usability/HIG#Behaviour|nexttext=Next Section: Behaviour|index=Projects/Usability/HIG#Getting_Started|indextext=Back to Getting Started}}</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Projects/Usability/HIG/Organization&diff=84470Projects/Usability/HIG/Organization2014-12-19T04:23:48Z<p>AaronPeterson: /* Context Structure */</p>
<hr />
<div>=Organization=<br />
The organizational model, also called the information architecture, describes how the system’s content and functionality are ordered and categorized. It is made up of the command structure and content structure of the application.<br />
<br />
==Command Structure==<br />
A command is any function performed by the application based on user input. Commands that perform similar functions may be grouped together. The collection of commands and command groups make up the command structure of the application. The command structure of KDE applications fall into three categories:<br />
* '''Simple''' - When there are relatively few globally applicable commands (~ less than 10) and command groups (~ less than 4). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_simple_command_structure|command patterns for a simple command structure]]. Plasmoids should use a simple command structure.<br />
* '''Complex''' - When there are several globally applicable commands and command groups and relatively few frequently used commands (~ less than 8). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_complex_command_structure|command patterns for a complex command structure]].<br />
* '''Very complex''' - When there are many globally applicable commands and command groups and many frequently used commands. Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_very_complex_command_structure|command patterns for a very complex command structure]].<br />
<br />
<br />
If it is unclear what the command structure of a new application should be, start by assuming a simple command structure and select an associated command pattern. As the design evolves, if the selected pattern becomes inadequate then consider a pattern for a more complex command structure.<br />
<br />
==Content Structure==<br />
The content structure depends on how the underlying content of the application is organized. The content of KDE applications fall into 4 categories:<br />
* '''Flat''' - When the pieces of application content are not grouped. E.g. a playlist, a slideshow or a list of documents or contacts. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_flat_content_structure|navigation patterns for a flat content structure]]. Plasmoids may use a flat content structure.<br />
* '''2-deep''' - When all application content are grouped into top-level categories. E.g. picture albums, music albums, email folders or tags. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_2-deep_content_structure|navigation patterns for a 2-deep content structure]] . Plasmoids should use no more than a 2-deep content structure.<br />
* '''3 deep''' - When all application content are grouped into categories, which are themselves be grouped into top-level categories. E.g. a music or video library. Content structures this deep should generally be avoided where possible. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_3-deep_content_structure|navigation patterns for a 3-deep content structure]].<br />
* '''n-deep''' - When content is infinitely groupable. Examples include file systems and archives. Content structures this deep should be avoided where possible since it is difficult for the user to maintain awareness of their location in content structure. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_n-deep_content_structures|navigation patterns for a n-deep content structure]].<br />
<br />
==Context Structure==<br />
* What (specific) activity or problem is the user currently involved with solving<br />
* What user interface does the user have available to them?<br />
* Where is the user? (Location)<br />
* How to manage assumptions, and ask graciously what context the user is in.<br />
* How familiar is the user with the program.<br />
* What environment has the user come from? <br />
* accessibility<br />
* Administration How similar must this instance be to other instances? <br />
* Who should have access to this program or adjustment capability.<br />
* What other terms or alternate wordings might the user already know about solving this problem (search)<br />
<br />
<br />
{{Prevnext2|prevpage=Projects/Usability/HIG/Concept|prevtext=Concept|nextpage=Projects/Usability/HIG#Behaviour|nexttext=Next Section: Behaviour|index=Projects/Usability/HIG#Getting_Started|indextext=Back to Getting Started}}</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Projects/Usability/HIG/Organization&diff=84469Projects/Usability/HIG/Organization2014-12-19T04:22:08Z<p>AaronPeterson: /* Context Structure */</p>
<hr />
<div>=Organization=<br />
The organizational model, also called the information architecture, describes how the system’s content and functionality are ordered and categorized. It is made up of the command structure and content structure of the application.<br />
<br />
==Command Structure==<br />
A command is any function performed by the application based on user input. Commands that perform similar functions may be grouped together. The collection of commands and command groups make up the command structure of the application. The command structure of KDE applications fall into three categories:<br />
* '''Simple''' - When there are relatively few globally applicable commands (~ less than 10) and command groups (~ less than 4). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_simple_command_structure|command patterns for a simple command structure]]. Plasmoids should use a simple command structure.<br />
* '''Complex''' - When there are several globally applicable commands and command groups and relatively few frequently used commands (~ less than 8). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_complex_command_structure|command patterns for a complex command structure]].<br />
* '''Very complex''' - When there are many globally applicable commands and command groups and many frequently used commands. Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_very_complex_command_structure|command patterns for a very complex command structure]].<br />
<br />
<br />
If it is unclear what the command structure of a new application should be, start by assuming a simple command structure and select an associated command pattern. As the design evolves, if the selected pattern becomes inadequate then consider a pattern for a more complex command structure.<br />
<br />
==Content Structure==<br />
The content structure depends on how the underlying content of the application is organized. The content of KDE applications fall into 4 categories:<br />
* '''Flat''' - When the pieces of application content are not grouped. E.g. a playlist, a slideshow or a list of documents or contacts. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_flat_content_structure|navigation patterns for a flat content structure]]. Plasmoids may use a flat content structure.<br />
* '''2-deep''' - When all application content are grouped into top-level categories. E.g. picture albums, music albums, email folders or tags. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_2-deep_content_structure|navigation patterns for a 2-deep content structure]] . Plasmoids should use no more than a 2-deep content structure.<br />
* '''3 deep''' - When all application content are grouped into categories, which are themselves be grouped into top-level categories. E.g. a music or video library. Content structures this deep should generally be avoided where possible. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_3-deep_content_structure|navigation patterns for a 3-deep content structure]].<br />
* '''n-deep''' - When content is infinitely groupable. Examples include file systems and archives. Content structures this deep should be avoided where possible since it is difficult for the user to maintain awareness of their location in content structure. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_n-deep_content_structures|navigation patterns for a n-deep content structure]].<br />
<br />
==Context Structure==<br />
* What (specific) activity or problem is the user currently involved with solving<br />
* What user interface does the user have available to them?<br />
* Where is the user? (Location)<br />
* How to manage assumptions, and ask graciously what context the user is in.<br />
* How familiar is the user with the program.<br />
* What environment has the user come from? <br />
* accessibility<br />
* Administration How similar must this instance be to other instances? <br />
* Who should have access to this program or adjustment capability.<br />
<br />
{{Prevnext2|prevpage=Projects/Usability/HIG/Concept|prevtext=Concept|nextpage=Projects/Usability/HIG#Behaviour|nexttext=Next Section: Behaviour|index=Projects/Usability/HIG#Getting_Started|indextext=Back to Getting Started}}</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Projects/Usability/HIG/Organization&diff=84468Projects/Usability/HIG/Organization2014-12-19T04:15:19Z<p>AaronPeterson: /* Context Structure */</p>
<hr />
<div>=Organization=<br />
The organizational model, also called the information architecture, describes how the system’s content and functionality are ordered and categorized. It is made up of the command structure and content structure of the application.<br />
<br />
==Command Structure==<br />
A command is any function performed by the application based on user input. Commands that perform similar functions may be grouped together. The collection of commands and command groups make up the command structure of the application. The command structure of KDE applications fall into three categories:<br />
* '''Simple''' - When there are relatively few globally applicable commands (~ less than 10) and command groups (~ less than 4). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_simple_command_structure|command patterns for a simple command structure]]. Plasmoids should use a simple command structure.<br />
* '''Complex''' - When there are several globally applicable commands and command groups and relatively few frequently used commands (~ less than 8). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_complex_command_structure|command patterns for a complex command structure]].<br />
* '''Very complex''' - When there are many globally applicable commands and command groups and many frequently used commands. Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_very_complex_command_structure|command patterns for a very complex command structure]].<br />
<br />
<br />
If it is unclear what the command structure of a new application should be, start by assuming a simple command structure and select an associated command pattern. As the design evolves, if the selected pattern becomes inadequate then consider a pattern for a more complex command structure.<br />
<br />
==Content Structure==<br />
The content structure depends on how the underlying content of the application is organized. The content of KDE applications fall into 4 categories:<br />
* '''Flat''' - When the pieces of application content are not grouped. E.g. a playlist, a slideshow or a list of documents or contacts. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_flat_content_structure|navigation patterns for a flat content structure]]. Plasmoids may use a flat content structure.<br />
* '''2-deep''' - When all application content are grouped into top-level categories. E.g. picture albums, music albums, email folders or tags. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_2-deep_content_structure|navigation patterns for a 2-deep content structure]] . Plasmoids should use no more than a 2-deep content structure.<br />
* '''3 deep''' - When all application content are grouped into categories, which are themselves be grouped into top-level categories. E.g. a music or video library. Content structures this deep should generally be avoided where possible. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_3-deep_content_structure|navigation patterns for a 3-deep content structure]].<br />
* '''n-deep''' - When content is infinitely groupable. Examples include file systems and archives. Content structures this deep should be avoided where possible since it is difficult for the user to maintain awareness of their location in content structure. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_n-deep_content_structures|navigation patterns for a n-deep content structure]].<br />
<br />
==Context Structure==<br />
* What (specific) activity or problem is the user currently involved with solving<br />
* What user interface does the user have available to them?<br />
* Where is the user? (Location)<br />
* How to manage assumptions, and ask graciously what context the user is in.<br />
* How familiar is the user with the program.<br />
* What environment has the user come from? <br />
* accessibility<br />
{{Prevnext2|prevpage=Projects/Usability/HIG/Concept|prevtext=Concept|nextpage=Projects/Usability/HIG#Behaviour|nexttext=Next Section: Behaviour|index=Projects/Usability/HIG#Getting_Started|indextext=Back to Getting Started}}</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Projects/Usability/HIG/Organization&diff=84467Projects/Usability/HIG/Organization2014-12-19T04:12:51Z<p>AaronPeterson: /* Context Structure */</p>
<hr />
<div>=Organization=<br />
The organizational model, also called the information architecture, describes how the system’s content and functionality are ordered and categorized. It is made up of the command structure and content structure of the application.<br />
<br />
==Command Structure==<br />
A command is any function performed by the application based on user input. Commands that perform similar functions may be grouped together. The collection of commands and command groups make up the command structure of the application. The command structure of KDE applications fall into three categories:<br />
* '''Simple''' - When there are relatively few globally applicable commands (~ less than 10) and command groups (~ less than 4). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_simple_command_structure|command patterns for a simple command structure]]. Plasmoids should use a simple command structure.<br />
* '''Complex''' - When there are several globally applicable commands and command groups and relatively few frequently used commands (~ less than 8). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_complex_command_structure|command patterns for a complex command structure]].<br />
* '''Very complex''' - When there are many globally applicable commands and command groups and many frequently used commands. Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_very_complex_command_structure|command patterns for a very complex command structure]].<br />
<br />
<br />
If it is unclear what the command structure of a new application should be, start by assuming a simple command structure and select an associated command pattern. As the design evolves, if the selected pattern becomes inadequate then consider a pattern for a more complex command structure.<br />
<br />
==Content Structure==<br />
The content structure depends on how the underlying content of the application is organized. The content of KDE applications fall into 4 categories:<br />
* '''Flat''' - When the pieces of application content are not grouped. E.g. a playlist, a slideshow or a list of documents or contacts. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_flat_content_structure|navigation patterns for a flat content structure]]. Plasmoids may use a flat content structure.<br />
* '''2-deep''' - When all application content are grouped into top-level categories. E.g. picture albums, music albums, email folders or tags. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_2-deep_content_structure|navigation patterns for a 2-deep content structure]] . Plasmoids should use no more than a 2-deep content structure.<br />
* '''3 deep''' - When all application content are grouped into categories, which are themselves be grouped into top-level categories. E.g. a music or video library. Content structures this deep should generally be avoided where possible. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_3-deep_content_structure|navigation patterns for a 3-deep content structure]].<br />
* '''n-deep''' - When content is infinitely groupable. Examples include file systems and archives. Content structures this deep should be avoided where possible since it is difficult for the user to maintain awareness of their location in content structure. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_n-deep_content_structures|navigation patterns for a n-deep content structure]].<br />
<br />
==Context Structure==<br />
* What user interface does the user have available to them?<br />
* Where is the user? (Location)<br />
* How to manage assumptions, and ask graciously what context the user is in.<br />
* What activity or problem is the user currently involved with solving<br />
* How familiar is the user with the program.<br />
* accessibility<br />
{{Prevnext2|prevpage=Projects/Usability/HIG/Concept|prevtext=Concept|nextpage=Projects/Usability/HIG#Behaviour|nexttext=Next Section: Behaviour|index=Projects/Usability/HIG#Getting_Started|indextext=Back to Getting Started}}</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Projects/Usability/HIG/Organization&diff=84466Projects/Usability/HIG/Organization2014-12-19T04:04:57Z<p>AaronPeterson: /* Context Structure */</p>
<hr />
<div>=Organization=<br />
The organizational model, also called the information architecture, describes how the system’s content and functionality are ordered and categorized. It is made up of the command structure and content structure of the application.<br />
<br />
==Command Structure==<br />
A command is any function performed by the application based on user input. Commands that perform similar functions may be grouped together. The collection of commands and command groups make up the command structure of the application. The command structure of KDE applications fall into three categories:<br />
* '''Simple''' - When there are relatively few globally applicable commands (~ less than 10) and command groups (~ less than 4). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_simple_command_structure|command patterns for a simple command structure]]. Plasmoids should use a simple command structure.<br />
* '''Complex''' - When there are several globally applicable commands and command groups and relatively few frequently used commands (~ less than 8). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_complex_command_structure|command patterns for a complex command structure]].<br />
* '''Very complex''' - When there are many globally applicable commands and command groups and many frequently used commands. Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_very_complex_command_structure|command patterns for a very complex command structure]].<br />
<br />
<br />
If it is unclear what the command structure of a new application should be, start by assuming a simple command structure and select an associated command pattern. As the design evolves, if the selected pattern becomes inadequate then consider a pattern for a more complex command structure.<br />
<br />
==Content Structure==<br />
The content structure depends on how the underlying content of the application is organized. The content of KDE applications fall into 4 categories:<br />
* '''Flat''' - When the pieces of application content are not grouped. E.g. a playlist, a slideshow or a list of documents or contacts. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_flat_content_structure|navigation patterns for a flat content structure]]. Plasmoids may use a flat content structure.<br />
* '''2-deep''' - When all application content are grouped into top-level categories. E.g. picture albums, music albums, email folders or tags. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_2-deep_content_structure|navigation patterns for a 2-deep content structure]] . Plasmoids should use no more than a 2-deep content structure.<br />
* '''3 deep''' - When all application content are grouped into categories, which are themselves be grouped into top-level categories. E.g. a music or video library. Content structures this deep should generally be avoided where possible. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_3-deep_content_structure|navigation patterns for a 3-deep content structure]].<br />
* '''n-deep''' - When content is infinitely groupable. Examples include file systems and archives. Content structures this deep should be avoided where possible since it is difficult for the user to maintain awareness of their location in content structure. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_n-deep_content_structures|navigation patterns for a n-deep content structure]].<br />
<br />
==Context Structure==<br />
* What user interface does the user have available to them?<br />
* Where is the user? (Location)<br />
* How to manage assumptions, and ask graciously what context the user is in.<br />
* What activity or problem is the user currently involved with solving<br />
<br />
{{Prevnext2|prevpage=Projects/Usability/HIG/Concept|prevtext=Concept|nextpage=Projects/Usability/HIG#Behaviour|nexttext=Next Section: Behaviour|index=Projects/Usability/HIG#Getting_Started|indextext=Back to Getting Started}}</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Projects/Usability/HIG/Organization&diff=84465Projects/Usability/HIG/Organization2014-12-19T04:03:33Z<p>AaronPeterson: From a meetup in Seattle, added Context structure, This may be moved to talk without much fight from the transcriptor.</p>
<hr />
<div>=Organization=<br />
The organizational model, also called the information architecture, describes how the system’s content and functionality are ordered and categorized. It is made up of the command structure and content structure of the application.<br />
<br />
==Command Structure==<br />
A command is any function performed by the application based on user input. Commands that perform similar functions may be grouped together. The collection of commands and command groups make up the command structure of the application. The command structure of KDE applications fall into three categories:<br />
* '''Simple''' - When there are relatively few globally applicable commands (~ less than 10) and command groups (~ less than 4). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_simple_command_structure|command patterns for a simple command structure]]. Plasmoids should use a simple command structure.<br />
* '''Complex''' - When there are several globally applicable commands and command groups and relatively few frequently used commands (~ less than 8). Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_complex_command_structure|command patterns for a complex command structure]].<br />
* '''Very complex''' - When there are many globally applicable commands and command groups and many frequently used commands. Use [[Projects/Usability/HIG/Patterns/CommandPatterns#Patterns_for_a_very_complex_command_structure|command patterns for a very complex command structure]].<br />
<br />
<br />
If it is unclear what the command structure of a new application should be, start by assuming a simple command structure and select an associated command pattern. As the design evolves, if the selected pattern becomes inadequate then consider a pattern for a more complex command structure.<br />
<br />
==Content Structure==<br />
The content structure depends on how the underlying content of the application is organized. The content of KDE applications fall into 4 categories:<br />
* '''Flat''' - When the pieces of application content are not grouped. E.g. a playlist, a slideshow or a list of documents or contacts. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_flat_content_structure|navigation patterns for a flat content structure]]. Plasmoids may use a flat content structure.<br />
* '''2-deep''' - When all application content are grouped into top-level categories. E.g. picture albums, music albums, email folders or tags. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_2-deep_content_structure|navigation patterns for a 2-deep content structure]] . Plasmoids should use no more than a 2-deep content structure.<br />
* '''3 deep''' - When all application content are grouped into categories, which are themselves be grouped into top-level categories. E.g. a music or video library. Content structures this deep should generally be avoided where possible. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_a_3-deep_content_structure|navigation patterns for a 3-deep content structure]].<br />
* '''n-deep''' - When content is infinitely groupable. Examples include file systems and archives. Content structures this deep should be avoided where possible since it is difficult for the user to maintain awareness of their location in content structure. Use [[Projects/Usability/HIG/Patterns/NavigationPatterns#Patterns_for_n-deep_content_structures|navigation patterns for a n-deep content structure]].<br />
<br />
==Context Structure==<br />
* What user interface does the user have available to them?<br />
* Where is the user?<br />
* How to not assume things needlessly, but to ask graciously what context the user is in.<br />
* What activity is the user currently involved with.<br />
<br />
{{Prevnext2|prevpage=Projects/Usability/HIG/Concept|prevtext=Concept|nextpage=Projects/Usability/HIG#Behaviour|nexttext=Next Section: Behaviour|index=Projects/Usability/HIG#Getting_Started|indextext=Back to Getting Started}}</div>AaronPetersonhttps://techbase.kde.org/index.php?title=User:AaronPeterson/Welcome_to_KDE_TechBase/20100805/&diff=53284User:AaronPeterson/Welcome to KDE TechBase/20100805/2010-08-09T01:39:34Z<p>AaronPeterson: </p>
<hr />
<div><div class="plainlinks"><br />
<!-- WELCOME TO META BOX --><br />
<div class="toccolours" style="padding:1em;"><br />
<div style="float: right;"><br />
[[File:KDE.jpg]]<br />
</div><br />
<br />
<div style="font-size: 115%; margin-right: 80px;"><br />
Welcome to the [[KDE]] [[Wiki]]. The K Desktop Enviornment is a software compilation that provides the user interface for many Linux, BSD distributions. (also available for Windows and Mac)<br />
<!-- probably to update the transclusions--><br />
<div style="font-size: 75%">[{{fullurl:Main Page|action=purge}} Purge cache]</div><br />
<br />
</div><br />
<hr style="clear: both;" /><br />
<div style="font-weight: bold; text-align: center;"><br />
<br />
[[Getting Started]] •<br />
[[Tasks]] • <br />
[[Projects]] •<br />
[[UserBase]] •<br />
[[TechBase]] •<br />
[[CommBase]] •<br />
[[Development]] <br />
<br />
<br style="clear: both;" /><br />
</div><br />
</div><br />
<!-- TechBase IN MANY LANGUAGES --><br />
<div style="padding:1em; background:#FFEFF0; border:1px solid #AAA; margin:1px 0;"><br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
</span><br />
TechBase is available in many languages!<br />
</h2><br />
{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}<br />
</div><br />
{| cellspacing="1"<br />
|- valign="top"<br />
| style="width:50%; border:1px solid #AAA; padding:1em; background:#E4FFDF;" |<br />
<!-- Our Content --><br />
<br />
=== [[Using]] ===<br />
; [[Get KDE]]<br />
; [[Tasks]]<br />
; [[Applications]]<br />
; [[Vocabulary]]<br />
; [[Get help]]<br />
<br />
=== [[Administrating]] ===<br />
; Kiosk<br />
; Configuration<br />
; Case Studies<br />
<br />
=== [[Acquiring]] ===<br />
; Distributions<br />
; For Developers <br />
; For Personal Use<br />
<br />
=== [[Developing]] ===<br />
; KDE API<br />
; Modify KDE<br />
; Create New<br />
; Tutorials<br />
<br />
=== [[Contributing]] ===<br />
; Financially<br />
; collaboration<br />
<br />
=== Community ===<br />
; Governance<br />
; ev<br />
<!-- NOTIFICATIONS --><br />
| valign="top" style="width:50%; border:1px solid #AAA; padding:1em; background:#E8F1FF;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Information_thread|action=watch}} watch]]<br />
[[{{fullurl:Template:Information_thread|action=edit}} edit]]<br />
[[{{fullurl:Goings-on/{{CURRENTYEAR}}}} '''read older news''']]<br />
</span><br />
Notifications<br />
</h2><br />
{{Information thread}}<br />
<br />
|- valign="top"<br />
| style="width:40%; border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Using this Website<br />
</h2><br />
This website is for technical documentation that supports kde users and developers<br />
<br />
* [[Style Guide]] -- conventions<br />
* [[meta:]] -- how to use mediawiki<br />
* [http://lists.kde.org|] and [[IRC]]<br />
* [[Meetup]]s (meetings between participants)<br />
* [[User groups|User groups]] <br />
<br />
| valign="top" style="border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Teams and Groups<br />
</h2><br />
What groups<br />
* [[GSoC|GSoC and SoK]]<br />
* [[Akademy]]<br />
* [[KDE e.V.]]<br />
* [[KDE Edu]]<br />
* [[KDE PIM]]<br />
* [[Promo|KDE Promo]]<br />
* [[KDE Documentation]]<br />
* [[KDE Women]]<br />
* [[Sysadmin|KDE Sysadmin]]<br />
* [[Real-Time_Communication_and_Collaboration|Real-Time Communication and Collaboration (Telepathy)]]<br />
* [[Digikam|digiKam]]<br />
* [[Plasma|Plasma Project Team Coordination]]<br />
* [[Plasma Netbook Reference Platform]]<br />
* [[Krita| Krita, Painting for Digital Artists: Developer notebook]]<br />
* [[KDE GB| KDE GB, KDE in Britain]]<br />
* [[KDE Localization|KDE Localization]]<br />
* [[KDE.org|KDE.org Websites]]<br />
* [[Phonon]]<br />
* [[Common Task Videos]]<br />
* [[Elegance]] <br />
|- valign="top"<br />
| colspan="2" style="border:1px solid #AAA; padding:1em; background:#F9F9F9" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Wikimedia Foundation|action=edit}} edit]]<br />
</span><br />
Wikimedia Foundation, Meta-Wiki, and its sister projects<br />
</h2><br />
{{Wikimedia Foundation}}{{Sisterprojects}}<br />
|}<br />
</div>__NOTOC__ __NOEDITSECTION__<br />
[[Category:Main page]]<br />
<br />
<br />
<br />
{|<br />
;[[Getting Started|Setting up a KDE development environment]]<br />
:Learn how to get, build and run KDE.<br />
<br />
<br />
;[[Development|Developing with KDE]]<br />
:[[Development/Tutorials|Tutorials]] <br />
[http://api.kde.org API Documentation] <br />
[[Development/FAQs|FAQs]] and more.<br />
:''Related'': [[Schedules|Release Schedules and Feature Plans]] <br />
[[Policies|Code Contribution and Development Guidelines]]<br />
<br />
;[[KDE System Administration]]<br />
:Information for system administrators managing KDE deployments. <br />
<br />
[[Image:Interact.png|noframe]]<br />
<br />
<br />
[[Contribute|Join the KDE Team and Contribute]]<br />
:Contribute patches, keep in touch with and join our community.<br />
:''Related:'' [[Policies|KDE Project Policies]] | [http://www.kde.org/support/support.php Donate Money]<br />
<br />
;[[ISV|ISV Information]]<br />
:Developer information for Independent Software Vendors.<br />
<br />
<br />
;[[Projects|KDE projects]]<br />
:Links to development wikis, task lists, etc. for various KDE Projects.</div>AaronPetersonhttps://techbase.kde.org/index.php?title=User:AaronPeterson/Welcome_to_KDE_TechBase/20100805/&diff=53283User:AaronPeterson/Welcome to KDE TechBase/20100805/2010-08-09T01:34:26Z<p>AaronPeterson: </p>
<hr />
<div><div class="plainlinks"><br />
<!-- WELCOME TO META BOX --><br />
<div class="toccolours" style="padding:1em;"><br />
<div style="float: right;"><br />
[[File:KDE.jpg]]<br />
</div><br />
<br />
<div style="font-size: 115%; margin-right: 80px;"><br />
Welcome to the [[KDE]] [[Wiki]]. The K Desktop Enviornment is a software compilation that provides the user interface for many Linux, BSD distributions. (also available for Windows and Mac)<br />
<!-- probably to update the transclusions--><br />
<div style="font-size: 75%">[{{fullurl:Main Page|action=purge}} Purge cache]</div><br />
<br />
</div><br />
<hr style="clear: both;" /><br />
<div style="font-weight: bold; text-align: center;"><br />
<br />
[[Getting Started]] •<br />
[[Tasks]] • <br />
[[Projects]] •<br />
[[UserBase]] •<br />
[[TechBase]] •<br />
[[CommBase]] •<br />
[[Development]] <br />
<br />
<br style="clear: both;" /><br />
</div><br />
</div><br />
<!-- TechBase IN MANY LANGUAGES --><br />
<div style="padding:1em; background:#FFEFF0; border:1px solid #AAA; margin:1px 0;"><br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
</span><br />
TechBase is available in many languages!<br />
</h2><br />
{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}<br />
</div><br />
{| cellspacing="1"<br />
|- valign="top"<br />
| style="width:50%; border:1px solid #AAA; padding:1em; background:#E4FFDF;" |<br />
<!-- Our Content --><br />
<br />
=== [[Using]] ===<br />
; [[Get KDE]]<br />
; [[Tasks]]<br />
; [[Applications]]<br />
; [[Vocabulary]]<br />
; [[Get help]]<br />
<br />
== [[Administrating]] ==<br />
; Kiosk<br />
; Configuration<br />
; Case Studies<br />
<br />
=== [[Building]] ===<br />
; Distributions<br />
; For Developers <br />
; For Personal Use<br />
<br />
=== [[Developing]] ===<br />
; Core KDE Libraries<br />
; Modify apps<br />
; Create New apps<br />
; API<br />
<br />
=== [[Contributing]] ===<br />
; Financially<br />
; By collaborating<br />
<br />
=== Community ===<br />
; Governance<br />
; ev<br />
<!-- NOTIFICATIONS --><br />
| valign="top" style="width:50%; border:1px solid #AAA; padding:1em; background:#E8F1FF;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Information_thread|action=watch}} watch]]<br />
[[{{fullurl:Template:Information_thread|action=edit}} edit]]<br />
[[{{fullurl:Goings-on/{{CURRENTYEAR}}}} '''read older news''']]<br />
</span><br />
Notifications<br />
</h2><br />
{{Information thread}}<br />
<br />
|- valign="top"<br />
| style="width:40%; border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Using this Website<br />
</h2><br />
This website is for technical documentation that supports kde users and developers<br />
<br />
* [[Style Guide]] -- conventions<br />
* [[meta:]] -- how to use mediawiki<br />
* [http://lists.kde.org|] and [[IRC]]<br />
* [[Meetup]]s (meetings between participants)<br />
* [[User groups|User groups]] <br />
<br />
| valign="top" style="border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Teams and Groups<br />
</h2><br />
What groups<br />
* [[GSoC|GSoC and SoK]]<br />
* [[Akademy]]<br />
* [[KDE e.V.]]<br />
* [[KDE Edu]]<br />
* [[KDE PIM]]<br />
* [[Promo|KDE Promo]]<br />
* [[KDE Documentation]]<br />
* [[KDE Women]]<br />
* [[Sysadmin|KDE Sysadmin]]<br />
* [[Real-Time_Communication_and_Collaboration|Real-Time Communication and Collaboration (Telepathy)]]<br />
* [[Digikam|digiKam]]<br />
* [[Plasma|Plasma Project Team Coordination]]<br />
* [[Plasma Netbook Reference Platform]]<br />
* [[Krita| Krita, Painting for Digital Artists: Developer notebook]]<br />
* [[KDE GB| KDE GB, KDE in Britain]]<br />
* [[KDE Localization|KDE Localization]]<br />
* [[KDE.org|KDE.org Websites]]<br />
* [[Phonon]]<br />
* [[Common Task Videos]]<br />
* [[Elegance]] <br />
|- valign="top"<br />
| colspan="2" style="border:1px solid #AAA; padding:1em; background:#F9F9F9" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Wikimedia Foundation|action=edit}} edit]]<br />
</span><br />
Wikimedia Foundation, Meta-Wiki, and its sister projects<br />
</h2><br />
{{Wikimedia Foundation}}{{Sisterprojects}}<br />
|}<br />
</div>__NOTOC__ __NOEDITSECTION__<br />
[[Category:Main page]]<br />
<br />
<br />
<br />
{|<br />
;[[Getting Started|Setting up a KDE development environment]]<br />
:Learn how to get, build and run KDE.<br />
<br />
<br />
;[[Development|Developing with KDE]]<br />
:[[Development/Tutorials|Tutorials]] <br />
[http://api.kde.org API Documentation] <br />
[[Development/FAQs|FAQs]] and more.<br />
:''Related'': [[Schedules|Release Schedules and Feature Plans]] <br />
[[Policies|Code Contribution and Development Guidelines]]<br />
<br />
;[[KDE System Administration]]<br />
:Information for system administrators managing KDE deployments. <br />
<br />
[[Image:Interact.png|noframe]]<br />
<br />
<br />
[[Contribute|Join the KDE Team and Contribute]]<br />
:Contribute patches, keep in touch with and join our community.<br />
:''Related:'' [[Policies|KDE Project Policies]] | [http://www.kde.org/support/support.php Donate Money]<br />
<br />
;[[ISV|ISV Information]]<br />
:Developer information for Independent Software Vendors.<br />
<br />
<br />
;[[Projects|KDE projects]]<br />
:Links to development wikis, task lists, etc. for various KDE Projects.</div>AaronPetersonhttps://techbase.kde.org/index.php?title=User:AaronPeterson/Welcome_to_KDE_TechBase/20100805/&diff=53282User:AaronPeterson/Welcome to KDE TechBase/20100805/2010-08-09T01:27:40Z<p>AaronPeterson: </p>
<hr />
<div><div class="plainlinks"><br />
<!-- WELCOME TO META BOX --><br />
<div class="toccolours" style="padding:1em;"><br />
<div style="float: right;"><br />
[[File:KDE.jpg]]<br />
</div><br />
<br />
<div style="font-size: 115%; margin-right: 80px;"><br />
Welcome to the [[KDE]] [[Wiki]]. The K Desktop Enviornment is a software compilation that provides the user interface for many Linux, BSD distributions. (also available for Windows and Mac)<br />
<!-- probably to update the transclusions--><br />
<div style="font-size: 75%">[{{fullurl:Main Page|action=purge}} Purge cache]</div><br />
<br />
</div><br />
<hr style="clear: both;" /><br />
<div style="font-weight: bold; text-align: center;"><br />
<br />
[[Getting Started]] •<br />
[[Tasks]] • <br />
[[Projects]] •<br />
[[UserBase]] •<br />
[[TechBase]] •<br />
[[CommBase]] •<br />
[[Development]] <br />
<br />
<br style="clear: both;" /><br />
</div><br />
</div><br />
<!-- TechBase IN MANY LANGUAGES --><br />
<div style="padding:1em; background:#FFEFF0; border:1px solid #AAA; margin:1px 0;"><br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
</span><br />
TechBase is available in many languages!<br />
</h2><br />
{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}<br />
</div><br />
{| cellspacing="1"<br />
|- valign="top"<br />
| style="width:50%; border:1px solid #AAA; padding:1em; background:#E4FFDF;" |<br />
<!-- Our Content --><br />
<br />
=== [[Using]] ===<br />
; [[Get KDE]]<br />
; [[Tasks]]<br />
; [[Applications]]<br />
; [[Vocabulary]]<br />
<br />
== [[Administrating]] ==<br />
; Kiosk<br />
; Configuration<br />
; Case Studies<br />
<br />
=== [[Building]] ===<br />
; Distributions<br />
; For Developers <br />
; For Personal Use<br />
<br />
=== [[Developing]] ===<br />
; Core KDE Libraries<br />
; Existing Applications<br />
; New applications<br />
; System <br />
<br />
=== [[Contributing]] ===<br />
; Financially<br />
; By collaborating<br />
<br />
=== Community ===<br />
; Governance<br />
; ev<br />
<!-- NOTIFICATIONS --><br />
| valign="top" style="width:50%; border:1px solid #AAA; padding:1em; background:#E8F1FF;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Information_thread|action=watch}} watch]]<br />
[[{{fullurl:Template:Information_thread|action=edit}} edit]]<br />
[[{{fullurl:Goings-on/{{CURRENTYEAR}}}} '''read older news''']]<br />
</span><br />
Notifications<br />
</h2><br />
{{Information thread}}<br />
<br />
|- valign="top"<br />
| style="width:40%; border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Using this Website<br />
</h2><br />
This website is for technical documentation that supports kde users and developers<br />
<br />
* [[Style Guide]] -- conventions<br />
* [[meta:]] -- how to use mediawiki<br />
* [http://lists.kde.org|] and [[IRC]]<br />
* [[Meetup]]s (meetings between participants)<br />
* [[User groups|User groups]] <br />
<br />
| valign="top" style="border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Teams and Groups<br />
</h2><br />
What groups<br />
* [[GSoC|GSoC and SoK]]<br />
* [[Akademy]]<br />
* [[KDE e.V.]]<br />
* [[KDE Edu]]<br />
* [[KDE PIM]]<br />
* [[Promo|KDE Promo]]<br />
* [[KDE Documentation]]<br />
* [[KDE Women]]<br />
* [[Sysadmin|KDE Sysadmin]]<br />
* [[Real-Time_Communication_and_Collaboration|Real-Time Communication and Collaboration (Telepathy)]]<br />
* [[Digikam|digiKam]]<br />
* [[Plasma|Plasma Project Team Coordination]]<br />
* [[Plasma Netbook Reference Platform]]<br />
* [[Krita| Krita, Painting for Digital Artists: Developer notebook]]<br />
* [[KDE GB| KDE GB, KDE in Britain]]<br />
* [[KDE Localization|KDE Localization]]<br />
* [[KDE.org|KDE.org Websites]]<br />
* [[Phonon]]<br />
* [[Common Task Videos]]<br />
* [[Elegance]] <br />
|- valign="top"<br />
| colspan="2" style="border:1px solid #AAA; padding:1em; background:#F9F9F9" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Wikimedia Foundation|action=edit}} edit]]<br />
</span><br />
Wikimedia Foundation, Meta-Wiki, and its sister projects<br />
</h2><br />
{{Wikimedia Foundation}}{{Sisterprojects}}<br />
|}<br />
</div>__NOTOC__ __NOEDITSECTION__<br />
[[Category:Main page]]<br />
<br />
<br />
<br />
{|<br />
;[[Getting Started|Setting up a KDE development environment]]<br />
:Learn how to get, build and run KDE.<br />
<br />
<br />
;[[Development|Developing with KDE]]<br />
:[[Development/Tutorials|Tutorials]] <br />
[http://api.kde.org API Documentation] <br />
[[Development/FAQs|FAQs]] and more.<br />
:''Related'': [[Schedules|Release Schedules and Feature Plans]] <br />
[[Policies|Code Contribution and Development Guidelines]]<br />
<br />
;[[KDE System Administration]]<br />
:Information for system administrators managing KDE deployments. <br />
<br />
[[Image:Interact.png|noframe]]<br />
<br />
<br />
[[Contribute|Join the KDE Team and Contribute]]<br />
:Contribute patches, keep in touch with and join our community.<br />
:''Related:'' [[Policies|KDE Project Policies]] | [http://www.kde.org/support/support.php Donate Money]<br />
<br />
;[[ISV|ISV Information]]<br />
:Developer information for Independent Software Vendors.<br />
<br />
<br />
;[[Projects|KDE projects]]<br />
:Links to development wikis, task lists, etc. for various KDE Projects.</div>AaronPetersonhttps://techbase.kde.org/index.php?title=User:AaronPeterson/Welcome_to_KDE_TechBase/20100805/&diff=53281User:AaronPeterson/Welcome to KDE TechBase/20100805/2010-08-09T01:21:56Z<p>AaronPeterson: </p>
<hr />
<div><div class="plainlinks"><br />
<!-- WELCOME TO META BOX --><br />
<div class="toccolours" style="padding:1em;"><br />
<div style="float: right;"><br />
[[File:Discover.jpg]]<br />
</div><br />
<br />
<div style="font-size: 115%; margin-right: 80px;"><br />
Welcome to the [[KDE]] [[Wiki]]. The K Desktop Enviornment is a software compilation that provides the user interface for many Linux, BSD distributions. (also available for Windows and Mac)<br />
<!-- probably to update the transclusions--><br />
<div style="font-size: 75%">[{{fullurl:Main Page|action=purge}} Purge cache]</div><br />
<br />
</div><br />
<hr style="clear: both;" /><br />
<div style="font-weight: bold; text-align: center;"><br />
[[Projects]] • <br />
[[Mission]] • <br />
[[Vision]] • <br />
<br style="clear: both;" /><br />
</div><br />
</div><br />
<!-- TechBase IN MANY LANGUAGES --><br />
<div style="padding:1em; background:#FFEFF0; border:1px solid #AAA; margin:1px 0;"><br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
</span><br />
TechBase is available in many languages!<br />
</h2><br />
{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}<br />
</div><br />
{| cellspacing="1"<br />
|- valign="top"<br />
| style="width:50%; border:1px solid #AAA; padding:1em; background:#E4FFDF;" |<br />
<!-- Our Content --><br />
<br />
=== [[Using]] ===<br />
; [[Get KDE]]<br />
; [[Tasks]]<br />
; [[Applications]]<br />
; [[Vocabulary]]<br />
<br />
== [[Administrating]] ==<br />
; Kiosk<br />
; Configuration<br />
; Case Studies<br />
<br />
=== [[Building]] ===<br />
; Distributions<br />
; For Developers <br />
; For Personal Use<br />
<br />
=== [[Developing]] ===<br />
; Core KDE Libraries<br />
; Existing Applications<br />
; New applications<br />
; System <br />
<br />
=== [[Contributing]] ===<br />
; Financially<br />
; By collaborating<br />
<br />
=== Community ===<br />
; Governance<br />
; ev<br />
<!-- NOTIFICATIONS --><br />
| valign="top" style="width:50%; border:1px solid #AAA; padding:1em; background:#E8F1FF;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Information_thread|action=watch}} watch]]<br />
[[{{fullurl:Template:Information_thread|action=edit}} edit]]<br />
[[{{fullurl:Goings-on/{{CURRENTYEAR}}}} '''read older news''']]<br />
</span><br />
Notifications<br />
</h2><br />
{{Information thread}}<br />
<br />
|- valign="top"<br />
| style="width:40%; border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Using this Website<br />
</h2><br />
This website is for technical documentation that supports kde users and developers<br />
<br />
* [[Style Guide]] -- conventions<br />
* [[meta:]] -- how to use mediawiki<br />
* [http://lists.kde.org|] and [[IRC]]<br />
* [[Meetup]]s (meetings between participants)<br />
* [[User groups|User groups]] <br />
<br />
| valign="top" style="border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Teams and Groups<br />
</h2><br />
What groups<br />
* [[GSoC|GSoC and SoK]]<br />
* [[Akademy]]<br />
* [[KDE e.V.]]<br />
* [[KDE Edu]]<br />
* [[KDE PIM]]<br />
* [[Promo|KDE Promo]]<br />
* [[KDE Documentation]]<br />
* [[KDE Women]]<br />
* [[Sysadmin|KDE Sysadmin]]<br />
* [[Real-Time_Communication_and_Collaboration|Real-Time Communication and Collaboration (Telepathy)]]<br />
* [[Digikam|digiKam]]<br />
* [[Plasma|Plasma Project Team Coordination]]<br />
* [[Plasma Netbook Reference Platform]]<br />
* [[Krita| Krita, Painting for Digital Artists: Developer notebook]]<br />
* [[KDE GB| KDE GB, KDE in Britain]]<br />
* [[KDE Localization|KDE Localization]]<br />
* [[KDE.org|KDE.org Websites]]<br />
* [[Phonon]]<br />
* [[Common Task Videos]]<br />
* [[Elegance]] <br />
|- valign="top"<br />
| colspan="2" style="border:1px solid #AAA; padding:1em; background:#F9F9F9" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Wikimedia Foundation|action=edit}} edit]]<br />
</span><br />
Wikimedia Foundation, Meta-Wiki, and its sister projects<br />
</h2><br />
{{Wikimedia Foundation}}{{Sisterprojects}}<br />
|}<br />
</div>__NOTOC__ __NOEDITSECTION__<br />
[[Category:Main page]]<br />
<br />
<br />
<br />
{|<br />
;[[Getting Started|Setting up a KDE development environment]]<br />
:Learn how to get, build and run KDE.<br />
<br />
<br />
;[[Development|Developing with KDE]]<br />
:[[Development/Tutorials|Tutorials]] <br />
[http://api.kde.org API Documentation] <br />
[[Development/FAQs|FAQs]] and more.<br />
:''Related'': [[Schedules|Release Schedules and Feature Plans]] <br />
[[Policies|Code Contribution and Development Guidelines]]<br />
<br />
;[[KDE System Administration]]<br />
:Information for system administrators managing KDE deployments. <br />
<br />
[[Image:Interact.png|noframe]]<br />
<br />
<br />
[[Contribute|Join the KDE Team and Contribute]]<br />
:Contribute patches, keep in touch with and join our community.<br />
:''Related:'' [[Policies|KDE Project Policies]] | [http://www.kde.org/support/support.php Donate Money]<br />
<br />
;[[ISV|ISV Information]]<br />
:Developer information for Independent Software Vendors.<br />
<br />
<br />
;[[Projects|KDE projects]]<br />
:Links to development wikis, task lists, etc. for various KDE Projects.</div>AaronPetersonhttps://techbase.kde.org/index.php?title=User:AaronPeterson/Welcome_to_KDE_TechBase/20100805/&diff=53280User:AaronPeterson/Welcome to KDE TechBase/20100805/2010-08-09T01:17:55Z<p>AaronPeterson: trying to throw Nokia a bone</p>
<hr />
<div><div class="plainlinks"><br />
<!-- WELCOME TO META BOX --><br />
<div class="toccolours" style="padding:1em;"><br />
<div style="float: right;"><br />
[[File:Discover.jpg]]<br />
</div><br />
<br />
<div style="font-size: 115%; margin-right: 80px;"><br />
This is the [[KDE]] [[Wiki]]. The K Desktop Enviornment is a software compilation that provides the user interface for many Linux, BSD distributions. It is also available for Windows and Mac. We are known for style, code reuse, reconfigurability, research and for being free! Our software utilizes on Nokia's GPL Qt libraries, so [[development]] is easy, fast, and powerful.<br />
<br />
[[IRC|IRC channels]]<br />
<div style="font-size: 75%">[{{fullurl:Main Page|action=purge}} Purge cache]</div><br />
</div><br />
<hr style="clear: both;" /><br />
<div style="font-weight: bold; text-align: center;"><br />
[[Wikimedia projects|Projects]] ([[Complete list of Wikimedia projects|complete list]]) • <br />
[[Mission]] • <br />
[[Vision]] • <br />
[[Meta:Babylon|Translation]] ([[Translation requests|requests]])<br />
<br style="clear: both;" /><br />
</div><br />
</div><br />
<!-- TechBase IN MANY LANGUAGES --><br />
<div style="padding:1em; background:#FFEFF0; border:1px solid #AAA; margin:1px 0;"><br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
</span><br />
TechBase is available in many languages!<br />
</h2><br />
{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}<br />
</div><br />
{| cellspacing="1"<br />
|- valign="top"<br />
| style="width:50%; border:1px solid #AAA; padding:1em; background:#E4FFDF;" |<br />
<!-- Our Content --><br />
<br />
=== [[Using]] ===<br />
; [[Get KDE]]<br />
; [[Tasks]]<br />
; [[Applications]]<br />
; [[Vocabulary]]<br />
<br />
== [[Administrating]] ==<br />
; Kiosk<br />
; Configuration<br />
; Case Studies<br />
<br />
=== [[Building]] ===<br />
; Distributions<br />
; For Developers <br />
; For Personal Use<br />
<br />
=== [[Developing]] ===<br />
; Core KDE Libraries<br />
; Existing Applications<br />
; New applications<br />
; System <br />
<br />
=== [[Contributing]] ===<br />
; Financially<br />
; By collaborating<br />
<br />
=== Community ===<br />
; Governance<br />
; ev<br />
<!-- NOTIFICATIONS --><br />
| valign="top" style="width:50%; border:1px solid #AAA; padding:1em; background:#E8F1FF;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Information_thread|action=watch}} watch]]<br />
[[{{fullurl:Template:Information_thread|action=edit}} edit]]<br />
[[{{fullurl:Goings-on/{{CURRENTYEAR}}}} '''read older news''']]<br />
</span><br />
Notifications<br />
</h2><br />
{{Information thread}}<br />
<br />
|- valign="top"<br />
| style="width:40%; border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Using this Website<br />
</h2><br />
This website is for technical documentation that supports kde users and developers<br />
<br />
* [[Style Guide]] -- conventions<br />
* [[meta:]] -- how to use mediawiki<br />
* [http://lists.kde.org|] and [[IRC]]<br />
* [[Meetup]]s (meetings between participants)<br />
* [[User groups|User groups]] <br />
<br />
| valign="top" style="border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Teams and Groups<br />
</h2><br />
What groups<br />
* [[GSoC|GSoC and SoK]]<br />
* [[Akademy]]<br />
* [[KDE e.V.]]<br />
* [[KDE Edu]]<br />
* [[KDE PIM]]<br />
* [[Promo|KDE Promo]]<br />
* [[KDE Documentation]]<br />
* [[KDE Women]]<br />
* [[Sysadmin|KDE Sysadmin]]<br />
* [[Real-Time_Communication_and_Collaboration|Real-Time Communication and Collaboration (Telepathy)]]<br />
* [[Digikam|digiKam]]<br />
* [[Plasma|Plasma Project Team Coordination]]<br />
* [[Plasma Netbook Reference Platform]]<br />
* [[Krita| Krita, Painting for Digital Artists: Developer notebook]]<br />
* [[KDE GB| KDE GB, KDE in Britain]]<br />
* [[KDE Localization|KDE Localization]]<br />
* [[KDE.org|KDE.org Websites]]<br />
* [[Phonon]]<br />
* [[Common Task Videos]]<br />
* [[Elegance]] <br />
|- valign="top"<br />
| colspan="2" style="border:1px solid #AAA; padding:1em; background:#F9F9F9" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Wikimedia Foundation|action=edit}} edit]]<br />
</span><br />
Wikimedia Foundation, Meta-Wiki, and its sister projects<br />
</h2><br />
{{Wikimedia Foundation}}{{Sisterprojects}}<br />
|}<br />
</div>__NOTOC__ __NOEDITSECTION__<br />
[[Category:Main page]]<br />
<br />
<br />
<br />
{|<br />
;[[Getting Started|Setting up a KDE development environment]]<br />
:Learn how to get, build and run KDE.<br />
<br />
<br />
;[[Development|Developing with KDE]]<br />
:[[Development/Tutorials|Tutorials]] <br />
[http://api.kde.org API Documentation] <br />
[[Development/FAQs|FAQs]] and more.<br />
:''Related'': [[Schedules|Release Schedules and Feature Plans]] <br />
[[Policies|Code Contribution and Development Guidelines]]<br />
<br />
;[[KDE System Administration]]<br />
:Information for system administrators managing KDE deployments. <br />
<br />
[[Image:Interact.png|noframe]]<br />
<br />
<br />
[[Contribute|Join the KDE Team and Contribute]]<br />
:Contribute patches, keep in touch with and join our community.<br />
:''Related:'' [[Policies|KDE Project Policies]] | [http://www.kde.org/support/support.php Donate Money]<br />
<br />
;[[ISV|ISV Information]]<br />
:Developer information for Independent Software Vendors.<br />
<br />
<br />
;[[Projects|KDE projects]]<br />
:Links to development wikis, task lists, etc. for various KDE Projects.</div>AaronPetersonhttps://techbase.kde.org/index.php?title=User:AaronPeterson/Welcome_to_KDE_TechBase/20100805/&diff=53274User:AaronPeterson/Welcome to KDE TechBase/20100805/2010-08-08T09:41:49Z<p>AaronPeterson: Need to keep it below 9th grade reading level, (got kind of into writing colorful metaphors that wouldn't translate well ;)</p>
<hr />
<div><div class="plainlinks"><br />
<!-- WELCOME TO META BOX --><br />
<div class="toccolours" style="padding:1em;"><br />
<div style="float: right;"><br />
[[File:Discover.jpg]]<br />
</div><br />
<br />
<div style="font-size: 115%; margin-right: 80px;"><br />
K Desktop Enviornment Software Compilation [[KDE]] is the main user interface of Suse, Kubuntu, LinuxMint and is available for most platforms including, Linux, Windows and Mac. It is known for it's [[style]] and cutting edge user interface.<br />
<br />
This is our [[wiki]] where we write down stuff to help each other.<br />
<br />
<br />
[[IRC|IRC channels]]<br />
<div style="font-size: 75%">[{{fullurl:Main Page|action=purge}} Purge cache]</div><br />
</div><br />
<hr style="clear: both;" /><br />
<div style="font-weight: bold; text-align: center;"><br />
[[Wikimedia projects|Projects]] ([[Complete list of Wikimedia projects|complete list]]) • <br />
[[Mission]] • <br />
[[Vision]] • <br />
[[Meta:Babylon|Translation]] ([[Translation requests|requests]])<br />
<br style="clear: both;" /><br />
</div><br />
</div><br />
<!-- TechBase IN MANY LANGUAGES --><br />
<div style="padding:1em; background:#FFEFF0; border:1px solid #AAA; margin:1px 0;"><br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
</span><br />
TechBase is available in many languages!<br />
</h2><br />
{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}<br />
</div><br />
{| cellspacing="1"<br />
|- valign="top"<br />
| style="width:50%; border:1px solid #AAA; padding:1em; background:#E4FFDF;" |<br />
<!-- Our Content --><br />
<br />
=== [[Using]] ===<br />
; [[Get KDE]]<br />
; [[Tasks]]<br />
; [[Applications]]<br />
; [[Vocabulary]]<br />
<br />
== [[Administrating]] ==<br />
; Kiosk<br />
; Configuration<br />
; Case Studies<br />
<br />
=== [[Building]] ===<br />
; Distributions<br />
; For Developers <br />
; For Personal Use<br />
<br />
=== [[Developing]] ===<br />
; Core KDE Libraries<br />
; Existing Applications<br />
; New applications<br />
; System <br />
<br />
=== [[Contributing]] ===<br />
; Financially<br />
; By collaborating<br />
<br />
=== Community ===<br />
; Governance<br />
; ev<br />
<!-- NOTIFICATIONS --><br />
| valign="top" style="width:50%; border:1px solid #AAA; padding:1em; background:#E8F1FF;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Information_thread|action=watch}} watch]]<br />
[[{{fullurl:Template:Information_thread|action=edit}} edit]]<br />
[[{{fullurl:Goings-on/{{CURRENTYEAR}}}} '''read older news''']]<br />
</span><br />
Notifications<br />
</h2><br />
{{Information thread}}<br />
<br />
|- valign="top"<br />
| style="width:40%; border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Using this Website<br />
</h2><br />
This website is for technical documentation that supports kde users and developers<br />
<br />
* [[Style Guide]] -- conventions<br />
* [[meta:]] -- how to use mediawiki<br />
* [http://lists.kde.org|] and [[IRC]]<br />
* [[Meetup]]s (meetings between participants)<br />
* [[User groups|User groups]] <br />
<br />
| valign="top" style="border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Teams and Groups<br />
</h2><br />
What groups<br />
* [[GSoC|GSoC and SoK]]<br />
* [[Akademy]]<br />
* [[KDE e.V.]]<br />
* [[KDE Edu]]<br />
* [[KDE PIM]]<br />
* [[Promo|KDE Promo]]<br />
* [[KDE Documentation]]<br />
* [[KDE Women]]<br />
* [[Sysadmin|KDE Sysadmin]]<br />
* [[Real-Time_Communication_and_Collaboration|Real-Time Communication and Collaboration (Telepathy)]]<br />
* [[Digikam|digiKam]]<br />
* [[Plasma|Plasma Project Team Coordination]]<br />
* [[Plasma Netbook Reference Platform]]<br />
* [[Krita| Krita, Painting for Digital Artists: Developer notebook]]<br />
* [[KDE GB| KDE GB, KDE in Britain]]<br />
* [[KDE Localization|KDE Localization]]<br />
* [[KDE.org|KDE.org Websites]]<br />
* [[Phonon]]<br />
* [[Common Task Videos]]<br />
* [[Elegance]] <br />
|- valign="top"<br />
| colspan="2" style="border:1px solid #AAA; padding:1em; background:#F9F9F9" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Wikimedia Foundation|action=edit}} edit]]<br />
</span><br />
Wikimedia Foundation, Meta-Wiki, and its sister projects<br />
</h2><br />
{{Wikimedia Foundation}}{{Sisterprojects}}<br />
|}<br />
</div>__NOTOC__ __NOEDITSECTION__<br />
[[Category:Main page]]<br />
<br />
<br />
<br />
{|<br />
;[[Getting Started|Setting up a KDE development environment]]<br />
:Learn how to get, build and run KDE.<br />
<br />
<br />
;[[Development|Developing with KDE]]<br />
:[[Development/Tutorials|Tutorials]] <br />
[http://api.kde.org API Documentation] <br />
[[Development/FAQs|FAQs]] and more.<br />
:''Related'': [[Schedules|Release Schedules and Feature Plans]] <br />
[[Policies|Code Contribution and Development Guidelines]]<br />
<br />
;[[KDE System Administration]]<br />
:Information for system administrators managing KDE deployments. <br />
<br />
[[Image:Interact.png|noframe]]<br />
<br />
<br />
[[Contribute|Join the KDE Team and Contribute]]<br />
:Contribute patches, keep in touch with and join our community.<br />
:''Related:'' [[Policies|KDE Project Policies]] | [http://www.kde.org/support/support.php Donate Money]<br />
<br />
;[[ISV|ISV Information]]<br />
:Developer information for Independent Software Vendors.<br />
<br />
<br />
;[[Projects|KDE projects]]<br />
:Links to development wikis, task lists, etc. for various KDE Projects.</div>AaronPetersonhttps://techbase.kde.org/index.php?title=User:AaronPeterson/Welcome_to_KDE_TechBase/20100805/&diff=53273User:AaronPeterson/Welcome to KDE TechBase/20100805/2010-08-08T09:22:26Z<p>AaronPeterson: a few good changes</p>
<hr />
<div><div class="plainlinks"><br />
<!-- WELCOME TO META BOX --><br />
<div class="toccolours" style="padding:1em;"><br />
<div style="float: right;"><br />
[[File:Discover.jpg]]<br />
</div><br />
<br />
<div style="font-size: 115%; margin-right: 80px;"><br />
'''Welcome to [[KDE Techbase Wiki]]''', the global community...developer site for the [[projects]], and [[coordination]] and [[documentation]] of the KDE community. For Governance issues, please visit http://community.kde.org For further information, see http://lists.kde.org [[IRC|IRC channels]]<br />
<div style="font-size: 75%">[{{fullurl:Main Page|action=purge}} Purge cache]</div><br />
</div><br />
<hr style="clear: both;" /><br />
<div style="font-weight: bold; text-align: center;"><br />
[[Wikimedia projects|Projects]] ([[Complete list of Wikimedia projects|complete list]]) • <br />
[[Mission]] • <br />
[[Vision]] • <br />
[[Meta:Babylon|Translation]] ([[Translation requests|requests]])<br />
<br style="clear: both;" /><br />
</div><br />
</div><br />
<!-- TechBase IN MANY LANGUAGES --><br />
<div style="padding:1em; background:#FFEFF0; border:1px solid #AAA; margin:1px 0;"><br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
</span><br />
TechBase is available in many languages!<br />
</h2><br />
{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}<br />
</div><br />
{| cellspacing="1"<br />
|- valign="top"<br />
| style="width:50%; border:1px solid #AAA; padding:1em; background:#E4FFDF;" |<br />
<!-- Our Content --><br />
<br />
=== [[Using]] ===<br />
; [[Get KDE]]<br />
; [[Tasks]]<br />
; [[Applications]]<br />
; [[Vocabulary]]<br />
<br />
== [[Administrating]] ==<br />
; Kiosk<br />
; Configuration<br />
; Case Studies<br />
<br />
=== [[Building]] ===<br />
; Distributions<br />
; For Developers <br />
; For Personal Use<br />
<br />
=== [[Developing]] ===<br />
; Core KDE Libraries<br />
; Existing Applications<br />
; New applications<br />
; System <br />
<br />
=== [[Contributing]] ===<br />
; Financially<br />
; By collaborating<br />
<br />
=== Community ===<br />
; Governance<br />
; ev<br />
<!-- NOTIFICATIONS --><br />
| valign="top" style="width:50%; border:1px solid #AAA; padding:1em; background:#E8F1FF;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Information_thread|action=watch}} watch]]<br />
[[{{fullurl:Template:Information_thread|action=edit}} edit]]<br />
[[{{fullurl:Goings-on/{{CURRENTYEAR}}}} '''read older news''']]<br />
</span><br />
Notifications<br />
</h2><br />
{{Information thread}}<br />
<br />
|- valign="top"<br />
| style="width:40%; border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Using this Website<br />
</h2><br />
This website is for technical documentation that supports kde users and developers<br />
<br />
* [[Style Guide]] -- conventions<br />
* [[meta:]] -- how to use mediawiki<br />
* [http://lists.kde.org|] and [[IRC]]<br />
* [[Meetup]]s (meetings between participants)<br />
* [[User groups|User groups]] <br />
<br />
| valign="top" style="border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Teams and Groups<br />
</h2><br />
What groups<br />
* [[GSoC|GSoC and SoK]]<br />
* [[Akademy]]<br />
* [[KDE e.V.]]<br />
* [[KDE Edu]]<br />
* [[KDE PIM]]<br />
* [[Promo|KDE Promo]]<br />
* [[KDE Documentation]]<br />
* [[KDE Women]]<br />
* [[Sysadmin|KDE Sysadmin]]<br />
* [[Real-Time_Communication_and_Collaboration|Real-Time Communication and Collaboration (Telepathy)]]<br />
* [[Digikam|digiKam]]<br />
* [[Plasma|Plasma Project Team Coordination]]<br />
* [[Plasma Netbook Reference Platform]]<br />
* [[Krita| Krita, Painting for Digital Artists: Developer notebook]]<br />
* [[KDE GB| KDE GB, KDE in Britain]]<br />
* [[KDE Localization|KDE Localization]]<br />
* [[KDE.org|KDE.org Websites]]<br />
* [[Phonon]]<br />
* [[Common Task Videos]]<br />
* [[Elegance]] <br />
|- valign="top"<br />
| colspan="2" style="border:1px solid #AAA; padding:1em; background:#F9F9F9" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Wikimedia Foundation|action=edit}} edit]]<br />
</span><br />
Wikimedia Foundation, Meta-Wiki, and its sister projects<br />
</h2><br />
{{Wikimedia Foundation}}{{Sisterprojects}}<br />
|}<br />
</div>__NOTOC__ __NOEDITSECTION__<br />
[[Category:Main page]]<br />
<br />
<br />
<br />
{|<br />
;[[Getting Started|Setting up a KDE development environment]]<br />
:Learn how to get, build and run KDE.<br />
<br />
<br />
;[[Development|Developing with KDE]]<br />
:[[Development/Tutorials|Tutorials]] <br />
[http://api.kde.org API Documentation] <br />
[[Development/FAQs|FAQs]] and more.<br />
:''Related'': [[Schedules|Release Schedules and Feature Plans]] <br />
[[Policies|Code Contribution and Development Guidelines]]<br />
<br />
;[[KDE System Administration]]<br />
:Information for system administrators managing KDE deployments. <br />
<br />
[[Image:Interact.png|noframe]]<br />
<br />
<br />
[[Contribute|Join the KDE Team and Contribute]]<br />
:Contribute patches, keep in touch with and join our community.<br />
:''Related:'' [[Policies|KDE Project Policies]] | [http://www.kde.org/support/support.php Donate Money]<br />
<br />
;[[ISV|ISV Information]]<br />
:Developer information for Independent Software Vendors.<br />
<br />
<br />
;[[Projects|KDE projects]]<br />
:Links to development wikis, task lists, etc. for various KDE Projects.</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Template:Information_thread&diff=53270Template:Information thread2010-08-07T21:02:02Z<p>AaronPeterson: </p>
<hr />
<div>Names of these files will need to be changed, but the transclusion is awesome!<br />
<br />
=== Latest Features ===<br />
KDE 4.5 is now faster and has 2x more yum. Many small improvements to<br />
[[Plasmoid Handles]]<br />
<br />
[[Release Log]]<br />
<br />
<br />
===Release Plan===<br />
Read up here [[]]<br />
Integration team is focusing on sharing Tool Tip features and icon actions<br />
<br />
<br />
=== Independent Development ===<br />
Who you are and what you are working on</div>AaronPetersonhttps://techbase.kde.org/index.php?title=User:AaronPeterson&diff=53269User:AaronPeterson2010-08-07T20:58:44Z<p>AaronPeterson: /* This Wiki */</p>
<hr />
<div>Aaron Peterson lives in Washington State USA. and has contriubted to various wikis including openwiki.org one of the gentoo wikis and wikipedias metawiki. as of 2010.07 Aaron is a novice programmer, who has done a bit of WMI, Javascript, C, and has followed a few C++ and QT tutorials, so he is very much learning and new to the process.<br />
<br />
==Request for HELP==<br />
None currently, Aaron helped wean me from my psychological dependence on kdesrc-build<br />
<br />
== Wiki ==<br />
===style===<br />
Aaron generally organizes then polishes, Some users may be offended by misspellings or hanging links to pages that do not exist, and making placeholders for content that he thinks should go there.<br />
<br />
<br />
He likes using categories whenever possible.<br />
==== Style II ====<br />
I find that wiki's especially, mediawiki, get misused when in techbase role. It is important to use Categories, and NOT subdirectories so that wiki linking becomes easy. Filing something under [[Getting Started]] is a horrible way to do it, because the item will also be related to the <nowiki>[[Topic]]</nowiki> In general, sub pages should be used only if the topic page is too large, and the additional content is exclusive to the topic. I hope to re-arrange the wiki to make it easier to navigate.<br />
<br />
===ethics===<br />
Aaron will move content about and adjust sentence structure to get right to the point. He rarely deletes content, rather, prefers to move it to new pages.<br />
<br />
=== frequency Noise===<br />
I talk a lot, I am learning about projects that i interact with, and hope that I am actually contributing. I want to give a high signal to noise, and I have a lot of time right now (July 2010) and am running with high enthusiasm.<br />
<br />
<br />
<br />
== Person ==<br />
=== Contact Info ===<br />
Aaron generally cares a great deal about the projects he works on and would very much enjoy talking with what they are working on, and requests help learning this stuff.<br />
<br />
Telephone: 206 334 5925<br />
<br />
=== Creativity ===<br />
Part of my creativity comes from experimentation. I try a lot of things, and I believe i have a talent for testing software, and creating user interfaces.<br />
<br />
== Bugs ==<br />
I file a lot of bugs and wishlist items. Often the fix is not trivial, and does not fit exactly in the category I put the item... because I have no idea where it should go. For example, I don't think we should program based on click, double click, drag, I think we need more abstract concepts . <br />
<br />
I have filed bugs for bugzilla at mozilla regarding micropayment integration, and I tend to prefer Mantis as a bug/feature tracker. I also very much think that searching for existing bugs should go thru closed bugs and not just open bugs.<br />
<br />
<br />
== KDE ==<br />
<br />
Aaron has enjoyed using applications made in KDE and QT for quite some time, and has posted bugs. He would like to be considered a usability contributer and is attempting to set up a build environment to actually fix some of the behavior he cares deeply about.<br />
<br />
=== Learning ===<br />
[[/tutorials that are good]]<br />
[[/tutorials that do not work]]<br />
<br />
=== Specific bugs and enhancements ===<br />
* selecting items in dolphin and konqueror / dialogs are over-engineered and while simplify some very basic selection capability, complicates general use of the program.<br />
* Single vs double click -- Aaron cares very deeply about accidental clicks activating programs, and would like to seporate desired appliacation behavior vs application use by creating a concept to make user interfaces easier.<br />
** Reversable-Safe-to-activate -- no-data-loss -- a button, single click, even moving a cursor over can trigger an event and this triggers no possiblity of data loss.<br />
** known-common-use - reversable - arranging content, a single button can trigger.<br />
** known-non-reversable<br />
an example would be a slide-lock on an iphone, a double click, or similar<br />
** known-dangerous<br />
a confirmation dialog/interuption of user is required.<br />
** unknown<br />
a confirmation dialog may be requried.<br />
==== plasma ====<br />
* [[\gridplasmoid]] for icons Seen in KDE3<br />
<br />
<br />
*show contents of directory--within a panel, not an icon to start a new window..<br />
*application plasmoids, task-bar like objects that organize application windows and documents, that stay persistant.. AND also provide taskbar like control ((all other implementations seen either are just like taskbars or completely hide content)<br />
* Note taking / journal plasmoid, that actually prepends to a simple text file. Saves like an instant messanger log, perhaps just instant message self in a note., (from anywhere) and have it save on the server.<br />
* [[/In panel run command]] There is a run plasmoid, it just manifests as an icon, and I don't want to click on an icon, then click again and type what I want to run.<br />
<br />
-- The active user interface field is IN the plasmoid, so one less click. (first seen with IE4beta but then removed.. also seen in KDE3)<br />
* Make applets have a choice weather to behave like a popupapplet or an applet<br />
(wishlist/bug filed: https://bugs.kde.org/show_bug.cgi?id=245124 ) Spent many many hours reading api / source code etc trying to figure this out ;) still<br />
<br />
<br />
<notmart> MrDarkUser: you reimplement void Applet::createConfigurationInterface(KConfigDialog *parent)<br />
<br />
<br />
==== KDE settings ====<br />
[[/kdesettingsFixes]]<br />
* wants to make kde settings behave as expected with single click, because they are all buttons/hyperlinks Not fileRepresentation.<br />
<br />
==== Dolphin ====<br />
* adding more columns [[/MoreMetaDataInDolphin]]<br />
* Adding a view that allows grouping based on metadata<br />
* Making Details be accessible in Icon view<br />
* Make an Icon view that can be rearranged, not snapped to a grid.<br />
* Make Thumbnails be in their own column/ make filetype icon still show up even in iconview<br />
* Make DetailedIcon view, where metadata gets shown in same tile as icon.<br />
<br />
== Knotify ==<br />
. Need to have a filter on incoming messages, and present a log view. Would like to implement a time and check condition capability, conditions to check would be file is filesize, window has gotten focus, other things to help knotify if it should pop up that annyoing dialog. Also the application can send information like how many it expects to send.<br />
<br />
Would like all kinds of things to get logged. Deletion of files, trash cleared..... tons of stuff would be great to keep track of. sorting it would be a pain tho.<br />
<br />
==social networking ==<br />
kreactor<br />
overheard a conversation and started thinking about using it to make a social networking portal<br />
alternative -- standards based websites that people put up themselves (already a project)<br />
(facebook afterall, is just a glorified, centralized log analyzer that can trigger alarms) We could eventually string all of our instant messages thru our log analyzer, have it show us what we want, and retransmit based on rules if certain conditions are met. <br />
<br />
* (social networking use is probably best in a sub page [[/NotificationLogAnalyzerAsSocialNetworking]]<br />
<br />
* http://lists.kde.org/?l=kde-core-devel&m=127935490806410&w=2<br />
* http://bugs.kde.org/show_bug.cgi?id=215229<br />
* Telepathy<br />
<br />
== Development ==<br />
http://forums.gentoo.org/viewtopic-p-6368828.html#6368828<br />
<br />
I still don't kknow how<br />
{{help|building}}<br />
[[/kdesrc-build-stories]]<br />
<br />
== Build it ==<br />
[[/build]]<br />
<br />
== This Wiki ==<br />
[[Welcome_to_KDE_TechBase/20100805/]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=User:AaronPeterson&diff=53268User:AaronPeterson2010-08-07T20:57:52Z<p>AaronPeterson: /* Build it */</p>
<hr />
<div>Aaron Peterson lives in Washington State USA. and has contriubted to various wikis including openwiki.org one of the gentoo wikis and wikipedias metawiki. as of 2010.07 Aaron is a novice programmer, who has done a bit of WMI, Javascript, C, and has followed a few C++ and QT tutorials, so he is very much learning and new to the process.<br />
<br />
==Request for HELP==<br />
None currently, Aaron helped wean me from my psychological dependence on kdesrc-build<br />
<br />
== Wiki ==<br />
===style===<br />
Aaron generally organizes then polishes, Some users may be offended by misspellings or hanging links to pages that do not exist, and making placeholders for content that he thinks should go there.<br />
<br />
<br />
He likes using categories whenever possible.<br />
==== Style II ====<br />
I find that wiki's especially, mediawiki, get misused when in techbase role. It is important to use Categories, and NOT subdirectories so that wiki linking becomes easy. Filing something under [[Getting Started]] is a horrible way to do it, because the item will also be related to the <nowiki>[[Topic]]</nowiki> In general, sub pages should be used only if the topic page is too large, and the additional content is exclusive to the topic. I hope to re-arrange the wiki to make it easier to navigate.<br />
<br />
===ethics===<br />
Aaron will move content about and adjust sentence structure to get right to the point. He rarely deletes content, rather, prefers to move it to new pages.<br />
<br />
=== frequency Noise===<br />
I talk a lot, I am learning about projects that i interact with, and hope that I am actually contributing. I want to give a high signal to noise, and I have a lot of time right now (July 2010) and am running with high enthusiasm.<br />
<br />
<br />
<br />
== Person ==<br />
=== Contact Info ===<br />
Aaron generally cares a great deal about the projects he works on and would very much enjoy talking with what they are working on, and requests help learning this stuff.<br />
<br />
Telephone: 206 334 5925<br />
<br />
=== Creativity ===<br />
Part of my creativity comes from experimentation. I try a lot of things, and I believe i have a talent for testing software, and creating user interfaces.<br />
<br />
== Bugs ==<br />
I file a lot of bugs and wishlist items. Often the fix is not trivial, and does not fit exactly in the category I put the item... because I have no idea where it should go. For example, I don't think we should program based on click, double click, drag, I think we need more abstract concepts . <br />
<br />
I have filed bugs for bugzilla at mozilla regarding micropayment integration, and I tend to prefer Mantis as a bug/feature tracker. I also very much think that searching for existing bugs should go thru closed bugs and not just open bugs.<br />
<br />
<br />
== KDE ==<br />
<br />
Aaron has enjoyed using applications made in KDE and QT for quite some time, and has posted bugs. He would like to be considered a usability contributer and is attempting to set up a build environment to actually fix some of the behavior he cares deeply about.<br />
<br />
=== Learning ===<br />
[[/tutorials that are good]]<br />
[[/tutorials that do not work]]<br />
<br />
=== Specific bugs and enhancements ===<br />
* selecting items in dolphin and konqueror / dialogs are over-engineered and while simplify some very basic selection capability, complicates general use of the program.<br />
* Single vs double click -- Aaron cares very deeply about accidental clicks activating programs, and would like to seporate desired appliacation behavior vs application use by creating a concept to make user interfaces easier.<br />
** Reversable-Safe-to-activate -- no-data-loss -- a button, single click, even moving a cursor over can trigger an event and this triggers no possiblity of data loss.<br />
** known-common-use - reversable - arranging content, a single button can trigger.<br />
** known-non-reversable<br />
an example would be a slide-lock on an iphone, a double click, or similar<br />
** known-dangerous<br />
a confirmation dialog/interuption of user is required.<br />
** unknown<br />
a confirmation dialog may be requried.<br />
==== plasma ====<br />
* [[\gridplasmoid]] for icons Seen in KDE3<br />
<br />
<br />
*show contents of directory--within a panel, not an icon to start a new window..<br />
*application plasmoids, task-bar like objects that organize application windows and documents, that stay persistant.. AND also provide taskbar like control ((all other implementations seen either are just like taskbars or completely hide content)<br />
* Note taking / journal plasmoid, that actually prepends to a simple text file. Saves like an instant messanger log, perhaps just instant message self in a note., (from anywhere) and have it save on the server.<br />
* [[/In panel run command]] There is a run plasmoid, it just manifests as an icon, and I don't want to click on an icon, then click again and type what I want to run.<br />
<br />
-- The active user interface field is IN the plasmoid, so one less click. (first seen with IE4beta but then removed.. also seen in KDE3)<br />
* Make applets have a choice weather to behave like a popupapplet or an applet<br />
(wishlist/bug filed: https://bugs.kde.org/show_bug.cgi?id=245124 ) Spent many many hours reading api / source code etc trying to figure this out ;) still<br />
<br />
<br />
<notmart> MrDarkUser: you reimplement void Applet::createConfigurationInterface(KConfigDialog *parent)<br />
<br />
<br />
==== KDE settings ====<br />
[[/kdesettingsFixes]]<br />
* wants to make kde settings behave as expected with single click, because they are all buttons/hyperlinks Not fileRepresentation.<br />
<br />
==== Dolphin ====<br />
* adding more columns [[/MoreMetaDataInDolphin]]<br />
* Adding a view that allows grouping based on metadata<br />
* Making Details be accessible in Icon view<br />
* Make an Icon view that can be rearranged, not snapped to a grid.<br />
* Make Thumbnails be in their own column/ make filetype icon still show up even in iconview<br />
* Make DetailedIcon view, where metadata gets shown in same tile as icon.<br />
<br />
== Knotify ==<br />
. Need to have a filter on incoming messages, and present a log view. Would like to implement a time and check condition capability, conditions to check would be file is filesize, window has gotten focus, other things to help knotify if it should pop up that annyoing dialog. Also the application can send information like how many it expects to send.<br />
<br />
Would like all kinds of things to get logged. Deletion of files, trash cleared..... tons of stuff would be great to keep track of. sorting it would be a pain tho.<br />
<br />
==social networking ==<br />
kreactor<br />
overheard a conversation and started thinking about using it to make a social networking portal<br />
alternative -- standards based websites that people put up themselves (already a project)<br />
(facebook afterall, is just a glorified, centralized log analyzer that can trigger alarms) We could eventually string all of our instant messages thru our log analyzer, have it show us what we want, and retransmit based on rules if certain conditions are met. <br />
<br />
* (social networking use is probably best in a sub page [[/NotificationLogAnalyzerAsSocialNetworking]]<br />
<br />
* http://lists.kde.org/?l=kde-core-devel&m=127935490806410&w=2<br />
* http://bugs.kde.org/show_bug.cgi?id=215229<br />
* Telepathy<br />
<br />
== Development ==<br />
http://forums.gentoo.org/viewtopic-p-6368828.html#6368828<br />
<br />
I still don't kknow how<br />
{{help|building}}<br />
[[/kdesrc-build-stories]]<br />
<br />
== Build it ==<br />
[[/build]]<br />
<br />
== This Wiki ==<br />
Welcome_to_KDE_TechBase/20100805/</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53262Getting Started2010-08-07T09:10:24Z<p>AaronPeterson: /* Choose Version */ shorten words for distribution synchronized, it can still get smaller and better.</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
Our content is generally written with KDE4 and Linux in mind, Windows and BSD and KDE3 look at [[Getting_Started/Build|other Supported Platforms]] page.<br />
<br />
== [[Choose Version]] ==<br />
; Distribution synchronized<br />
: To ease finding dependencies, See [[Distributions with KDE]], or you may have a requirement to support a version supplied by a vendor.<br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] Where new features grow (may have build problems on Mondays)<br />
<br />
;Browse availability:<br />
:http://websvn.kde.org/branches/KDE/<br />
<br />
== Choose Location ==<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
===Source and Build Directories===<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
===Installation Directory===<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
===Qt ===<br />
; System Qt<br />
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root tho.<br />
<br />
; KDE-Qt <br />
:Previously known as qt-copy -- This is the minimum version of Qt any of your users is expected to have, Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.<br />
<br />
; Main Qt<br />
: get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt<br />
<br />
==Getting the Source==<br />
We are migrating from SVN to git. We have extensive infrastructure that is being converted, but please know that this is a much anticipated, complex, and popular change. http://www.omat.nl/2010/07/07/move-to-git-the-progress-so-far/<br />
<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Build it ==<br />
<br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; augmented with bash functions.<br />
:[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
:Specific examples:[[Build KDE4.6 on Kubuntu]]<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
=== Troubleshooting the build ===<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
=== Environment Variables ===<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
===Set up Development Tools===<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
===Contribution===<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53253Getting Started2010-08-07T04:20:44Z<p>AaronPeterson: /* Build it */</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
Our content is generally written with KDE4 and Linux in mind, Windows and BSD and KDE3 look at [[Getting_Started/Build|other Supported Platforms]] page.<br />
<br />
== [[Choose Version]] ==<br />
; Distribution synchronized<br />
: [[Distributions with KDE]] will show what versions are used by which distros if you have to keep with strictly what vendor offers <br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] Where new features grow (may have build problems on Mondays)<br />
<br />
;Browse availability:<br />
:http://websvn.kde.org/branches/KDE/<br />
<br />
== Choose Location ==<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
===Source and Build Directories===<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
===Installation Directory===<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
===Qt ===<br />
; System Qt<br />
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root tho.<br />
<br />
; KDE-Qt <br />
:Previously known as qt-copy -- This is the minimum version of Qt any of your users is expected to have, Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.<br />
<br />
; Main Qt<br />
: get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt<br />
<br />
==Getting the Source==<br />
We are migrating from SVN to git. We have extensive infrastructure that is being converted, but please know that this is a much anticipated, complex, and popular change. http://www.omat.nl/2010/07/07/move-to-git-the-progress-so-far/<br />
<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Build it ==<br />
<br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; augmented with bash functions.<br />
:[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
:Specific examples:[[Build KDE4.6 on Kubuntu]]<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
=== Troubleshooting the build ===<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
=== Environment Variables ===<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
===Set up Development Tools===<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
===Contribution===<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53250Getting Started2010-08-07T03:20:27Z<p>AaronPeterson: /* Build it */</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
Our content is generally written with KDE4 and Linux in mind, Windows and BSD and KDE3 look at [[Getting_Started/Build|other Supported Platforms]] page.<br />
<br />
== [[Choose Version]] ==<br />
; Distribution synchronized<br />
: [[Distributions with KDE]] will show what versions are used by which distros if you have to keep with strictly what vendor offers <br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] Where new features grow (may have build problems on Mondays)<br />
<br />
;Browse availability:<br />
:http://websvn.kde.org/branches/KDE/<br />
<br />
== Choose Location ==<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
===Source and Build Directories===<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
===Installation Directory===<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
===Qt ===<br />
; System Qt<br />
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root tho.<br />
<br />
; KDE-Qt <br />
:Previously known as qt-copy -- This is the minimum version of Qt any of your users is expected to have, Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.<br />
<br />
; Main Qt<br />
: get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt<br />
<br />
==Getting the Source==<br />
We are migrating from SVN to git. We have extensive infrastructure that is being converted, but please know that this is a much anticipated, complex, and popular change. http://www.omat.nl/2010/07/07/move-to-git-the-progress-so-far/<br />
<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
:[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
:Specific examples:[[Build KDE4.6 on Kubuntu]]<br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
=== Troubleshooting the build ===<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
=== Environment Variables ===<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
===Set up Development Tools===<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
===Contribution===<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=User:AaronPeterson/Welcome_to_KDE_TechBase/20100805/&diff=53249User:AaronPeterson/Welcome to KDE TechBase/20100805/2010-08-07T02:12:12Z<p>AaronPeterson: </p>
<hr />
<div><div class="plainlinks"><br />
<!-- WELCOME TO META BOX --><br />
<div class="toccolours" style="padding:1em;"><br />
<div style="float: right;"><br />
[[File:Discover.jpg]]<br />
</div><br />
<br />
<div style="font-size: 115%; margin-right: 80px;"><br />
'''Welcome to [[KDE Techbase Wiki]]''', the global community...developer site for the [[projects]], and [[coordination]] and [[documentation]] of the KDE community. For Governance issues, please visit http://community.kde.org For further information, see http://lists.kde.org [[IRC|IRC channels]]<br />
<div style="font-size: 75%">[{{fullurl:Main Page|action=purge}} Purge cache]</div><br />
</div><br />
<hr style="clear: both;" /><br />
<div style="font-weight: bold; text-align: center;"><br />
[[Wikimedia projects|Projects]] ([[Complete list of Wikimedia projects|complete list]]) • <br />
[[Mission]] • <br />
[[Vision]] • <br />
[[Meta:Babylon|Translation]] ([[Translation requests|requests]])<br />
<br style="clear: both;" /><br />
</div><br />
</div><br />
<!-- TechBase IN MANY LANGUAGES --><br />
<div style="padding:1em; background:#FFEFF0; border:1px solid #AAA; margin:1px 0;"><br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
</span><br />
TechBase is available in many languages!<br />
</h2><br />
{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}<br />
</div><br />
{| cellspacing="1"<br />
|- valign="top"<br />
| style="width:50%; border:1px solid #AAA; padding:1em; background:#E4FFDF;" |<br />
<!-- Our Content --><br />
<br />
=== [[Using]] ===<br />
; End User<br />
; Administrators<br />
; Kiosk<br />
; Case Studies<br />
<br />
=== [[Building]] ===<br />
; Distributions<br />
; For Developers <br />
; For Personal Use<br />
<br />
=== [[Developing]] ===<br />
; Core KDE Libraries<br />
; Existing Applications<br />
; New applications<br />
; System <br />
<br />
=== Contributing ===<br />
; Financially<br />
; By collaborating<br />
<br />
=== Community ===<br />
; Governance<br />
; ev<br />
<!-- NOTIFICATIONS --><br />
| valign="top" style="width:50%; border:1px solid #AAA; padding:1em; background:#E8F1FF;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Information_thread|action=watch}} watch]]<br />
[[{{fullurl:Template:Information_thread|action=edit}} edit]]<br />
[[{{fullurl:Goings-on/{{CURRENTYEAR}}}} '''read older news''']]<br />
</span><br />
Notifications<br />
</h2><br />
{{Information thread}}<br />
<br />
|- valign="top"<br />
| style="width:40%; border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Using this Website<br />
</h2><br />
This website is for technical documentation that supports kde users and developers<br />
<br />
* [[Style Guide]] -- conventions<br />
* [[meta:]] -- how to use mediawiki<br />
* [http://lists.kde.org|] and [[IRC]]<br />
* [[Meetup]]s (meetings between participants)<br />
* [[User groups|User groups]] <br />
<br />
| valign="top" style="border:1px solid #AAA; padding:1em;" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
Teams and Groups<br />
</h2><br />
What groups<br />
* [[GSoC|GSoC and SoK]]<br />
* [[Akademy]]<br />
* [[KDE e.V.]]<br />
* [[KDE Edu]]<br />
* [[KDE PIM]]<br />
* [[Promo|KDE Promo]]<br />
* [[KDE Documentation]]<br />
* [[KDE Women]]<br />
* [[Sysadmin|KDE Sysadmin]]<br />
* [[Real-Time_Communication_and_Collaboration|Real-Time Communication and Collaboration (Telepathy)]]<br />
* [[Digikam|digiKam]]<br />
* [[Plasma|Plasma Project Team Coordination]]<br />
* [[Plasma Netbook Reference Platform]]<br />
* [[Krita| Krita, Painting for Digital Artists: Developer notebook]]<br />
* [[KDE GB| KDE GB, KDE in Britain]]<br />
* [[KDE Localization|KDE Localization]]<br />
* [[KDE.org|KDE.org Websites]]<br />
* [[Phonon]]<br />
* [[Common Task Videos]]<br />
* [[Elegance]] <br />
|- valign="top"<br />
| colspan="2" style="border:1px solid #AAA; padding:1em; background:#F9F9F9" |<br />
<h2 style="font-size:130%; border:none; font-weight:bold;"><br />
<span style="font-weight:normal; float:right; font-size:70%;"><br />
[[{{fullurl:Template:Wikimedia Foundation|action=edit}} edit]]<br />
</span><br />
Wikimedia Foundation, Meta-Wiki, and its sister projects<br />
</h2><br />
{{Wikimedia Foundation}}{{Sisterprojects}}<br />
|}<br />
</div>__NOTOC__ __NOEDITSECTION__<br />
[[Category:Main page]]<br />
<br />
<br />
<br />
{|<br />
;[[Getting Started|Setting up a KDE development environment]]<br />
:Learn how to get, build and run KDE.<br />
<br />
<br />
;[[Development|Developing with KDE]]<br />
:[[Development/Tutorials|Tutorials]] <br />
[http://api.kde.org API Documentation] <br />
[[Development/FAQs|FAQs]] and more.<br />
:''Related'': [[Schedules|Release Schedules and Feature Plans]] <br />
[[Policies|Code Contribution and Development Guidelines]]<br />
<br />
;[[KDE System Administration]]<br />
:Information for system administrators managing KDE deployments. <br />
<br />
[[Image:Interact.png|noframe]]<br />
<br />
<br />
[[Contribute|Join the KDE Team and Contribute]]<br />
:Contribute patches, keep in touch with and join our community.<br />
:''Related:'' [[Policies|KDE Project Policies]] | [http://www.kde.org/support/support.php Donate Money]<br />
<br />
;[[ISV|ISV Information]]<br />
:Developer information for Independent Software Vendors.<br />
<br />
<br />
;[[Projects|KDE projects]]<br />
:Links to development wikis, task lists, etc. for various KDE Projects.</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Archive:Getting_Started/Build/Requirements&diff=53248Archive:Getting Started/Build/Requirements2010-08-07T01:49:27Z<p>AaronPeterson: /* Abstract */ link to how to get for each distro</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started/Build/KDE4/Prerequisites}}<br />
<br />
{{TutorialBrowser|<br />
<br />
series=Getting Started|<br />
<br />
name=Building KDE4 From Source/Prerequisites|<br />
<br />
pre=[[../|KDE SVN Quickstart Guide]]|<br />
<br />
next=[[../|KDE SVN Quickstart Guide]]|<br />
|<br />
}}<br />
<br />
== Abstract ==<br />
<br />
Some or all of these packages should be available for installation [[build requirements|from your distribution]]. For ease of installation and upgrading it is a good idea to install distribution packages if a recent enough version is provided. Software required to build KDE4 includes:<br />
<br />
* gcc and g++, preferably version 4.2 or higher<br />
* svn, the subversion revision control client<br />
* pkg-config<br />
* development libraries and headers for X11, OpenGL (mesa-common-dev and libglu1-mesa-dev), libjpeg, libpng, libungif, [http://download.librdf.org/source/ librdf], libxml2 and libxslt<br />
* the <tt>makeobj</tt> script, which is included in kdesdk. You can install it from kdesdk (kdesdk-scripts on Debian) or similar packages, or download at [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/makeobj WebSVN]<br />
* the [http://freedesktop.org/wiki/Software/shared-mime-info shared-mime-info package], is the freedesktop MIME standard now used in KDE<br />
* the [http://oscaf.sourceforge.net/ shared-desktop-ontologies package] is required to build and run all Nepomuk semantic desktop/desktop search modules.<br />
* [http://boost.org/ boost], used by kdebase; after build and/or install, in order to make cmake aware about its location (FindBoost), add the boost directory (which contains the include subdirectory) to CMAKE_INCLUDE_PATH or set a environment variable called BOOST_ROOT that points to the boost directory.<br />
* [http://docbook.org/schemas/4x.html DocBook XML DTDs (v4.2)] and [http://wiki.docbook.org/topic/DocBookXslStylesheets related XSL stylesheets], used by KDE help system; their packages are available in most distributions<br />
<br />
== D-Bus ==<br />
QtDBus and KDE are known to work with D-Bus versions 0.62, as well as 0.92 and upwards. Versions 0.60 and 0.61 may work too but are not tested. Versions 0.90 and 0.91 are known not to work. We recommend using post-1.0 release versions (at least 0.94), so consider upgrading if you haven't done so.<br />
<br />
Get [http://www.freedesktop.org/wiki/Software/dbus dbus] from your distribution, current stable release is version 1.2. Additionally you will also need dbus-glib. Be sure to also install the corresponding lib- and -devel packages.<br />
<br />
If you need to build it manually, latest release is [http://www.example.com link title http://dbus.freedesktop.org/releases/dbus/dbus-1.2.24.tar.gz]<br />
<br />
<br />
== CMake ==<br />
You need to have [http://cmake.org/ CMake] >=2.6.4 installed. <br />
You should be able to directly use the binary packages available on the [http://cmake.org/HTML/index.html CMake site]. There are also distribution specific packages available.<br />
<br />
== Qt ==<br />
Next we need to get Qt4. KDE 4.3 builds against Qt 4.5, however KDE trunk requires Qt 4.6. If you plan to build trunk on an ongoing basis, it is probably easier to track kde-qt, especially as KDE trunk may occasionally require a pre-release version of Qt.<br />
<br />
Most up-to-date distributions will have packages of sufficiently new Qt to build the latest KDE stable branch. Some distributions may even package kde-qt; if so, using it is a viable option. If the distribution you use does not provide packages of the necessary version of Qt, it will be necessary to use the recipe below. More information can be found in the sections of the tutorial specific to each distribution.<br />
<br />
Building qt4.4 with the -no-qt3support option will cause things to break.<br />
<br />
; README<br />
Please read the [http://qt.gitorious.org/+kde-developers/qt/kde-qt/blobs/master/README.kde-qt README.kde-qt] file for the necessary Qt configure options as well as currently known issues.<br />
<br />
=== The Recipe ===<br />
cs # Note: cs is not a typo. See [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|<font color=red>.bashrc</font>]] <br />
git clone git://gitorious.org/+kde-developers/qt/kde-qt.git qt-kde<br />
cd qt-kde<br />
./configure ''[copy/paste configure line from README.kde-qt replacing <installdir> with $QTDIR]''<br />
make -j2 # use 'make -j(X+1)' where X is your number of processors, to compile faster<br />
make install<br />
<br />
Note that you need to install Qt and Phonon from Qt and then later to install Phonon KDE from git at the same location. This will ensure you get sounds in Qt-based applications as well as in KDE ones.<br />
<br />
If ./configure produces errors about missing headers, run the following command before trying again: <code>QTDIR=`pwd` bin/syncqt</code><br />
<br />
'''Make sure <tt>which qmake</tt> delivers something out of $QTDIR, e.g.:'''<br />
/home/kde-devel/qt-kde/bin/qmake<br />
<br />
=== What's Happening ===<br />
We switch back to the <tt>kde-devel</tt> user's home directory (line 1) and download the source code, KDE branch, from gitorious using git (line 2). After changing into the resulting {{path|qt-kde}} directory (line 3), we then set up the build using the <tt>configure</tt> script (line 4). The various command line options used are explained in the {{path|qt-kde/README.kde-qt}} file. Finally, we build the minimal requirements for KDE (line 6) and install (line 9) Qt. If install dir is the same as the current dir (line 7), then we just free some space (line 8) instead. If you want all the example and demo applications, you can either build them individually or simply do a <tt>make</tt> from the {{path|qt-kde}} directory. <br />
<br />
Note that the installation does not require root as it installs Qt locally into {{path|$QTDIR}}. Installation is necessary if {{path|$QTDIR}} differs from the source directory.<br />
In the end, we make sure the cmake macro to find the Qt directory will work. It must be able to find qmake in $QTDIR.<br />
<br />
=== Troubleshooting ===<br />
If you get "error: X11/Xlib.h: No such file or directory", install the devel package of <tt>xorg</tt> (the actual name may vary between operating systems, for example it is <tt>xorg-dev</tt> on Ubuntu based systems such as Kubuntu). <br />
<br />
If you get an error in the configure step about missing defines, check the value of <tt>$QMAKESPEC</tt>. Some distributions set this to point directly to the system-installed Qt. If <tt>unset QMAKESPEC</tt> solves the problem, you probably want to add it to the <tt>~/.bashrc</tt> script.<br />
<br />
If you get an error ".pch/debug-shared/QtCore", this is because Qt-4.3 enables precompiled headers if your gcc supports it, but for some reason it doesn't work for you. If you use distcc, configure qt with -no-pch. If you use icecream, update to the latest icecream from svn trunk.<br />
<br />
Try running any Qt program, like {{program|assistant}}. '''Note:''' You may need to run <tt>xhost +local:kde-devel</tt> as your regular kde3 user to run this application. If it crashes in QSpanData::adjustSpanMethods, then your problem is the oxygen style. Try removing {{path|lib/kde4/plugins/styles/kstyle-oxygen.so}} and {{path|lib/kde4/plugins/styles/oxygen.so}} if they exist in the KDE install prefix.<br />
<br />
=== Generating local API documentation ===<br />
It's nice to have the Qt documentation locally for nice integration with [[Getting_Started/Set_up_KDE_4_for_development#KDevelop|KDevelop]], and doing this is really quite easy (also shown in {{path|README.kde-qt}}):<br />
cd $KDE_SRC/qt-kde<br />
make docs<br />
./config.status<br />
make install<br />
Note that it is necessary to do this only once, even if you rebuild Qt later.<br />
<br />
== HAL ==<br />
<br />
{{tip|You can use qdbusviewer to see if you have org.freedesktop.hal. If not, you might need a newer version of hal. If you have org.freedesktop.hal, you probably don't need to, and don't ''want'' to, roll your own HAL.}}<br />
<br />
If your system requires you to build a newer version of HAL, there's a decent chance you'll need to build other stuff as well, some of which may not be straight forward. This, however, should only be required for older distros.<br />
<br />
== kdesupport ==<br />
<br />
{{warning|Don't forget to read the [[Getting_Started/Build/KDE4#Setting_up_the_environment|Setting Up The Environment]] section first.}}<br />
<br />
There are several libraries that KDE applications rely on in the kdesupport module. This includes Strigi and Soprano for file metadata and search, QImageBlitz for image manipulation needed in kdebase, eigen for visual effects in applications such as Kalzium, taglib for music players and qca for some cryptographic needs. <br />
<br />
Strigi itself has a few dependencies as well: you will need the libraries and headers for libz, libbz2, openssl (libcrypto or libssl), libclucene (>=0.9.16a but watch out: version 0.9.17 does '''not''' work), and either libxml2 or libexpat.<br />
<br />
[[Getting_Started/Build/KDE4/Prerequisites#DBusMenu|'''Phonon''']] is not in kdesupport anymore but in a git repository.<br />
<br />
There is a new dependency: [[Getting_Started/Build/KDE4/Prerequisites#DBusMenu|'''DBusMenu''']].<br />
<br />
Please remember that if you use openSUSE, you can install the needed packages from the KDE:KDE4 buildservice repository and do not have to bother with fiddling the details below. Skip to the kdelibs section. <br />
<br />
=== The Recipe ===<br />
<!--'cs' and 'cb' are NOT typos!--><br />
cs # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]<br />
svn checkout svn://anonsvn.kde.org/home/kde/trunk/kdesupport/<br />
cd kdesupport<br />
cmakekde<br />
<br />
=== What's Happening ===<br />
We change to the base source directory (line 1). We download the sources in kdesupport using subversion (line 2), go into the new {{path|~/kde/src/kdesupport}} directory (line 3), and commence the build (line 4). This will leave us in the kdesupport build directory after the build is completed.<br />
<br />
=== Troubleshooting ===<br />
If you get <br />
cmakekde: command not found<br />
then you have to go manually into the kdesupport directory in ~ and execute the command cmakekde. if this still doesn't work, then something is wrong with your bashrc.<br />
<br />
If you get <br />
CMake Error: This project requires some variables to be set,<br />
and cmake can not find them.<br />
Please set the following variables:<br />
LIBXML2_INCLUDE_DIR (ADVANCED)<br />
you should install the development package for libxml2.<br />
<br />
If you get <br />
CMake Error: Could NOT find REDLAND<br />
then you need librdf from the Redland.<br />
If your distribution does not provide the librdf package, you can download the source there: [http://download.librdf.org/source/ http://download.librdf.org/source/] and build it.<br />
(Gentoo users: The ebuild for librdf is named dev-libs/redland)<br />
<br />
If you get<br />
Fetching external item into 'kdesupport/admin'<br />
Error validating server certificate for 'https://...'<br />
see [[Getting_Started/Sources/Using_Subversion_with_KDE|Using Subversion with KDE]]<br />
<br />
If you get<br />
FILE cannot create directory: /usr/lib[64]/qt4/plugins/crypto. Maybe need administrative privileges.<br />
<br />
make: *** [install] Error 255<br />
take a second look in the .bashrc file described above, are paths correct? ($QTDIR and $PATH are used to get the QT installation path)<br />
Alternatively, you may see this error if you decided to use a distribution installed version of qt4 and skipped the Qt install above. Either install qt-kde as describe above, or "sudo make install". If you use "sudo make install", make sure that you change the ownership back to your user for some of the ~/kde subdirectories that were effected by using sudo (ie. "<tt>sudo chown -R kde-devel:kde-devel ~/kde</tt>").<br />
<br />
If you get a message related to <br />
target libQtTest.so not found<br />
you may need to recompile qt-kde. This time you should take out<br />
-nomake demos -nomake examples<br />
from the configure command, so that Qt generates library QtTest.<br />
<br />
<br />
If you get<br />
CMake Error: Qt qmake not found!<br />
Then:<br />
1) uncomment Qt section in .bashrc script (QTDIR, QT_PLUGINS_DIR, <br />
PKG_CONFIG_PATH variable settings).<br />
2) source ~/.bashrc<br />
3) cd && cd qt-kde<br />
4) make confclean<br />
5) repeat steps for installing Qt (from ./configure line).<br />
6) retry building kdesupport<br />
<br />
If you get<br />
"CMake Error: Could NOT find BZip2"<br />
then<br />
sudo apt-get install libbz2-dev<br />
or<br />
urpmi libbzip2_1-devel<br />
<br />
If you get <br />
message that MySql support cannot be enabled<br />
then<br />
you need to install corresponding devel package. (libmysqlclient-devel for SuSe 11.1)<br />
<br />
== Phonon ==<br />
Phonon is not in kdesupport anymore but in a git repository. You need to build it as Phonon from Qt is not enough for KDE sound to work.<br />
<br />
=== The Recipe ===<br />
<!--'cs' and 'cb' are NOT typos!--><br />
cs # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]<br />
git clone git://gitorious.org/phonon/phonon.git phonon<br />
cd phonon<br />
mkdir build<br />
cd build<br />
cmake .. -DCMAKE_INSTALL_PREFIX=$QTDIR -DCMAKE_BUILD_TYPE=debugfull \-DKDE4_BUILD_TESTS=TRUE<br />
make <br />
make install<br />
<br />
'''Note''' that you need to install this Phonon in the same location than Phonon from Qt i.e. in $QTDIR.<br />
<br />
=== Troubleshooting ===<br />
<br />
If you get an error like<br />
<br />
designer: symbol lookup error: /path/to/kde/lib/kde4/plugins/phonon_backend/phonon_xine.so: undefined symbol: _ZN6Phonon12PulseSupport11getInstanceEv<br />
<br />
while running Qt Designer you need to:<br />
<br />
rm $QTDIR/lib/libphonon.so.4<br />
<br />
== DBusMenu ==<br />
<br />
Since the 26th April 2010, DBusMenu is a new dependency for kdelibs. You can either get it from<br />
http://people.canonical.com/~agateau/dbusmenu/index.html<br />
as a tarball (latest is libdbusmenu-qt-0.3.3.tar.bz2)<br />
or from its it repository<br />
<br />
=== The Recipe ===<br />
<!--'cs' and 'cb' are NOT typos!--><br />
cs # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]<br />
git clone git://gitorious.org/dbusmenu/dbusmenu-qt.git dbusmenu<br />
cd dbusmenu<br />
mkdir build<br />
cd build<br />
cmake .. -DCMAKE_INSTALL_PREFIX=$KDEDIR -DCMAKE_BUILD_TYPE=debugfull \-DKDE4_BUILD_TESTS=TRUE<br />
make <br />
make install<br />
=== Troubleshooting ===<br />
You need json to build the tests.<br />
<br />
If your version is not correct, you will lose the context menu for the systray icons.<br />
<br />
== Next Step ==<br />
Once all requirements have been installed it is time to install [[../#kdelibs|kdelibs]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53241Getting Started2010-08-06T04:08:50Z<p>AaronPeterson: /* Getting the Source */ linked to toma's blog</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
Our content is generally written with KDE4 and Linux in mind, Windows and BSD and KDE3 look at [[Getting_Started/Build|other Supported Platforms]] page.<br />
<br />
== [[Choose Version]] ==<br />
; Distribution synchronized<br />
: [[Distributions with KDE]] will show what versions are used by which distros if you have to keep with strictly what vendor offers <br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] Where new features grow (may have build problems on Mondays)<br />
<br />
;Browse availability:<br />
:http://websvn.kde.org/branches/KDE/<br />
<br />
== Choose Location ==<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
===Source and Build Directories===<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
===Installation Directory===<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
===Qt ===<br />
; System Qt<br />
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root tho.<br />
<br />
; KDE-Qt <br />
:Previously known as qt-copy -- This is the minimum version of Qt any of your users is expected to have, Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.<br />
<br />
; Main Qt<br />
: get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt<br />
<br />
==Getting the Source==<br />
We are migrating from SVN to git. We have extensive infrastructure that is being converted, but please know that this is a much anticipated, complex, and popular change. http://www.omat.nl/2010/07/07/move-to-git-the-progress-so-far/<br />
<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
=== Troubleshooting the build ===<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
=== Environment Variables ===<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
===Set up Development Tools===<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
===Contribution===<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53240Getting Started2010-08-06T04:04:42Z<p>AaronPeterson: /* Troubleshooting the build */ should be a part of building</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
Our content is generally written with KDE4 and Linux in mind, Windows and BSD and KDE3 look at [[Getting_Started/Build|other Supported Platforms]] page.<br />
<br />
== [[Choose Version]] ==<br />
; Distribution synchronized<br />
: [[Distributions with KDE]] will show what versions are used by which distros if you have to keep with strictly what vendor offers <br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] Where new features grow (may have build problems on Mondays)<br />
<br />
;Browse availability:<br />
:http://websvn.kde.org/branches/KDE/<br />
<br />
== Choose Location ==<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
===Source and Build Directories===<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
===Installation Directory===<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
===Qt ===<br />
; System Qt<br />
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root tho.<br />
<br />
; KDE-Qt <br />
:Previously known as qt-copy -- This is the minimum version of Qt any of your users is expected to have, Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.<br />
<br />
; Main Qt<br />
: get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
=== Troubleshooting the build ===<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
=== Environment Variables ===<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
===Set up Development Tools===<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
===Contribution===<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53239Getting Started2010-08-06T04:03:59Z<p>AaronPeterson: enviornment variables are important, and development tools and contribution are covered elsewhere</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
Our content is generally written with KDE4 and Linux in mind, Windows and BSD and KDE3 look at [[Getting_Started/Build|other Supported Platforms]] page.<br />
<br />
== [[Choose Version]] ==<br />
; Distribution synchronized<br />
: [[Distributions with KDE]] will show what versions are used by which distros if you have to keep with strictly what vendor offers <br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] Where new features grow (may have build problems on Mondays)<br />
<br />
;Browse availability:<br />
:http://websvn.kde.org/branches/KDE/<br />
<br />
== Choose Location ==<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
===Source and Build Directories===<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
===Installation Directory===<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
===Qt ===<br />
; System Qt<br />
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root tho.<br />
<br />
; KDE-Qt <br />
:Previously known as qt-copy -- This is the minimum version of Qt any of your users is expected to have, Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.<br />
<br />
; Main Qt<br />
: get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
=== Environment Variables ===<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
===Set up Development Tools===<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
===Contribution===<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53238Getting Started2010-08-06T04:02:21Z<p>AaronPeterson: /* Location */ knock it to a more significant level</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
Our content is generally written with KDE4 and Linux in mind, Windows and BSD and KDE3 look at [[Getting_Started/Build|other Supported Platforms]] page.<br />
<br />
== [[Choose Version]] ==<br />
; Distribution synchronized<br />
: [[Distributions with KDE]] will show what versions are used by which distros if you have to keep with strictly what vendor offers <br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] Where new features grow (may have build problems on Mondays)<br />
<br />
;Browse availability:<br />
:http://websvn.kde.org/branches/KDE/<br />
<br />
== Choose Location ==<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
===Source and Build Directories===<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
===Installation Directory===<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
===Qt ===<br />
; System Qt<br />
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root tho.<br />
<br />
; KDE-Qt <br />
:Previously known as qt-copy -- This is the minimum version of Qt any of your users is expected to have, Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.<br />
<br />
; Main Qt<br />
: get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53237Getting Started2010-08-06T04:01:24Z<p>AaronPeterson: /* Method */ generally covered elsewhere</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
Our content is generally written with KDE4 and Linux in mind, Windows and BSD and KDE3 look at [[Getting_Started/Build|other Supported Platforms]] page.<br />
<br />
== [[Choose Version]] ==<br />
; Distribution synchronized<br />
: [[Distributions with KDE]] will show what versions are used by which distros if you have to keep with strictly what vendor offers <br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] Where new features grow (may have build problems on Mondays)<br />
<br />
;Browse availability:<br />
:http://websvn.kde.org/branches/KDE/<br />
<br />
=== Location ===<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
====Source and Build Directories====<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
====Installation Directory====<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
===Qt ===<br />
; System Qt<br />
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root tho.<br />
<br />
; KDE-Qt <br />
:Previously known as qt-copy -- This is the minimum version of Qt any of your users is expected to have, Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.<br />
<br />
; Main Qt<br />
: get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53236Getting Started2010-08-06T03:59:43Z<p>AaronPeterson: /* Choose Version */</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
Our content is generally written with KDE4 and Linux in mind, Windows and BSD and KDE3 look at [[Getting_Started/Build|other Supported Platforms]] page.<br />
<br />
== [[Choose Version]] ==<br />
; Distribution synchronized<br />
: [[Distributions with KDE]] will show what versions are used by which distros if you have to keep with strictly what vendor offers <br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] Where new features grow (may have build problems on Mondays)<br />
<br />
;Browse availability:<br />
:http://websvn.kde.org/branches/KDE/<br />
<br />
=== Location ===<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
====Source and Build Directories====<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
====Installation Directory====<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
=== Method ===<br />
<br />
Read up on steps below. [[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual -- to learn how things work<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: most common method, set environment variables and use scripts.<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
===Qt ===<br />
; System Qt<br />
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root tho.<br />
<br />
; KDE-Qt <br />
:Previously known as qt-copy -- This is the minimum version of Qt any of your users is expected to have, Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.<br />
<br />
; Main Qt<br />
: get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Talk:Installing_third_party_softwares_in_terminal/Build/kdesrc-build&diff=53235Talk:Installing third party softwares in terminal/Build/kdesrc-build2010-08-06T03:51:19Z<p>AaronPeterson: Just pasting in something taken from Getting Started that made it work for me, not listed elsewhere</p>
<hr />
<div>== Just pasting in something taken from Getting Started that made it work for me, not listed elsewhere ==<br />
<br />
* This will compile qt for you, or you can configure it to use system QT<br />
* When you choose a branch<br />
** edit your ''.kdesrc-buildrc'' <br />
*** set your branch<br />
*** you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: ''module-base-path tags/kdesupport-for-4.5''</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53234Getting Started2010-08-06T03:49:53Z<p>AaronPeterson: getting it comes before building it..., chop off some kdesrc-build stuff that I added earlier</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
=== [[Choose Version]] ===<br />
; Synchronized with distribution<br />
: [[Distributions with KDE]] may provide KDE Dev and SDK for 3rd party development<br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] (may have build problems on Mondays)<br />
<br />
[[Getting_Started/Build|other Supported Platforms]] ''Including information for building on non-linux systems Incl KDE3'' [[Older Versions]]<br />
<br />
To See which versions/branches of KDE are available go to:<br />
::http://websvn.kde.org/branches/KDE/<br />
<br />
=== Location ===<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
====Source and Build Directories====<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
====Installation Directory====<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
=== Method ===<br />
<br />
Read up on steps below. [[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual -- to learn how things work<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: most common method, set environment variables and use scripts.<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
===Qt ===<br />
; System Qt<br />
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root tho.<br />
<br />
; KDE-Qt <br />
:Previously known as qt-copy -- This is the minimum version of Qt any of your users is expected to have, Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.<br />
<br />
; Main Qt<br />
: get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53233Getting Started2010-08-06T03:46:38Z<p>AaronPeterson: /* Gather Prerequisites */ Qt deserves it's own nodd here</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
=== [[Choose Version]] ===<br />
; Synchronized with distribution<br />
: [[Distributions with KDE]] may provide KDE Dev and SDK for 3rd party development<br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] (may have build problems on Mondays)<br />
<br />
[[Getting_Started/Build|other Supported Platforms]] ''Including information for building on non-linux systems Incl KDE3'' [[Older Versions]]<br />
<br />
To See which versions/branches of KDE are available go to:<br />
::http://websvn.kde.org/branches/KDE/<br />
<br />
=== Location ===<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
====Source and Build Directories====<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
====Installation Directory====<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
=== Method ===<br />
<br />
Read up on steps below. [[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual -- to learn how things work<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: most common method, set environment variables and use scripts.<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
===Qt ===<br />
; System Qt<br />
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root tho.<br />
<br />
; KDE-Qt <br />
:Previously known as qt-copy -- This is the minimum version of Qt any of your users is expected to have, Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.<br />
<br />
; Main Qt<br />
: get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
* This will compile qt for you, or you can configure it to use system QT<br />
* When you choose a branch<br />
** edit your ''.kdesrc-buildrc'' <br />
*** set your branch<br />
*** you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: ''module-base-path tags/kdesupport-for-4.5''<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53231Getting Started2010-08-06T03:36:00Z<p>AaronPeterson: /* Installation Directory */</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
=== [[Choose Version]] ===<br />
; Synchronized with distribution<br />
: [[Distributions with KDE]] may provide KDE Dev and SDK for 3rd party development<br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] (may have build problems on Mondays)<br />
<br />
[[Getting_Started/Build|other Supported Platforms]] ''Including information for building on non-linux systems Incl KDE3'' [[Older Versions]]<br />
<br />
To See which versions/branches of KDE are available go to:<br />
::http://websvn.kde.org/branches/KDE/<br />
<br />
=== Location ===<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
====Source and Build Directories====<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
====Installation Directory====<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
; [[Contributor]]<br />
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]<br />
<br />
=== Method ===<br />
<br />
Read up on steps below. [[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual -- to learn how things work<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: most common method, set environment variables and use scripts.<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
* This will compile qt for you, or you can configure it to use system QT<br />
* When you choose a branch<br />
** edit your ''.kdesrc-buildrc'' <br />
*** set your branch<br />
*** you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: ''module-base-path tags/kdesupport-for-4.5''<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53230Getting Started2010-08-06T03:32:57Z<p>AaronPeterson: /* Choose Version */</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
=== [[Choose Version]] ===<br />
; Synchronized with distribution<br />
: [[Distributions with KDE]] may provide KDE Dev and SDK for 3rd party development<br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]] (may have build problems on Mondays)<br />
<br />
[[Getting_Started/Build|other Supported Platforms]] ''Including information for building on non-linux systems Incl KDE3'' [[Older Versions]]<br />
<br />
To See which versions/branches of KDE are available go to:<br />
::http://websvn.kde.org/branches/KDE/<br />
<br />
=== Location ===<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
====Source and Build Directories====<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
====Installation Directory====<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
=== Method ===<br />
<br />
Read up on steps below. [[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual -- to learn how things work<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: most common method, set environment variables and use scripts.<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
* This will compile qt for you, or you can configure it to use system QT<br />
* When you choose a branch<br />
** edit your ''.kdesrc-buildrc'' <br />
*** set your branch<br />
*** you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: ''module-base-path tags/kdesupport-for-4.5''<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Talk:Installing_third_party_softwares_in_terminal/Increased_Productivity_in_KDE4_with_Scripts&diff=53227Talk:Installing third party softwares in terminal/Increased Productivity in KDE4 with Scripts2010-08-06T03:25:44Z<p>AaronPeterson: moved Talk:Getting Started/Increased Productivity in KDE4 with Scripts to Talk:Build/KDE4:&#32;Scripts are not the focus, This is the main way people install, note that a redirect will be made, this can be undone</p>
<hr />
<div>#REDIRECT [[Talk:Build/KDE4]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Talk:Build/KDE4&diff=53226Talk:Build/KDE42010-08-06T03:25:44Z<p>AaronPeterson: moved Talk:Getting Started/Increased Productivity in KDE4 with Scripts to Talk:Build/KDE4:&#32;Scripts are not the focus, This is the main way people install, note that a redirect will be made, this can be undone</p>
<hr />
<div>isn't the qt-copy installation going to end with gmake gmake install instead of make and make install ?<br />
i$baran<br />
<br />
<br />
----<br />
<br />
<br />
In the environment variables, shouldn't KDESYCOCA be set to something like "$KDEHOME/ksycoca-database" (right now, KDESYCOCA is not set)?<br />
<br />
If the purpose is to share the same account to develop trunk (installed in a directory of the user account) with the one used for daily tasks (the stable version provided by the distro installed system wide), you are likely going to execute at the same time applications of each type.<br />
<br />
I don't know if I made something wrong, but if I don't set KDESYCOCA, when I execute a trunk application it overwrites the configuration cache (for that user) of the stable applications. For example, if I run trunk kdevelop, stable Dolphin service menus disappear.<br />
<br />
Instead, if I set KDESYCOCA in the environment variables of .my-setup, everything is fine. Trunk applications use the specified file for ksycoca database, and thus the development environment is isolated from the daily use environment.<br />
<br />
However, I didn't edit the article because I'm not sure if I made something wrong and that's why I needed to set up KDESYCOCA, because it seems strange to me that nobody had had this problem before...</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53223Getting Started2010-08-06T03:20:45Z<p>AaronPeterson: /* Determine Your Needs */ still awkward, but less unneeded verbage</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), <br />
<br />
=== [[Choose Version]] ===<br />
; Synchronized with distribution<br />
: [[Distributions with KDE]] may provide KDE Dev and SDK for 3rd party development<br />
; Latest Features for production<br />
: [[branch]] (stable / beta)<br />
; [[Core Development]]<br />
: [[trunk]]<br />
<br />
[[Getting_Started/Build|other Supported Platforms]] ''Including information for building on non-linux systems Incl KDE3'' [[Older Versions]]<br />
<br />
To See which versions/branches of KDE are available go to:<br />
::http://websvn.kde.org/branches/KDE/<br />
<br />
=== Location ===<br />
Choose where you want to put the KDE installation, and keep source and build directories.<br />
( [[QCA plugin]] may have to be installed as root if using system Qt))<br />
====Source and Build Directories====<br />
: suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE)<br />
: possibly /usr/src/ if [[building as root]]<br />
<br />
====Installation Directory====<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
=== Method ===<br />
<br />
Read up on steps below. [[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual -- to learn how things work<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: most common method, set environment variables and use scripts.<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
* This will compile qt for you, or you can configure it to use system QT<br />
* When you choose a branch<br />
** edit your ''.kdesrc-buildrc'' <br />
*** set your branch<br />
*** you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: ''module-base-path tags/kdesupport-for-4.5''<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53222Getting Started2010-08-06T03:00:05Z<p>AaronPeterson: /* Location */</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
=== [[Choose Version]] ===<br />
For production use, we recommend using a stable "branch" version of KDE. If you just want to use KDE, take a look at http://userbase.kde.org/. If you are developing applications, your distribution's dev packages and the kde-sdk may work. If your distribution does not have KDE you'll need to build it yourself. <br />
<br />
If you want to hack at KDE's core modules, you'll need to build it, and TRUNK is the main branch where new features (and prerequisites) are added, however it can be difficult to keep up with.<br />
<br />
[[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems Incl KDE3''<br />
<br />
To See which versions/branches of KDE are available go to:<br />
::http://websvn.kde.org/branches/KDE/<br />
<br />
=== Location ===<br />
There may be advantages to putting your KDE in different locations.( Note that if using system Qt for a user based KDE install, the [[QCA plugin]] may have to be installed as root))<br />
<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
: To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
=== Method ===<br />
<br />
Regardless of method chosen, reading up on the manual steps below will be very helpful.<br />
[[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: Manual, but with a few scripts to keep everything easy<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
* This will compile qt for you, or you can configure it to use system QT<br />
* When you choose a branch<br />
** edit your ''.kdesrc-buildrc'' <br />
*** set your branch<br />
*** you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: ''module-base-path tags/kdesupport-for-4.5''<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53221Getting Started2010-08-06T02:59:33Z<p>AaronPeterson: /* Location */ Switched to user organized, there are dead links, haven't figured out best names yet</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
=== [[Choose Version]] ===<br />
For production use, we recommend using a stable "branch" version of KDE. If you just want to use KDE, take a look at http://userbase.kde.org/. If you are developing applications, your distribution's dev packages and the kde-sdk may work. If your distribution does not have KDE you'll need to build it yourself. <br />
<br />
If you want to hack at KDE's core modules, you'll need to build it, and TRUNK is the main branch where new features (and prerequisites) are added, however it can be difficult to keep up with.<br />
<br />
[[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems Incl KDE3''<br />
<br />
To See which versions/branches of KDE are available go to:<br />
::http://websvn.kde.org/branches/KDE/<br />
<br />
=== Location ===<br />
There may be advantages to putting your KDE in different locations.( Note that if using system Qt for a user based KDE install, the [[QCA plugin]] may have to be installed as root))<br />
<br />
;[[Casual Curiosity]]<br />
: [[development user home]] if you do not want to mess up your production KDE<br />
: [[your home directory]] if you are willing to use environment variables to keep versions seporate( using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine<br />
: [[As root]] Not advised unless you have a dedicated machine<br />
<br />
<br />
; [[Application Developer]]<br />
: [[development user home]] same as for curious user<br />
: [[as root]] will be more useful to simulate environment of customers<br />
: [[your home directory]] may simplify your development<br />
<br />
; [[Distribution Manager]]<br />
; To test KDM, you may want to install [[as root]] and or use a [[virtual machine]] so you do not damage a production system.<br />
<br />
=== Method ===<br />
<br />
Regardless of method chosen, reading up on the manual steps below will be very helpful.<br />
[[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: Manual, but with a few scripts to keep everything easy<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
* This will compile qt for you, or you can configure it to use system QT<br />
* When you choose a branch<br />
** edit your ''.kdesrc-buildrc'' <br />
*** set your branch<br />
*** you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: ''module-base-path tags/kdesupport-for-4.5''<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Template:Getting_Started&diff=53219Template:Getting Started2010-08-06T02:46:23Z<p>AaronPeterson: Created page with 'Category:Getting Started <!--Use this template to denote that this page is a starting point for your track.-->'</p>
<hr />
<div>[[Category:Getting Started]]<br />
<!--Use this template to denote that this page is a starting point for your track.--></div>AaronPetersonhttps://techbase.kde.org/index.php?title=Template:Build_KDE&diff=53218Template:Build KDE2010-08-06T02:44:58Z<p>AaronPeterson: just including categories now</p>
<hr />
<div>[[Category:Build KDE]]<br />
[[Category:KDE4]]<br />
[[Category:Cmake]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started/Build/KDE4&diff=53217Getting Started/Build/KDE42010-08-06T02:43:39Z<p>AaronPeterson: use templates to include categories, so other related articles can inherit</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started/Build/KDE4}}<br />
<br />
{{TutorialBrowser|<br />
<br />
<br />
<br />
series=Getting Started|<br />
<br />
name=Building KDE4 (Development version, TRUNK) From Source|<br />
<br />
pre=[[../../Sources/Anonymous_SVN|Anonymous SVN Quickstart Guide]]|<br />
<br />
next=[[../../Set_up_KDE_4_for_development|Set up KDE 4 for development]]|<br />
<br />
reading=[[../kdesrc-build|kdesrc-build: The KDE From Source Build Tool]]<br>[[Contribute/Send Patches|Sending Patches]]<br>[[../../Increased_Productivity_in_KDE4_with_Scripts|Increased Productivity in KDE4 with Scripts]]<br>[[Development/Tutorials/CMake |Introduction to CMake]]<br>[[../KDE4/FreeBSD|FreeBSD notes]]<br>[[../KDE4/Mac OS X|Instructions for Mac OS X]]<br>[[../KDE4/Windows|Instructions for MS Windows]]|<br />
}}<br />
{| class="collapsible collapsed" style="border: 1px #aaa solid; background: #efefef;"<br />
! style="font-size: 1.25em; "| Table of contents<br />
|-<br />
| __TOC__<br />
|}<br />
{{warning|The commands below are used to build the latest UNSTABLE version of KDE from TRUNK. <br />
<br />
This should not be used in a production environment -- not recommended for daily use.<br />
<br />
To build a stable KDE-4 version, go to:<br />
<br />
::[[Getting_Started/Build/KDE4.x|upgrading to KDE-4.x from KDE-3.x]]<br />
<br />
Or<br />
<br />
::[[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
<br />
which is currently under construction.<br />
}}<br />
<br />
== Abstract ==<br />
<br />
This tutorial shows a labor intensive way to get KDE from trunk running on Linux/BSD systems. <br />
<br />
<br />
{{Note|<br />
kdesrc-build http://kdesrc-build.kde.org/ is an easy alternative. (Previously called kdesvn-build)<br />
}}<br />
<br />
There are also tutorials for [[Getting_Started/Build/KDE4/FreeBSD|FreeBSD]], [[/Windows|Windows]], [[/Mac OS X|Mac OS X]] and [http://solaris.kde.org/ Solaris]. This tutorial creates a special user, kde-devel, that will run KDE trunk. On the one hand, this allows other users to continue with another KDE version. On the other hand, testing special system-wide code like the KDE display manager is not possible. There is a tutorial to<br />
[[Getting_Started/Build/KDE4/onVmWare|set up KDE 4 trunk on a virtual machine]].<br />
<br />
Throughout the tutorial the bash shell is used.<br />
<br />
{{warning|Expect a higher risk of build failure '''on Mondays''' when most kdelibs changes are committed. [http://developer.kde.org/~dirk/dashboard/ Dashboard] reports unexpected breakages. You are encouraged to fix failing modules.}}<br />
<br />
== Create a user account for KDE4 development ==<br />
<br />
It is important to keep the development version from interfering with the rest of your computer, The method covered here is creating a dedicated kde-devel user.<br />
<br />
We will need to:<br />
#Add the user<br />
#Set the shell to bash<br />
#and may have to use sudoedit if we want to be able to sudo<br />
#Create a .bashrc file with environment variables for the build system<br />
<br />
A graphical tool is avalable from most distributions, if you have KDE you can get to this tool via: K->Computer->System Settings->User Management<br />
<br />
<br />
{{Note|<br />
Less Safe Alternative:<br />
One can do everything under your normal user account<br />
<br />
See [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|Increased Productivity in KDE4 with Scripts]]<br />
for more details. <br />
<br />
The environment variables determinate what version you use. Proceed same as here except put the environment variables in a file. In your <tt>.bashrc</tt> file add the line <tt>source .kde_devel_env</tt>. renaming the .kde_devel_env file would make them not be loaded, so you wouldn't use the devel version.<br />
}}<br />
<br />
===Commandline useradd===<br />
Some systems are configured to use {{path|/bin/sh}}. Many users prefer Bash{{path|/bin/bash}} <br />
<br />
{{Note|<br />
On Ark Linux and Fedora, you can skip the <tt>-s /bin/bash</tt> switch - {{path|/bin/sh}} is {{path|bash}}.<br />
}}<br />
<code bash><br />
useradd -m kde-devel -s /bin/bash<br />
passwd kde-devel<br />
</code><br />
<br />
<br />
==== commandline permissions and groups ====<br />
Edit your /etc/groups file to add the kde-devel user to all the groups that you need (probably the groups that your usual username is already assigned to).<br />
<br />
You may need to add user to sudoers file. (beyond scope of this tutorial)<br />
<br />
=== Setting up the environment ===<br />
<br />
Copy the {{path|~/.bashrc}} from your normal user account to the new kde-devel account. <br />
<br />
Next, copy and paste the contents of the [[Getting Started/Increased Productivity in KDE4 with Scripts/.bashrc|example .bashrc]] into {{path|~kde-devel/.bashrc}}. Be sure to comment out the line <tt>alias make=makeobj</tt> if you do not have the <tt>[[Getting Started/Build/KDE4/Prerequisites#Abstract|makeobj]]</tt> command available. (What is this, how do we know???)<br />
<br />
<br />
Alternatively, you can download the kde-sdk a.k.a kdesdk package (or perform a subversion checkout) and include the kde-sdk/scripts/ directory in your path. (What is this???)<br />
<br />
You will probably also want to modify the path to make sure it doesn't include your kde3 paths.<br />
<br />
Also if you want to use KDevelop to develop KDE 4 applications you may pass the ''-GKDevelop3'' flag to the ''cmake'' command (to make CMake generate KDevelop project files, it will help to avoid rebuilding in the future, see [[Getting_Started/Set_up_KDE_4_for_development#Setting_up_the_environment|this]]). <br />
To make it run, you have to open a new bash or to execute <br />
<code bash><br />
source ~/.bashrc<br />
</code><br />
<br />
This will provide access to commands such as <tt>cmakekde</tt> that are used in this tutorial as well as ensure that the proper paths are in place for Qt, KDE and CMake binaries.<br />
<br />
For more information, please read the [[Getting Started/Increased Productivity in KDE4 with Scripts]] tutorial.<br />
<br />
=== Using the kde-devel User ===<br />
To get a text-only command prompt, say from konsole<br />
su - kde-devel<br />
'(need hyphen otherwise your environment will be the same as your regular user)<br />
<br />
To Log in Text-only from a virtual terminal:<br />
CTRL-F1 ( CTRL-F7 is normally graphical )<br />
<br />
To use a shell that can pop up applications when your normal user is logged in:<br />
<code bash><br />
ssh -X kde-devel@localhost<br />
</code><br />
<br />
{{Note|<br />
If the ssh command fails, check out the [[Getting_Started/Set_up_KDE_4_for_development#Launching_KDE_4_apps|Launching KDE 4 apps]] section of the [[Getting_Started/Set_up_KDE_4_for_development|KDE4 development guide]].<br />
}}<br />
<br />
== Required packages from your distribution ==<br />
The requirements to build kde4 from source vary from distribution to distribution. Instructions for your distribution are provided below:<br />
See [[build requirements]] for more complete list.<br />
<br />
[[Getting_Started/Build/KDE4/Ark Linux|Ark Linux]],<br />
[[Getting_Started/Build/KDE4/Arch Linux|Arch Linux]], [[Getting_Started/Build/KDE4/Fedora|Fedora]],<br />
[[Getting_Started/Build/KDE4/Kubuntu and Debian|Kubuntu and Debian]]( or check out [[Getting_Started/Using_Project_Neon_to_contribute_to_KDE|Project Neon]])<br />
, [[Getting_Started/Build/KDE4/openSUSE|openSUSE]]( [http://en.opensuse.org/openSUSE:KDE_developers_guide specific guide for openSUSE]. However be careful because it updates a huge number of your stable packages.),<br />
[[Getting_Started/Build/KDE4/Gentoo|Gentoo]],<br />
[[Getting_Started/Build/KDE4/LFS|Linux from Scratch]] or to build from source.<br />
[[Getting_Started/Build/KDE4/Mandriva|Mandriva]]<br />
[[Getting_Started/Build/KDE4/Generic|any other distro]]<br />
<br />
<br />
=== Optional Documentation Dependencies ===<br />
For trunk you also now need docbook-dtd42-xml for the docs. Depending on your distribution please get the docbook related packages and the 4.2 DTD.<br />
<br />
Your next compilation step depends on the packages supplied by your distro.<br />
<br />
== Compiling kde-qt, etc. ==<br />
If you do not want to use the packages provided by your distro you can compile things like Qt yourself. Instructions for building all dependencies including CMake, Qt4 (kde-qt) and kdesupport are available in [[Getting_Started/Build/KDE4/Prerequisites|the build prerequisites page]]. Note that automoc, strigi, soprano, and a few other things are part of kdesupport, so if you have errors about these missing, you'll need to get kdesupport.<br />
<br />
=== Useful subversion tweaks ===<br />
<br />
{{Warning|Do not use this method when you don't know what you are doing or just want to test some trunk feature, seriously! <br />
You can create a very costly load when you accidentially checkout all of trunk or for example all of "trunk/KDE" just to build single modules. This would generate immense useless load on the svn server.}}<br />
<br />
If you check out large parts of svn trunk regularly or if you want to create patches which touch several modules at once, you should try to checkout an empty tree of trunk first and then update only the relevant modules, for example:<br />
<br />
==== Example ====<br />
cd<br />
cs # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]<br />
svn checkout --depth empty svn://anonsvn.kde.org/home/kde/trunk<br />
cd trunk<br />
svn up kdesupport && cd kdesupport<br />
cmakekde<br />
cs trunk<br />
svn up --depth empty KDE<br />
svn up KDE/kdelibs && cd KDE/kdelibs<br />
cmakekde<br />
cs trunk<br />
svn up KDE/kdepimlibs<br />
...<br />
<br />
==== Why do I want to do that? ====<br />
That way you can move stuff around all over the trunk repository, e.g. from playground to kdereview or to KDE/*. The following examples assume that you only want to test or work on single and few modules of trunk. <br />
<br />
This way updating the whole repository to a (hopefully) consitent state, the same revision, is really easy:<br />
<br />
cs trunk # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]<br />
svn up<br />
<br />
== Download and Compile ==<br />
In this section we go over acquiring and building the product.<br />
{{Note|<br />
check out http://kdesvn-build.kde.org/ you may not need to do all of this stuff.<br />
}}<br />
<br />
=== Troubleshooting ===<br />
Please note, that requirements and dependancies frequently change.<br />
You are running an UNSTABLE version, and simply compiling is not guaranteed. You will need to review errors and locate packages, (see acquire dependencies above) and [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information.<br />
<br />
We can now move on to building KDE's most essential libraries.<br />
<br />
=== kdelibs ===<br />
Very important for lots of things, you may need to see troubleshooting and install some things from kdesupport first.<br />
<br />
==== The Recipe ====<br />
cd <br />
cs # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]<br />
mkdir KDE && cd KDE<br />
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs<br />
cd kdelibs<br />
mkdir build<br />
cd build<br />
cmakekde ..<br />
<br />
==== What's Happening ====<br />
We change to the base source directory (line 1) then make and go into the KDE directory (line 3). We download the sources for kdelibs using subversion (line 4), go into the new {{path|~/kde/src/KDE/kdelibs}} directory (line 5), and commence the build (line 6). This will leave us in the <tt>kdelibs</tt> build directory after the build is completed.<br />
<br />
{{tip|There might be missing dependencies on your system! They are easily overlooked in the output of <tt>cmakekde</tt>.<br />
You might want to do a <tt>cmake $KDE_SRC/KDE/MODULE_NAME</tt> prior to compiling any kde modules (like kdelibs, kdepimlibs etc.)}}<br />
<br />
==== Additional KDE-specific CMake know-how ====<br />
<br />
There are additional CMake modules in {{path|kdelibs/cmake/modules/}} that are necessary for building KDE4 applications. These will be installed for you when kdelibs itself is installed.<br />
<br />
To make a non-debug-release (e.g. suppressing all kDebug() messages), use e.g.<br />
cmake -DCMAKE_BUILD_TYPE=Release . && make && make install<br />
<br />
==== Troubleshooting ====<br />
<br />
For troubleshooting information, see the [[Getting_Started/Build/KDE4/Troubleshooting#Issues_building_kdelibs|kdelibs troubleshooting section]].<br />
<br />
=== kdepimlibs ===<br />
Currently kdebase depends on kdepimlibs so it is required to install it first. These libraries are also shared by other packages such as those within kdepim, kdeutils and kdenetwork.<br />
<br />
==== libical ====<br />
Download libical from http://sourceforge.net/project/showfiles.php?group_id=16077, compile, link and install it.<br />
tar xvzf libical-0.41.tar.gz<br />
cd libical-0.41<br />
./configure && make && make install<br />
<br />
==== The Recipe ====<br />
cs KDE # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]<br />
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs<br />
cd kdepimlibs<br />
cmakekde<br />
<br />
==== What's Happening ====<br />
We go into the KDE source directory (line 1), download the source code for kdepimlibs using subversion (line 2) and then go into the new {{path|~/kde/src/KDE/kdepimlibs}} directory (line 3). We then commence the build (line 4). This will leave us in the <tt>kdepimlibs</tt> build directory after the build is completed.<br />
<br />
==== Troubleshooting ====<br />
<br />
For troubleshooting information, see the [[Getting_Started/Build/KDE4/Troubleshooting#Issues_building_kdepimlibs|kdepimlibs troubleshooting section]].<br />
<br />
=== kdebase ===<br />
kdebase is divided into three parts:<br />
* '''apps'''<br />
:This contains applications like Dolphin or KWrite.<br />
* '''runtime'''<br />
:This contains things needed by every application at runtime, like icons. It is a required dependency for each KDE application, so you have to compile and install this.<br />
* '''workspace'''<br />
:This contains things specific to the KDE desktop, like Plasma or the window manager. Most stuff here depends on X11. You only need it if you want to build a full KDE desktop.<br />
<br />
You can build all of kdebase at once, which is described in the recipe below. If you only want to build kdebase-runtime, which is the only requirement, you can replace <code bash>cd kdebase</code> with <code bash>cd kdebase/runtime</code> in the recipe below.<br />
<br />
==== The Recipe ====<br />
cs KDE # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]<br />
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase<br />
cd kdebase<br />
cmakekde<br />
<br />
==== Troubleshooting ====<br />
For troubleshooting information, see the [[Getting_Started/Build/KDE4/Troubleshooting#Issues_building_kdebase|kdebase troubleshooting section]].<br />
<br />
== Translations ==<br />
<br />
Most KDE users are going to install translations before being able to use their desktop properly. Full information is given in the [[Development/Tutorials/Localization/Building_KDE's_l10n_Module|Localisation tutorial]].<br />
For a single language, the following receipe installs messages and translated documentation:<br />
<br />
=== The Recipe ===<br />
cs KDE # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]<br />
svn checkout -N svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4<br />
cd l10n-kde4<br />
svn up scripts <language><br />
./scripts/autogen.sh <language><br />
cd <language><br />
cmakekde<br />
<br />
== Running KDE 4 programs ==<br />
<br />
You can now run KDE 4 programs (e.g. kwrite) by typing:<br />
ssh -X kde-devel@localhost<br />
kwrite <br />
<br />
=== Troubleshooting ===<br />
<br />
For troubleshooting issues see [[Getting_Started/Build/KDE4/Troubleshooting#Running_programs|troubleshooting running programs]].<br />
<br />
== Generating local API documentation ==<br />
<br />
See the [[Development/Tools/apidox|generating apidox]] page.<br />
<br />
== Staying up to date ==<br />
<br />
In order to keep the kde4 installation up to date, each of the modules installed should be updated periodically. As Monday is the day for big changes in kdelibs, Tuesday may be the best day to do this. For each module checked out, run <tt>svn up</tt> and <tt>make</tt>.<br />
<br />
For example:<br />
<code bash><br />
cs kdesupport # cs is not a typo<br />
svn up<br />
cb # cb is not a typo<br />
make install<br />
</code><br />
<br />
Note: it is not necessary to run cmakekde for updates.<br />
<br />
== Installing a subset of a module ==<br />
<br />
Many modules in KDE contain a large number of programs which could take a long time to download and compile. In cases where you want to work only on a particular program or programs in a module, it is possible to download and compile particular folders. In some cases, certain folders are required for any build of the module. This is determined in the CMakeLists.txt file of the module. For example the [http://websvn.kde.org/branches/KDE/4.0/kdegames/CMakeLists.txt?view=markup kdegames CMakeLists.txt file] lists:<br />
<br />
<code><br />
add_subdirectory(libkdegames)<br />
add_subdirectory(libkmahjongg)<br />
<br />
macro_optional_add_subdirectory(doc)<br />
macro_optional_add_subdirectory(lskat)<br />
macro_optional_add_subdirectory(katomic)<br />
</code><br />
<br />
So, the libkdegames and libkmahjongg directories are required to build any of kdegames. The cmake directory will also usually be required. All the other directories (doc, katomic etc) are optional. They will be built if present on your machine. In this example, we build kmahjongg and kbattleship:<br />
<br />
<code bash><br />
cs KDE<br />
svn co -N svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames # The -N switch performs a non-recursive checkout<br />
cd kdegames<br />
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/libkdegames # Get required directories<br />
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/libkmahjongg<br />
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/cmake<br />
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/kbattleship # Get optional directories<br />
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/kmahjongg<br />
cmakekde <br />
</code><br />
<br />
== Success! ==<br />
<br />
You are now ready to start building other svn modules in the same fashion as you built kdebase, running and testing KDE4 or writing your own patches and applications.<br />
<br />
For further isolation of your development environment change symbolic links, which you will see after executing ls -lh $(kde4-config --localprefix), assuming newly installed kde4-config is called.<br />
<br />
See the [[Getting Started/Set up KDE 4 for development|Set up KDE 4 for development]] tutorial for how to start KDE 4 applications and how to use KDevelop to work on them.<br />
<br />
For most of what you need to know on patches see: [[Contribute/Send Patches|Sending Patches]]<br />
<br />
[[Category:Build KDE]]<br />
[[Category:KDE4]]<br />
{{Build KDE}}{{Getting Started}}</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Distributions_with_KDE&diff=53216Distributions with KDE2010-08-06T01:28:18Z<p>AaronPeterson: </p>
<hr />
<div>__NOTOC__<br />
== Debian Based ==<br />
Debian<br />
<br />
SID<br />
=== Ubuntu / Kubuntu===<br />
<br />
: 10.04 -- [[4.4]]<br />
: 9.10 -- [[4.3]]<br />
: 8.04 -- [[3.5]]<br />
<br />
== RedHat ==<br />
===Fedora===<br />
===Mandriva===<br />
===Suse===<br />
<br />
<br />
==Slackware==<br />
==Gentoo==<br />
<br />
{{stub}}</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Distributions_with_KDE&diff=53215Distributions with KDE2010-08-06T01:22:58Z<p>AaronPeterson: This page is intended to help users find a distrubtion by version of KDE that they want to have</p>
<hr />
<div>== Debian Based ==<br />
Debian<br />
<br />
SID<br />
=== Ubuntu / Kubuntu===<br />
<br />
: 10.04 -- [[4.4]]<br />
: 9.10 -- [[4.3]]<br />
: 8.04 -- [[3.5]]<br />
<br />
== RedHat ==<br />
===Fedora===<br />
===Mandriva===<br />
===Suse===<br />
<br />
<br />
==Slackware==<br />
==Gentoo==<br />
<br />
{{stub}}</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Template:Current_Version&diff=53214Template:Current Version2010-08-06T01:17:49Z<p>AaronPeterson: This page is intended to be included in other pages</p>
<hr />
<div><!-- This page is intended to be included in many pages --><br />
;Trunk: [[4.6]]<br />
;Release: [[4.5]]<br />
;Still Supported: [[4.4]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53212Getting Started2010-08-06T00:55:47Z<p>AaronPeterson: /* Version */</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
=== [[Choose Version]] ===<br />
For production use, we recommend using a stable "branch" version of KDE. If you just want to use KDE, take a look at http://userbase.kde.org/. If you are developing applications, your distribution's dev packages and the kde-sdk may work. If your distribution does not have KDE you'll need to build it yourself. <br />
<br />
If you want to hack at KDE's core modules, you'll need to build it, and TRUNK is the main branch where new features (and prerequisites) are added, however it can be difficult to keep up with.<br />
<br />
[[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems Incl KDE3''<br />
<br />
To See which versions/branches of KDE are available go to:<br />
::http://websvn.kde.org/branches/KDE/<br />
<br />
=== Location ===<br />
It is possible to install KDE in a variety of ways. Instructions should be listed with each build method, however much is common between methods and reading all may be required. Note that if using system Qt for a user based KDE install, the [[QCA plugin]] may have to be installed as root)<br />
<br />
; development user home <br />
This is a common way to do it so that it does not interefere with your production user and the rest of the system. A common user name is kde-devel. This is recommended for the cautious testers and developers. You can still use [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]] to switch between system and regular.<br />
<br />
; your home directory <br />
Useful on development machines, or if you have no other access to the machine, you will have to set environment variables to switch between system and user versions of KDE, There are some [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]] to help you use it. And switching back and forth between versions of a program are likely to corrupt your data.<br />
<br />
; system-wide<br />
on development systems, do it to test KDM and other system level KDE functionality. This is normal for production use. If you are just testing KDM, you may want to use a virtual machine so you do not damage a production system.<br />
<br />
=== Method ===<br />
<br />
Regardless of method chosen, reading up on the manual steps below will be very helpful.<br />
[[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: Manual, but with a few scripts to keep everything easy<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
* This will compile qt for you, or you can configure it to use system QT<br />
* When you choose a branch<br />
** edit your ''.kdesrc-buildrc'' <br />
*** set your branch<br />
*** you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: ''module-base-path tags/kdesupport-for-4.5''<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53211Getting Started2010-08-05T23:39:47Z<p>AaronPeterson: /* Build it */</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
=== Version ===<br />
For production use, we recommend using a stable "branch" version of KDE. If you just want to use KDE, take a look at http://userbase.kde.org/. If you are developing applications, your distribution's dev packages and the kde-sdk may work. If your distribution does not have KDE you'll need to build it yourself. <br />
<br />
If you want to hack at KDE's core modules, you'll need to build it, and TRUNK is the main branch where new features (and prerequisites) are added, however it can be difficult to keep up with.<br />
<br />
[[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems Incl KDE3''<br />
<br />
To See which versions/branches of KDE are available go to:<br />
::http://websvn.kde.org/branches/KDE/<br />
<br />
<br />
=== Location ===<br />
It is possible to install KDE in a variety of ways. Instructions should be listed with each build method, however much is common between methods and reading all may be required. Note that if using system Qt for a user based KDE install, the [[QCA plugin]] may have to be installed as root)<br />
<br />
; development user home <br />
This is a common way to do it so that it does not interefere with your production user and the rest of the system. A common user name is kde-devel. This is recommended for the cautious testers and developers. You can still use [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]] to switch between system and regular.<br />
<br />
; your home directory <br />
Useful on development machines, or if you have no other access to the machine, you will have to set environment variables to switch between system and user versions of KDE, There are some [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]] to help you use it. And switching back and forth between versions of a program are likely to corrupt your data.<br />
<br />
; system-wide<br />
on development systems, do it to test KDM and other system level KDE functionality. This is normal for production use. If you are just testing KDM, you may want to use a virtual machine so you do not damage a production system.<br />
<br />
=== Method ===<br />
<br />
Regardless of method chosen, reading up on the manual steps below will be very helpful.<br />
[[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: Manual, but with a few scripts to keep everything easy<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
== Build it ==<br />
; Most used method, augmented with bash functions.<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
* This will compile qt for you, or you can configure it to use system QT<br />
* When you choose a branch<br />
** edit your ''.kdesrc-buildrc'' <br />
*** set your branch<br />
*** you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: ''module-base-path tags/kdesupport-for-4.5''<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53210Getting Started2010-08-05T23:38:39Z<p>AaronPeterson: /* Build it */ David's method is the one that most people use, My goal is to feature this method, and make others appear as alternatives</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
=== Version ===<br />
For production use, we recommend using a stable "branch" version of KDE. If you just want to use KDE, take a look at http://userbase.kde.org/. If you are developing applications, your distribution's dev packages and the kde-sdk may work. If your distribution does not have KDE you'll need to build it yourself. <br />
<br />
If you want to hack at KDE's core modules, you'll need to build it, and TRUNK is the main branch where new features (and prerequisites) are added, however it can be difficult to keep up with.<br />
<br />
[[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems Incl KDE3''<br />
<br />
To See which versions/branches of KDE are available go to:<br />
::http://websvn.kde.org/branches/KDE/<br />
<br />
<br />
=== Location ===<br />
It is possible to install KDE in a variety of ways. Instructions should be listed with each build method, however much is common between methods and reading all may be required. Note that if using system Qt for a user based KDE install, the [[QCA plugin]] may have to be installed as root)<br />
<br />
; development user home <br />
This is a common way to do it so that it does not interefere with your production user and the rest of the system. A common user name is kde-devel. This is recommended for the cautious testers and developers. You can still use [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]] to switch between system and regular.<br />
<br />
; your home directory <br />
Useful on development machines, or if you have no other access to the machine, you will have to set environment variables to switch between system and user versions of KDE, There are some [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]] to help you use it. And switching back and forth between versions of a program are likely to corrupt your data.<br />
<br />
; system-wide<br />
on development systems, do it to test KDM and other system level KDE functionality. This is normal for production use. If you are just testing KDM, you may want to use a virtual machine so you do not damage a production system.<br />
<br />
=== Method ===<br />
<br />
Regardless of method chosen, reading up on the manual steps below will be very helpful.<br />
[[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: Manual, but with a few scripts to keep everything easy<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
== Build it ==<br />
; Bash Script<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
* This will compile qt for you, or you can configure it to use system QT<br />
* When you choose a branch<br />
** edit your ''.kdesrc-buildrc'' <br />
*** set your branch<br />
*** you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: ''module-base-path tags/kdesupport-for-4.5''<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Getting_Started&diff=53209Getting Started2010-08-05T23:30:48Z<p>AaronPeterson: /* Determine Your Needs */ reorganizing, will make kdesrc-build less prominent because I was advised to just build it manually.</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}} <br />
<br />
== Determine Your Needs==<br />
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]]. <br />
<br />
=== Version ===<br />
For production use, we recommend using a stable "branch" version of KDE. If you just want to use KDE, take a look at http://userbase.kde.org/. If you are developing applications, your distribution's dev packages and the kde-sdk may work. If your distribution does not have KDE you'll need to build it yourself. <br />
<br />
If you want to hack at KDE's core modules, you'll need to build it, and TRUNK is the main branch where new features (and prerequisites) are added, however it can be difficult to keep up with.<br />
<br />
[[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems Incl KDE3''<br />
<br />
To See which versions/branches of KDE are available go to:<br />
::http://websvn.kde.org/branches/KDE/<br />
<br />
<br />
=== Location ===<br />
It is possible to install KDE in a variety of ways. Instructions should be listed with each build method, however much is common between methods and reading all may be required. Note that if using system Qt for a user based KDE install, the [[QCA plugin]] may have to be installed as root)<br />
<br />
; development user home <br />
This is a common way to do it so that it does not interefere with your production user and the rest of the system. A common user name is kde-devel. This is recommended for the cautious testers and developers. You can still use [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]] to switch between system and regular.<br />
<br />
; your home directory <br />
Useful on development machines, or if you have no other access to the machine, you will have to set environment variables to switch between system and user versions of KDE, There are some [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]] to help you use it. And switching back and forth between versions of a program are likely to corrupt your data.<br />
<br />
; system-wide<br />
on development systems, do it to test KDM and other system level KDE functionality. This is normal for production use. If you are just testing KDM, you may want to use a virtual machine so you do not damage a production system.<br />
<br />
=== Method ===<br />
<br />
Regardless of method chosen, reading up on the manual steps below will be very helpful.<br />
[[Development/CMake|CMake]] may also be of interest.<br />
<br />
; Fully Manual<br />
; Distribution Specific <br />
; Augmented (Recommended)<br />
: Manual, but with a few scripts to keep everything easy<br />
; KDEsrc-build <br />
: Useful for automated builds, may be tough to set up<br />
<br />
== Gather Prerequisites ==<br />
Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options.<br />
<br />
* [[Getting_Started/Build/KDE4/Prerequisites]]<br />
* [[build requirements]] by distribution<br />
<br />
== Build it ==<br />
; distribution specific<br />
There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. <br />
<br />
; kdesrc-build<br />
This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].<br />
<br />
* This will compile qt for you, or you can configure it to use system QT<br />
* When you choose a branch<br />
** edit your ''.kdesrc-buildrc'' <br />
*** set your branch<br />
*** you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: ''module-base-path tags/kdesupport-for-4.5''<br />
<br />
; Bash Script<br />
[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]] <br />
<br />
; Manual Steps <br />
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]<br />
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]<br />
* [[Getting_Started/Build/KDE4.4 Upgrade|Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH)]]<br />
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''<br />
<br />
==Getting the Source==<br />
[[Image:Action_down.svg|right|32px]]<br />
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]<br />
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''<br />
* [[Getting_Started/Sources/Amarok Git Tutorial|Amarok Git Tutorial]] ''Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop.''<br />
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]<br />
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]<br />
<br />
== Troubleshooting the build ==<br />
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]<br />
<br />
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.<br />
<br />
Compile and Linking errors are frequent sources of discouragement. make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. <br />
<br />
Please review your logs and do searches for fixes. If you cannot find a solution, [[Build/KDE4/Errors]] and IRC channel, and mailing lists. [[Build/Stories]]<br />
<br />
==Using your KDE==<br />
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:<br />
; Environment Variables<br />
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.<br />
[[Image:Action_pen.svg|right|32px]]<br />
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]<br />
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]<br />
<br />
==Set up Development Tools==<br />
You may need to set up or use, you will likely want to use a stable package from your distribution.<br />
<br />
it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help<br />
<br />
For most development topics, and documentation, see [[Development]]<br />
<br />
; Opening and creating KDE project files<br />
* [[eclipse]]<br />
* [[kdevelop]]<br />
* [[qtdesigner]]<br />
<br />
<br />
This is a stub, please help.<br />
<br />
==Contribution==<br />
You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix.<br />
<br />
[[Image:Action_tool.svg|right|32px]]<br />
* [[Contribute|Contribute]]<br />
* [[Contribute/Send_Patches|Send Patches]]<br />
* [[Contribute/Bugsquad|Bugsquad]]<br />
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]<br />
<br />
<br />
[[Category:Build_KDE]]</div>AaronPetersonhttps://techbase.kde.org/index.php?title=Welcome_to_KDE_TechBase/20100805/&diff=53204Welcome to KDE TechBase/20100805/2010-08-05T10:38:22Z<p>AaronPeterson: moved Welcome to KDE TechBase/20100805/ to User:AaronPeterson/Welcome to KDE TechBase/20100805/</p>
<hr />
<div>#REDIRECT [[User:AaronPeterson/Welcome to KDE TechBase/20100805/]]</div>AaronPeterson