Difference between revisions of "Getting Started/zh-cn"

Jump to: navigation, search
(Created page with "== 从源构建和运行 KDE 软件 ==")
(Updating to match new version of source page)
 
(One intermediate revision by one other user not shown)
Line 52: Line 52:
 
* [[Special:myLanguage/Getting_Started/Run/Full_Session|How to Run a full session of KDE]]
 
* [[Special:myLanguage/Getting_Started/Run/Full_Session|How to Run a full session of KDE]]
  
==开发模式==
+
== 开发工具 ==
 
+
TODO: General introduction to the dev model, release cycles, etc.
+
 
+
* [[Special:myLanguage/Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
+
* [[Special:myLanguage/Development/Software_Engineering_Framework|The KDE Software Engineering Framework]]
+
* [[Special:myLanguage/Policies|KDE Development Policies and Procedures to follow]]
+
* [[Special:myLanguage/Policies/Application_Lifecycle|The development lifecycle for a new application]]
+
 
+
== Development Tools ==
+
  
 
There are a number of [[Special:myLanguage/Development/Tools|Development Tools]] that are either required or helpful when building KDE Software.  For these you will usually want to use the stable packages provided by your distribution.
 
There are a number of [[Special:myLanguage/Development/Tools|Development Tools]] that are either required or helpful when building KDE Software.  For these you will usually want to use the stable packages provided by your distribution.
Line 79: Line 70:
 
* [[Special:myLanguage/Contribute/Send_Patches|Send Patches]]
 
* [[Special:myLanguage/Contribute/Send_Patches|Send Patches]]
 
* [[Special:myLanguage/Contribute/Bugsquad|Bugsquad]]
 
* [[Special:myLanguage/Contribute/Bugsquad|Bugsquad]]
 +
 +
 +
==开发模式==
 +
 +
This is information for release schedules, justification of why KDE has chosen the tools and policies that it has, and so on.  It used to be very important since KDE releases were done as big coordinated simutaneous efforts.  This is all completely outdated since the policy changed with KDE Frameworks 5.  Now, various parts of KDE have their own release cadences, ranging from regular monthly releases for Frameworks, every 3- or 4-months for Plasma, to "it happens when it happens" for applications like Krita.
 +
 +
TODO: completely rewrite everything here.
 +
 +
* [[Special:myLanguage/Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
 +
* [[Special:myLanguage/Development/Software_Engineering_Framework|The KDE Software Engineering Framework]]
 +
* [[Special:myLanguage/Policies|KDE Development Policies and Procedures to follow]]
 +
* [[Special:myLanguage/Policies/Application_Lifecycle|The development lifecycle for a new application]]
  
 
[[Category:Build_KDE]]
 
[[Category:Build_KDE]]

Latest revision as of 10:25, 11 March 2016

Other languages:
Ελληνικά • ‎English • ‎suomi • ‎français • ‎日本語 • ‎한국어 • ‎Nederlands • ‎português do Brasil • ‎русский • ‎Türkçe • ‎中文(中国大陆)‎
noframe
 
Warning
为反映新的KDE基础设施,目前这些网页正被完全重写,可能包含不一致的内容。一些网页上的信息和命令可能不再有效,请小心使用。


简介

加入 KDE 社区方式多种多样,最常见的方式是从单纯使用我们的软件开始到最终成为核心平台开发者。

本部分内容属于 KDE TechBase,用于引导您加入 KDE 社区的技术部落。您将了解到 KDE 软件的结构及如何构建,以及如何构建您自己的 KDE 软件。

使用 KDE 软件

如果您仅仅是想使用稳定版的 KDE 软件用于日常计算需求的话,那么您就不需要自己构建 KDE 软件,只需要使用 Linux 发行商提供的安装包安装即可。

学习如何使用 KDE 软件的最佳地点就是发行商的网站的技术支持频道。不过你也可以在下面这些链接的页面发现有用的信息:

获取帮助

如果您正在寻找 KDE Workspace 或 KDE 应用程序帮助信息的话,那么请访问 KDE UserBase.

如果您在构建或开发 KDE 软件期间有任何的问题或困难,您可以求助。 However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it all for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

浏览代码

KDE 项目完全自由开源。您可以查看和修改源代码。

http://projects.kde.org hosts the source for many KDE-related initiatives, including KDE itself. Choose a piece of KDE such as KDE Libraries, then click Repository to browse its source. Getting_Started/Sources explains the organization of KDE source code.

There are other utilities to browse the source code:

从源构建和运行 KDE 软件

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the Build Methods page.

If you simply want to build one application, the simple tutorial Building an Existing Application might be enough already.

noframe
 
Note
Quickstart: If you are impatient to get started without understanding what you are doing then you can skip straight to using a Build Script, but it is strongly recommended you read this documentation first.


The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

开发工具

There are a number of Development Tools that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:

Contributing To KDE

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

Action tool.svg


开发模式

This is information for release schedules, justification of why KDE has chosen the tools and policies that it has, and so on. It used to be very important since KDE releases were done as big coordinated simutaneous efforts. This is all completely outdated since the policy changed with KDE Frameworks 5. Now, various parts of KDE have their own release cadences, ranging from regular monthly releases for Frameworks, every 3- or 4-months for Plasma, to "it happens when it happens" for applications like Krita.

TODO: completely rewrite everything here.


This page was last modified on 11 March 2016, at 10:25. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2 unless otherwise noted.