Kdenlive/Manual/Installation/ru: Difference between revisions

Revision as of 09:21, 25 October 2012

Other languages:

Установка

Установка бинарных пакетов

Мультимедийные пакеты доступны во многих альтернативных хранилищах , часто из-за определенных ограничений на доступные кодеки, в связи с патентами в ряде стран (в основном США на данный момент).

Everything would be perfect in a wonderful world if package builders would contribute to official distributions, and multimedia editors chose only free codecs to promote their use worldwide ... So try to stick to distributions deliveries?

Debian, Ubuntu и производные

Debian project ships Kdenlive packages since "squeeze" (6.0) release, however to benefit from recent updates and bugfixes you might consider upgrading to a "testing" release or even "sid".

Ubuntu also offers Kdenlive since "gutsy" (7.10), but for similar reasons it could be preferable to upgrade to the latest release.

In both cases a simple apt-get install kdenlive should then work.

Fedora, RedHat и производные

RPM packages are not yet maintained in official branch, so you must go through unofficial RPM Fusion repository. Follow the site recommendations to make them available and end with yum install kdenlive

Gentoo, Arch, BSD порты

Building scripts are ready for up-to-date systems, so run respectively emerge kdenlive or pacman -S kdenlive or pkg_add kdenlive, etc.

Windows

Версии Kdenlive для Windows ещё не существует. Тем не менее, вы можете использовать некоторые виртуальные (Live)Linux дистрибутивы для запуска Kdenlive в Windows. Некоторые советы можно найти на этой странице.

MacOS

'Kdenlive и 'MLT можно скомпилировать и запустить под Mac OS X. Пакеты доступны из проекта MacPorts .

MacPorts is a source-based system - there is not a binary app bundle for Kdenlive. Therefore, Kdenlive and all of its numerous dependencies including multimedia libraries, KDE, and Qt must be compiled. This can take a long time and much disk space! Furthermore, it is not unusual for something not to build correctly; it is definitely not something for the novice, impatient, or "faint of heart."

Для получения дополнительной информации см. здесь

Установка из исходных кодов

If you want to test latest committed code or your personal patches, you will have to build Kdenlive (and probably MLT) on your own.

You can use your distribution's package building procedure to use its software management system to install/upgrade/remove the binaries and data, and eventually share your builds (and even contribute to package maintainance - refer to the respective distribution manual).

If you prefer you can build & install Kdenlive to a local area (preferably not /usr, but rather /usr/local or $HOME/my_local_builds/kdenlive-last-release or similar). It is then recommanded to use the build script ^[1]

↑ on distributions older than Debian 6 or Ubuntu 10.04 and derivatives, you need to set ENABLE_SWFDEC=0 in the config variables of the script

[1] stributions older than Debian 6 or Ubuntu 10.04 and derivatives, you need to set ENABLE_SWFDEC=0 in the config variables of the script

[1]

@@ Line 35: / Line 35: @@
 MacPorts is a source-based system - there is not a binary app bundle for Kdenlive. Therefore, '''Kdenlive''' and all of its numerous dependencies including multimedia libraries, KDE, and Qt must be compiled. This can take a long time and much disk space! Furthermore, it is not unusual for something not to build correctly; it is definitely not something for the novice, impatient, or "faint of heart."
-Для получения дополнительной информации см. [http://www.kdenlive.org/user-manual/downloading-and-installing-kdenlive/pre-compiled-packages/mac-os-x-packages-macports this]
+Для получения дополнительной информации см. [http://www.kdenlive.org/user-manual/downloading-and-installing-kdenlive/pre-compiled-packages/mac-os-x-packages-macports здесь]
 === Установка из исходных кодов ===