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


On Mon, Nov 22, 2010 at 8:48 PM, Kohei Yoshida <kyoshida@novell.com> wrote:
On Sat, 2010-11-20 at 18:40 -0500, Norbert Thiebaud wrote:
On Thu, Nov 18, 2010 at 10:18 PM, Jan Holesovsky <kendy@suse.cz> wrote:
Hi,

In case you are interested to try to build without the 'build' repo (the
rawbuild/ way), you can try to get the feature/rip-build-repo branch
which I hope is going to become the 'official' way of building soon ;-)

btw, I got it working on MacOS

I built it on Windows too.  The only issue I've encountered is that the
initial autogen.sh run checks for presence of certain dll files in the
external module, and it fails because the external module was not there.
The solution was to run g clone first, then run autogen.sh.

Argh, that is annoying. I managed to hide the git clone and the
./download step into the make
but you can't make before autogen... chicken and egg thing...
Any possibility to postpone these check or only do them if the autogen
option says --with-system for these dll (i'm guessing here), with the
understanding that if you are using the 'built-in' ones they will
pulled in ?


--
Kohei Yoshida, LibreOffice hacker, Calc
<kyoshida@novell.com>

_______________________________________________
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.