<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 25, 2017, at 12:18 PM, Tor Lillqvist <<a href="mailto:tml@iki.fi" class="">tml@iki.fi</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto" class=""><div class="">GNU gettext package is available in Homebrew.</div><div class=""><br class=""></div></div></blockquote><div class=""><br class=""></div><div class="">But we have traditionally strongly advised against polluting one's build environment on macOS with Homebrew and similar. Has this changed?</div><div class=""><br class=""></div><div class="">--tml</div><div class=""> </div></div></div></div></div></blockquote><br class=""></div><div>Ok. Then in this case we better clean up the Wiki to explicitly declare *all* extra packages that are needed for a Minimal Build [1] and how they are supposed to be installed. The order of preference as I get it should be:</div><div><br class=""></div><div>1. Manual download, configure & make install;</div><div>2. Some package management. Currently MacPorts is hinted on the Wiki, why not Homebrew too?</div><div><br class=""></div><div>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?</div><div><br class=""></div><div>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.</div><div><br class=""></div><div>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.</div><div><br class=""></div><div>[1] <a href="https://wiki.documentfoundation.org/Development/BuildingOnMac#Minimal_Setup" class="">https://wiki.documentfoundation.org/Development/BuildingOnMac#Minimal_Setup</a></div><div><br class=""></div><div>Regards,</div><div>Shinnok</div></body></html>