Building Sigil on Haiku

[DiapDealer]

Originally Posted by User_Z

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.

[DiapDealer]

Originally Posted by User_Z

This is a good idea. Not for everyone. The package in the repository is for everyone. Compile it yourself for enthusiasts. I already went through this.

You don't seem to get it. The same code is used to build Sigil by repo maintainers and by individual enthusiasts alike. The suggestion Kevin made would be something to help both.

[User_Z]

In the assembly recipe, this option is set.

	cmake .. \
		-DCMAKE_BUILD_TYPE=Release \
		-DCMAKE_INSTALL_PREFIX=$appsDir/Sigil \
		-DCMAKE_INSTALL_BINDIR=$appsDir/Sigil \
		-DSHARE_INSTALL_PREFIX=$appsDir/Sigil \
		-DCMAKE_INSTALL_LIBDIR=$appsDir/Sigil/lib \
		-DPYTHON_LIBRARY=$pythonLib \
		-DPYTHON_INCLUDE_DIR=$pythonInclude \
		-DPYTHON_EXECUTABLE=$pythonBin \
		-DUSE_SYSTEM_LIBS=1 \
		-DINSTALL_BUNDLED_DICTS=0

Maybe the problem is something else?
For example in this library tkinter or other path?

[DiapDealer]

And yet not a single one of those options is the one I mentioned. I know what's in the build recipe for HaikuPorts. I've studied it extensively. That's how I know they're deleting the launch script altogether. Without replacing its functionality with something else.

And it's nothing to do with tkinter. There is no HaikuPorts package for tkinter. I expected that to fail. And I mentioned the hunspell test would likely fail (because they've created no link from libhunspell.so to their versioned system libhunspell-1.7.so). The tragic failure there is the plugin framework not being able to perform the libsigilgumbo test for some reason.

[User_Z]

DiapDealer

Are you a secret agent? What do you beat around the bush? What are some of these reasons?
If you know or suppose, then speak already.

[DiapDealer]

I'm through. I've got better things to do with my time.

[KevinH]

He already did clearly explain what needs to be done to fix your port and has included a text file that explains exactly where to fix things. And he has explained what build flags are needed and the build docs that explain. He did this all in this very thread.

If you are not a programmer at all, perhaps you should pass a link to this thread along to someone involved with Haiku that actually is a developer, so that plugins will run in the Haiku version of Sigil.

FWIW, porting software is not just trying to build it and stopping when you run into difficulies or things you do not personally like.

[User_Z]

Test Plugins...

[KevinH]

Looks much better. You can fix 2 of those failures quite easily by installing the python projects: cssutils and regex. Both are pure python modules so should install with no problems. You should also try to install PIL (pillow) for graphics support. That should only leave tk grpahics module.

Has no one ported the tcl / tk libraries to Haiku? They are typically one of the first graphics libraries ported as they allow graphical user interfaces for perl, and python.

[User_Z]

HaikuDepot...

[theducks]

Originally Posted by User_Z

HaikuDepot...

IMHO The description is still the OLD one. (Devs: can we purge this everywhere?)
Silgil is not WYSWYG in the sense that you work in the resultant (formerly Bookview) view

[BetterRed]

Originally Posted by theducks

...
Silgil is not WYSWYG in the sense that you work in the resultant (formerly Bookview) view

BR

[DiapDealer]

Originally Posted by theducks

(Devs: can we purge this everywhere?)

We've purged it everywhere we have the power to do so. As BR already mentioned, however, the version of Sigil available on Haiki IS still a WYSIWYG version of Sigil.