View Single Post
Old 10-11-2019, 12:07 PM   #61
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,689
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by User_Z View Post
5. DiapDealer, instead of writing that you, without knowing Haiku, fixed plug-in problems in 10 minutes, it would be better to write how to do it.
I did that already. The detailed instructions I attached upthread documented how I got Haiku with plugin support running (albeit with Python 3.6). It would be trivial for someone with intimate knowledge of HaikuPorts packaging to use those instructions to get a working package.

The plugin framework is being orphaned because Sigil doesn't know what happened to its "share/sigil" directory. Because no one bothered to tell Sigil where it was moved to (or where to install it): either via the -DSHARE_INSTALL_PREFIX cmake command at compile time (which would make the most sense in this case, I think). Or by setting the SIGIL_EXTRA_ROOT environment variable in the launch script at run time.

All of this is documented in the build instructions.

Last edited by DiapDealer; 10-11-2019 at 12:21 PM.
DiapDealer is offline   Reply With Quote