Skip to content

Conversation

@naokiri
Copy link
Member

@naokiri naokiri commented Nov 7, 2025

Suggested fix on the last comment of #83

TODO: Need to review and confirm the release file actually works before merging. Run with workflow_dispatch event and fix the release file not to be attatched to the release but to be downloadable on manual run

@naokiri naokiri force-pushed the reenable_github_action_builds branch from 681d255 to c5b6588 Compare November 7, 2025 12:39
@naokiri naokiri marked this pull request as draft November 7, 2025 12:40
@naokiri naokiri force-pushed the reenable_github_action_builds branch from eb9ac4b to c1cb2e6 Compare November 28, 2025 06:36
@naokiri naokiri force-pushed the reenable_github_action_builds branch from c1cb2e6 to 852034f Compare November 28, 2025 06:52
@naokiri naokiri force-pushed the reenable_github_action_builds branch 9 times, most recently from 004ec7e to 3027da2 Compare November 29, 2025 08:40
@naokiri naokiri force-pushed the reenable_github_action_builds branch from 3027da2 to cc42f94 Compare November 29, 2025 08:51
@naokiri
Copy link
Member Author

naokiri commented Nov 29, 2025

Current issue: library path problem

On Archlinux and most fcitx5 development environment (= the new build env) -> uses source builds and saves RPATH on build, so they can find the shared libraries.

On deb file I'm making -> I want to make it able to use with latest Ubuntu at least as large portion of JP Linux users use that distribution. They expect fcitx5 libraries to be under /lib/x86_64-linux-gnu/fcitx5/ so making the deb file to distribute this lib to that directory even though it is usually for system's package managers' directory.

CSKK -> The deb file on release places the libcskk under /usr/local/lib/cskk as it is not expected to be the system's library but more like a local build library.

For these mixed up pathes especially the RPATH stored on the build time, the library search paths are mixed up and not easy to confirm what library is actually missing or just unable to find from the search paths or accidentally finding the old version.

Storing RPATH on build was an easy fix for using non-system library like CSKK but it causes more trouble when we want to run on multiple environments and expecting different build environment and runtime environment.

We probably need to disable storing RPATH and find a better solution for locally built libraries.

@naokiri
Copy link
Member Author

naokiri commented Nov 30, 2025

Even if I fix the library resolution PATHs, making a good deb file for Ubuntu24 seems hard because fcitx5 have changed the ABI and now we are building against latest fcitx5 which uses FCITX_ADDON_FACTORY_V2, but the Ubuntu's fcitx5 package only accepts FCITX_ADDON_FACTORY version.
Being able to build with newer fcitx5 is important as wayland is evolving fast these days, but if I want to support most of the JP users I have to retain the old code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants