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


On 16.08.2017 19:48, Shinnok wrote:

Another question would be, if gettext is a hard dependency, why not
fetch it during the autogen.sh just like libboost&co. are? Did anyone
try to do that and failed for some reason?

the stuff fetched via download.lst has traditionally been only stuff
that is bundled into the installation set.

although in recent times build tools started to appear, in particular
validator jar files.

however make fetch can't be used to download anything that's required to
run configure and make, so no cygwin, make, or compiler.

whether anybody wants invest effort into writing the makefiles to build
gettext etc. on all platforms is of course an open question.

Regarding doxygen, that is a requirement only for the UNO libs right?
Then in this case we should either not make it a hard dependency during
the configure stage or make it obvious that it needs to be excluded
manually via --without-doxygen otherwise autogen.sh will fail. I'm more
inclined towards the former, if there's no outstanding reason against
doing so.

hopefully the error message printed by configure when it can't find
doxygen makes it obvious how to do the latter?

I think it's important we get the default build working from top to
bottom without pitfall, I already have mentee reports that tripped over
this and never advanced, so I'd like to fix this.

[1] https://wiki.documentfoundation.org/Development/BuildingOnMac#Minimal_Setup

i was thinking that LODE was supposed to install everything
automagically but i don't have a Mac ...


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.