Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge fcitx/master; use the shared copy of data files provided by pac…
…kage 'rime-data' or 'brise'.
- Loading branch information
Showing
5 changed files
with
127 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
## RIME support for Fcitx | ||
|
||
RIME(中州韻輸入法引擎) is _mainly_ a Traditional Chinese input method engine. | ||
|
||
project: https://code.google.com/p/rimeime | ||
|
||
|
||
## Build From Source: | ||
|
||
### special notice of RIME dependency: | ||
|
||
RIME split its devlopment source into a few sections, here we need librime. | ||
|
||
In librime source, there are two directory, brise and librime. | ||
|
||
According to your distribution, you might need brise+librime package(openSUSE) or only librime which includes brise at /usr/share/brise. | ||
|
||
If your distribution doesn't have one you need to download librime and put brise directory into /usr/share/brise. | ||
|
||
If you're a distribution packager, ask maintainer of librime to add brise sub-package. | ||
|
||
### special notice of Boost dependency: | ||
|
||
Boost is a RIME dependency, so without boost >= 1.46.1, you will not ble to install librime-devel. | ||
|
||
Generally it means, distros that are a little old like openSUSE 11.4 or Ubuntu 10.10 might not be possible to build or install. | ||
|
||
### Dependency | ||
|
||
*cmake | ||
|
||
*gcc-c++ | ||
|
||
*intltool | ||
|
||
*fcitx-devel with all three skins | ||
|
||
some distro like openSUSE split a fcitx-skin-classic and a fcitx-skin-dark, so you need them. | ||
|
||
*librime-devel | ||
|
||
*brise | ||
|
||
*hicolor-icon-theme | ||
|
||
optional, for directory ownership. | ||
|
||
#### openSUSE: | ||
|
||
sudo zypper ar -f http://download.opensuse.org/repositories/M17N/openSUSE_12.2/ M17N | ||
|
||
sudo zypper in cmake gcc-c++ fcitx-devel fcitx-skin-classic fcitx-skin-dark librime-devel brise hicolor-icon-theme | ||
|
||
|
||
## Install from Distribution | ||
|
||
### openSUSE | ||
|
||
sudo zypper ar -f http://download.opensuse.org/repositories/M17N/openSUSE_12.2/ M17N | ||
|
||
sudo zypper in fcitx-rime | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Author: Marguerite Su <i@marguerite.su> | ||
# License: same as fcitx | ||
# Description: find RIME brise schemas collection package. | ||
# BRISE_FOUND - System has brise package | ||
# BRISE_DIR - Brise absolute path | ||
|
||
set(BRISE_FIND_DIR "${CMAKE_INSTALL_PREFIX}/share/brise" | ||
"${CMAKE_INSTALL_PREFIX}/share/rime-data" | ||
"${CMAKE_INSTALL_PREFIX}/share/rime/data" | ||
"/usr/share/brise" | ||
"/usr/share/rime-data" | ||
"/usr/share/rime/data") | ||
|
||
set(BRISE_FOUND FALSE) | ||
|
||
foreach(_BRISE_DIR ${BRISE_FIND_DIR}) | ||
if (IS_DIRECTORY ${_BRISE_DIR}) | ||
set(BRISE_FOUND True) | ||
set(BRISE_DIR ${_BRISE_DIR}) | ||
endif (IS_DIRECTORY ${_BRISE_DIR}) | ||
endforeach(_BRISE_DIR) | ||
|
||
include(FindPackageHandleStandardArgs) | ||
find_package_handle_standard_args(Brise DEFAULT_MSG | ||
BRISE_DIR) | ||
mark_as_advanced(BRISE_DIR) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters