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 ;-)
git clone git://anongit.freedesktop.org/libreoffice/bootstrap libo
cd libo/
git checkout -b rip-build-repo origin/rip-build-repo
./autogen.sh [flags that you normally use in rawbuild/]
./g clone
./download
make
make dev-install
[./g is there in toplevel, but can be in bin/, I am not sure what is
more convenient for you?]
How does it look like? The repos are again in a clone/ subdir, but this
time, they are linked to the bootstrap toplevel (libo/ in the example
above), so you 'feel' like having everything at hand. 'g' works both on
bootstrap and the repos in clone/, so you don't need to do "git
something && g something" any more, one "g something" is enough.
It is not ready for integration yet, TODOs:
- ./autogen.sh should work without params for most uses (ie. default to
the same values as ./autogen.sh in the build repo does)
- this means tweaking the default values according to the
distro-config/LibreOffice*.conf.in
- ./g clone should be called in ./download, when necessary
Let me know if you actually prefer to have it integrated ~now, it should
not interfere with the build/ repo in general, and would allow/pressure
others to help me fix the above mentioned TODOs :-)
Regards,
Kendy
Context
- [Libreoffice] feature/rip-build-repo - branch for removal of the need of the 'build' repo · Jan Holesovsky
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.