On 22/05/12 11:07, Tor Lillqvist wrote:
We could also just suggest installing MacPorts and pulling the necessary
tools. I do that on my mac box and it works a treat.
On the other hand, we have traditionally been trying hard to educate
people to *not* mess up their Mac build by involving MacPorts, as it
has caused harm and confusion. Can one install *only* automake and
autoconf from MacPorts?
does MacPorts have a hardcoded default location where it installs its
stuff? (the Fink i used years ago put everything in /sw)
can we
a) hack autogen.sh to invoke a "autoconf" in MacPorts' location (and
maybe Fink's as well) if it exists
b) put some check into configure that whatever part of MacPorts messes
up the build (or just something that identifies MacPorts) is not on $PATH?
[pity that Apple has to make life more difficult for developers again]
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.