Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Then, let not push my 'useless' patch lol :')
Sorry and thanks for detailed explanation.
--
Korrawit Pruegsanusak



On Mon, Mar 7, 2011 at 16:45, Bjoern Michaelsen <
bjoern.michaelsen@canonical.com> wrote:

On Mon, 07 Mar 2011 01:52:11 -0700
"Tor Lillqvist" <tlillqvist@novell.com>
wrote:

I hope someone with more knowledge on this will jump in and clarify,
but I *believe* these precompiled_foo.hxx headers are automatically
generated,

I think Bjoern told me on IRC that they were automatically generated
initially (at the time indicated, years ago), yes, but then the
script that was supposed to re-generate them was found to be broken,
or something, and the script is in any case not included in the OOo
or LO sources (!), so they have in fact been manually updated (by OOo
developers) since (sigh).

What you really want to do is build the precompiled_header sources from
the generated dependencies of the objects linked in the library
(including a set with those that are as included most). As the deps in
the new build system are plain text files, it should be rather easy to
reactivate the automatic generation of precompiled_headers then.

Best Regards,

Bjoern

--
https://launchpad.net/~bjoern-michaelsen


_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.