Compiling Mozc - Revision history

Weng Xuetian at 02:17, 29 March 2022

2022-03-29T02:17:10Z

← Older revision		Revision as of 02:17, 29 March 2022
Line 28:		Line 28:
	You'll need to put those files to the corresponding places:		You'll need to put those files to the corresponding places:

	<code>bazel-bin/unix/fcitx5/fcitx5-mozc.so</code> to <code>FCITX_PREFIX/lib/fcitx5/</code>		<code>bazel-bin/unix/fcitx5/fcitx5-mozc.so</code> to <code>FCITX_PREFIX/lib/fcitx5/</code> (For Debian/Ubuntu it should be <code>PREFIX/lib/[arch]/fcitx5</code>, e.g. <code>PREFIX/lib/x86_64-linux-gnu/fcitx5</code>).

	<code>bazel-bin/server/mozc_server</code> to <code>/usr/lib/mozc</code>		<code>bazel-bin/server/mozc_server</code> to <code>/usr/lib/mozc</code>

Weng Xuetian at 22:28, 28 March 2022

2022-03-28T22:28:08Z

← Older revision		Revision as of 22:28, 28 March 2022
Line 4:		Line 4:

	= Build Mozc with bazel =		= Build Mozc with bazel =
			If you clone the code from git repository, make sure you also fetch all the submodule. You can do this by <code>git submodule update --init --recursive</code>.

			Sometimes you may need to restart bazel to reload certain data (e.g. you already run bazel before you get all submodule), you can do <code>bazel clean; bazel shutdown</code>.

	While the command to build fcitx with bazel is simple, making bazel to locate the correct dependencies can be tricky, because the path of dependencies are all hard coded in the bazel's config file under src/. You are likely need to adjust QT_BASE_PATH if you are not building it under debian.		While the command to build fcitx with bazel is simple, making bazel to locate the correct dependencies can be tricky, because the path of dependencies are all hard coded in the bazel's config file under src/. You are likely need to adjust QT_BASE_PATH if you are not building it under debian.

	BUILD.fcitx5.bazel and WORKSPACE.bazel may also need to be updated to match your path. If you need custom prefix, the mozc server path also needs to be adjusted in config.bzl accordingly.		BUILD.fcitx5.bazel and WORKSPACE.bazel may also need to be updated to match your path. If you need custom prefix, the mozc server path also needs to be adjusted in config.bzl accordingly.

	If you are using bazel 5.0.0, you will hit [https://github.com/bazelbuild/bazel/issues/14260 an issue] that always require android NDK even if it is not used. It need to workaround by commenting out the <code>android_ndk_repository</code> line in WORKSPACE.bazel.		If you are using bazel 5.0.0, you will hit [https://github.com/bazelbuild/bazel/issues/14260 an issue] that always require android NDK even if it is not used. It need to workaround by commenting out the <code>android_ndk_repository</code> line in WORKSPACE.bazel (Maybe android_sdk_repository if you have error relevant to it).

	<pre>cd src # Need to run the bazel command under src/		<pre>cd src # Need to run the bazel command under src/

Weng Xuetian: Created page with "Fcitx maintains a fork of mozc that contains the support for [https://github.com/google/mozc/ Mozc]. Building mozc can be very tricky because it uses uncommon build system on..."

2022-02-02T18:58:34Z

Created page with "Fcitx maintains a fork of mozc that contains the support for [https://github.com/google/mozc/ Mozc]. Building mozc can be very tricky because it uses uncommon build system on..."

New page

Fcitx maintains a fork of mozc that contains the support for [https://github.com/google/mozc/ Mozc].

Building mozc can be very tricky because it uses uncommon build system on the Linux. The old one is [https://gyp.gsrc.io/ gyp] and the new one is [https://bazel.build/ bazel].

= Build Mozc with bazel =
While the command to build fcitx with bazel is simple, making bazel to locate the correct dependencies can be tricky, because the path of dependencies are all hard coded in the bazel's config file under src/. You are likely need to adjust QT_BASE_PATH if you are not building it under debian.

BUILD.fcitx5.bazel and WORKSPACE.bazel may also need to be updated to match your path. If you need custom prefix, the mozc server path also needs to be adjusted in config.bzl accordingly.

If you are using bazel 5.0.0, you will hit [https://github.com/bazelbuild/bazel/issues/14260 an issue] that always require android NDK even if it is not used. It need to workaround by commenting out the <code>android_ndk_repository</code> line in WORKSPACE.bazel.

<pre>cd src # Need to run the bazel command under src/
# Build 3 target: mozc_server, qt based GUI tool and fcitx5's plugin.
bazel build -c opt --copt=-fPIC --config oss_linux unix/fcitx5:fcitx5-mozc.so server:mozc_server gui/tool:mozc_tool
</pre>

The command above will generate following files required by mozc:

<pre>bazel-bin/unix/fcitx5/fcitx5-mozc.so
bazel-bin/server/mozc_server
bazel-bin/gui/tool/mozc_tool
</pre>

You'll need to put those files to the corresponding places:

<code>bazel-bin/unix/fcitx5/fcitx5-mozc.so</code> to <code>FCITX_PREFIX/lib/fcitx5/</code>

<code>bazel-bin/server/mozc_server</code> to <code>/usr/lib/mozc</code>

<code>bazel-bin/gui/tool/mozc_tool</code> to <code>/usr/lib/mozc</code>

<code>../scripts/install_fcitx5_bazel</code> and <code>../scripts/install_server_bazel</code> can be used to help you as a reference on what needs to be done.

= Build Mozc with gyp =
This method may be deprecated any time depending on the upstream. In fcitx/mozc repository, there are some scripts that helps to build it with gyp. As for now, it does not support python 3.10. Another issue is that it will also use libc++ to build, which is not an option if fcitx5 links to stdc++.

<pre>cd src/
# Set this environment variable if you want Release build: _bldtype=Release
GYP_DEFINES="use_fcitx=0 use_libibus=0" ../scripts/configure # Pass --server_dir if you want a different mozc server directory.
sed "/stdlib=libc++/d;/-lc++/d" -i gyp/common.gypi
../scripts/build_fcitx5
../scripts/install_server
../scripts/install_fcitx5
</pre>

The default path used by the script is assuming /usr as prefix, please adjust by set PREFIX environment variable if you want a custom prefix, or just do the installation manually.