so, When I asked about the project aiming for height at last, I tried multi-booting on a laptop.
Since ibus-anthy was the only Japanese input, [mozc](https://github.com/google/mozc mozc) I was investigating the reason why there was no. The build steps themselves have been simplified. Since it has been used normally for a long time in other distributions, there is no problem with mozc itself. For Linux and Android, it seems to run in an Ubuntu container on Docker and create a binary.
Now the process is clarified and people who maintain the package and build. As long as there are people who understand, we can continue to benefit. I decided to benefit from mozc on Alpine Linux as well.
I didn't have gyp from edge, but I was able to build it. Samurai (ninja) also worked without any error in the minimum up-to-date state in the container.
Thank you for your hard work. Thank you very much.
The place where I modified it was a build environment premised on clang, but I confirmed that it can be built with gcc, so I adjusted the contents of gyp/common.gypi accordingly. In base/mutex.cc, just change from RECURSIVE_NP to RECURSIVE, one branch correction.
I have confirmed that clang can be built on alpine if you do some tricky things such as changing the location of the unique header.
The rest is the same even if you install from the source, but in order to understand the mechanism of abuild, I referred to ninja's APKGBUILD and ibus-anthy's package.
In order to put the ibus-mozc package on aports testing, you have to check the procedure. I sent an email, but ~~ ninja seems to be out of maintenance at the edge, so if you don't explain the relationship there, other people may stumble. It worked with the ~~ samurai package.
Currently, I switched between ibus-anthy and ibus-mozc on alpine linux, and both worked. The setting panel can also be displayed, and Japanese input can be performed normally. It's Japanese. Hooray. I really appreciate it. For the installation method, ibus-mozc build notes was concise and helpful.
If you refer to the above reference site, you can install it manually in various environments.
The package will be when testing of aports is accepted, but I wonder if it will be OK if I do not organize it including the relationship with ninja. Also, I would like to check and organize the build process and package dependencies on a clean plain alpine container.
Thank you everyone for putting together all the information. that's all.
'mozc google' 'mozc branch alpine_edge'
apk update
apk upgrade
apk add alpine-sdk clang samurai ibus-dev qt5-qtbase-dev gtk+2.0-dev \
py3-core-api samurai pkgconf git clang
git clone --branch alpine_edge --single-branch --depth 1 --recursive https://github.com/phoepsilonix/mozc mozc
git submodule update --init
cd mozc/src
python3 build_mozc.py gyp
python3 build_mozc.py build -c Release package
~~~
Recommended Posts