422: abiword 2.7.8

I have upgraded Abiword from 2.7.7 to 2.7.8.

I have removed the Presentation module as it causes abiword to crash. Hopefully that will be remedied soon.

2.7.8 now does not use non-scalable fonts, so don't need to exclude any in ...er, I just tested, Dingbats and StandardSymbols still don't display properly, so I will still have to exclude those.


Posted on 5 Aug 2009, 23:49


Comments:

Posted on 7 Aug 2009, 3:59 by linuxcbon
compile abiword
Do you think
./configure --prefix=/usr
is enough to compile it ?
I used it and made a pet.
What's weird is we need to add that prefix. It should know by default where, in /usr/. Without that prefix, it is installed in /usr/local/ which is wrong.


Posted on 7 Aug 2009, 8:14 by BarryK
Abiword configure
technosaurus figured out good configure options:

http://puppylinux.com/blog/?viewDetailed=00912



Posted on 7 Aug 2009, 8:36 by linuxcbon
compile
Thank you.

I asked in the abiword mailing list, they told me the default option installs in /usr/local/

So I only used ./configure --prefix=/usr and I got a pet of 3Mb, which is normal(I trimed stuff though).



Posted on 8 Aug 2009, 2:28 by technosaurus
even smaller
I posted this into the pet packaging 100 and 101 sticky - it helps the linker shrink binaries by 5 to 50%

CFLAGS/CCFLAGS
-Os -ffunction-sections -fdata-sections

LDFLAGS -Wl,-O1,--gc-sections

NOTE: on certain programs that compile intermediate static libraries, this process fails. This can be remedied by omitting the LDFLAGS --gc-sections portion, deleting only the compiled executable(or shared library), then adding the --gc-sections back into the Makefile and recompiling
(-Os and -O1 are just standard size optimizations the others allow the linker to "garbage collect" otherwise inaccessible areas with duplicate/unnecessary "garbage")

also these strip commands tend to work well on most binaries and libraries (most binaries can use --strip-all)

strip --strip-unneeded --remove-section=.comment --remove-section=.note

(there are also some better options if we ever upgrade to gcc 4.4.1+)