Posts mit dem Label Compiling werden angezeigt. Alle Posts anzeigen
Posts mit dem Label Compiling werden angezeigt. Alle Posts anzeigen

Dienstag, 27. September 2016

The abi trouble :)

So how to start porting?

Day one:
Of corse the first thing was checking out the source. I used the github mirror of the svn repository because i starting to get used to git ;-)

I tried to follow the documentation how to build abiword it didnt worked out Since they dont use anymore.
./configure 
But this was not documented. Since i am Not a buildsytem pro
It lasted a while until i discovered the
autoconf
Running the autogen.sh gave some errors:

m4:configure.ac:226: cannot open `m4/plugin-list.m4': No such file or directory
m4:configure.ac:990: cannot open `m4/plugin-builtin.m4': No such file or directory
m4:configure.ac:992: cannot open `m4/plugin-configure.m4': No such file or directory
m4:configure.ac:1192: cannot open `m4/plugin-makefiles.m4': No such file or directory
autom4te: m4 failed with exit status: 1
While asking irc & google how to solve this Problem i cheked the listed dependencies. I really hoped that they the documentation at least had up to date dependencies.

So i did a:

pkgman install zlib_devel libpng_devel libiconv_devel fribidi_devel popt_devel


Day two:
Scanning through the help output of configure i Fond finally the switch to enable QT
So i did a:
autogen.sh  --enable-qt

To Fond me greeted with this warnings / errors:
libtoolize: Remember to add `LT_INIT' to configure.ac.
plugins/collab/backends/telepathy/unix/Makefile.am:21: warning: '%'-style pattern rules are a GNU make extension
./configure: line 17820: syntax error near unexpected token `-Werror=unknown-warning-option,'
./configure: line 17820: `AX_CHECK_COMPILE_FLAG(-Werror=unknown-warning-option,'
Thanks to the help from korli and PulkoMandy i understood that there where mitsingen autoconf archive files
I did a git clone of the autoconf archive repo ..after some trys to "install" it, i realized that i just need to copy the m4 Files from this repo into the m4 folder of the cloned abiword sourcetree.
Btw the abiword irc didnt responded once to my questions...

After running autogen again i saw that i was missing the boost libs .. since they are only available in _x86
I did a:

setarch x86

pkgman install glib2_x86 fribidi_x86
pango_x86 cairo_x86 boost_x86

Configure at least run way longer
But it told me what libs are missing:

  • Libgsf (there is a brocken recepie in haikuporter)
  • Wv (abiword lib for reading doc files but it also need libgsf)
  • Goffice (maybe only for one of the plugins?... i need to research this further)
  • Some more i didnt checked yet
I think i will only find time to continue work on this next week

Sonntag, 15. März 2015

First steps

Ok so i am trying to look into how ot port abiword to haiku.
Because i dont have so much time and i am not so skilled i will try to document my progress here on this blog.

Day one
Two or tree month ago i already downloaded abiword from haikuarchives
https://github.com/HaikuArchives/AbiWord
its a verry old version but it should compile - should!.
First running make i am greeted with a error.


Found libwv in peer directory
/bin/sh: line 4: ./configure: Permission denied
make[3]: Entering directory `/Haiku_Daten/dev/AbiWord/wv'



So what to do? After  a while i rememberd that pulkomandy showed me the solution some month ago, when i tried first to build Abiword.
So i checked back in the commits and found that the execute flag on the config file in AbiWord/wv was not set.

So after setting this flag, and reinstalling mississing libs like psiconv, popt and so on, Abiword compiled.