On 03/28/2011 12:25 PM, Fernando Oliveira wrote: > --- Em dom, 27/3/11, DJ Lucas<d...@linuxfromscratch.org> escreveu: > >> De: DJ Lucas<d...@linuxfromscratch.org> >> Assunto: Re: LibreOffice-3.3.2.2 >> Para: blfs-support@linuxfromscratch.org >> Data: Domingo, 27 de Março de 2011, 15:35 >> > > Thank you for your mail. > >> LibreOffice suffers the same problem and I >> do not recommend it for the book unless a rather large >> group of people can come to a consensus on "required" dependencies. > > Please, include me in the group. > >> Here are the buildopts for OOo's configure that were used >> in that patch set. Note that this is not for the top level configure >> script, but for OOo's internal configure script after LibreOffice >> does it's thing to the source tree >> (no mono patches were applied in the set I had defined): >> >> PKG_CONFIG=/usr/bin/pkg-config ./configure \ >> --disable-odk --disable-qadevoo --disable-fontooo \ >> --enable-cairo --enable-opengl --enable-dbus \ >> --enable-gio --disable-kdeab --enable-minimizer \ >> --enable-presenter-console --enable-pdfimport \ >> --enable-wiki-publisher --enable-report-builder \ >> --without-fonts --without-ppds --without-afms \ >> --with-system-stdlibs --with-system-cairo \ >> --with-system-zlib --with-system-openssl \ >> --with-system-jpeg --with-system-expat \ >> --with-system-libxml --with-system-python \ >> --with-system-poppler --with-system-db \ >> --with-system-libxslt --with-system-odbc-headers \ >> --with-system-xrender-headers --with-system-curl \ >> --with-system-boost --with-system-neon \ >> --disable-gnome-vfs --with-dict=ALL \ >> --with-vendor="BLFS" --with-build-version=3.2.1-1 \ >> --with-package-format=native --with-use-shell=bash > > Next time, I will try using option closer to these. >
Actually, I think those were the incorrect ones.... I forgot, I had deleted my local change sets, however, I had put them in my home directory for safe keeping: http://www.linuxfromscratch.org/~dj/ooo-build-3.2.1.4-BLFS_Config-1.patch >> As you can see, I was pretty heavy handed with the >> dependencies and am honestly not comfortable making decisions about _your_ >> systems. Unfortunately, this is what was required to get what I >> deemed "full functionality" out of the build with the least amount of >> internal products (based on what we have in BLFS now). > Same comments apply...however, it might be possible to encourage the upstream developers to add a couple of generic targets (or we can do them locally), say --with-vendor={KDE3,KDE4,GNOME2,GNOME3}. That would make the patch somewhat complex but would certainly make the book more readable and more malleable for different installations. They could, of course, be called anything we want if kept locally. ie: BLFS-GNOME3, BLFS-GNOME2, BLFS-TRINITY, BLFS-KDE4... > Probably you know already, the page > > http://wiki.documentfoundation.org/Development/How_to_build/Configure_options > > has some information. I include the address here, in order to be used by me > and others. > Thanks for the link. Looks like a few things have changed with the predefined patch sets so that patch may be of little use other than a generic set of directions now. -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
