Hi Christian, et al,
On 2011-01-24, at 7:00 AM, Christian Lohmaier wrote:
Hi David, *,
On Mon, Jan 24, 2011 at 2:26 AM, David Dumaresq <dfdumaresq@gmail.com> wrote:
On 2011-01-23, at 7:28 AM, Christian Lohmaier wrote:
On Sun, Jan 23, 2011 at 9:16 AM, Jonathan Aquilina
<eagles051387@gmail.com> wrote:
[…]
[1] You don't need /any/ external dependency unless you want to
compile mozilla/seamonkey from scratch (i.e. when not using
--disable-mozilla).
Then you /need/: libIDL and glib2 and gettext (and pkg-config for convenience).
All the other stuff is useless and not needed at all.
But you should get ccache as well, to speed up subsequent builds
(http://ccache.samba.org)
So what you're saying is, if my goal is to develop for libreOffice on OSX, I don't need any of
the dependencies mentioned above.
Exactly. You only need XCode with the 10.4u SDK when using --disable-mozilla
Unless you want to hack on document signing, ldap access or mozilla
address book integration, you don't need mozilla.
ciao
Christian
After removing & cleaning up the macport packages (coreutils, etc), I installed git and downloaded
the source and attempt to run ./autogen.sh
./autogen.sh
./autogen.sh: /usr/local/bin/aclocal: /opt/local/bin/perl: bad interpreter: No such file or
directory
I'm not sure what believes perl is in /opt/local/bin? On my system (osx 10.6.6), perl is in /usr/bin
I have since created a sym link and autogen runs, but I wonder if you have any ideas about this?
Thanks,
Dave
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.