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


On Tue, Nov 02, 2010 at 11:02:56PM +0100, Gert Faller <gertfaller@aliceadsl.fr> wrote:
1) I update the 'clone' directory often. No problem with that.
2) I've read that when updating 'clone', 'bin/g' must be run.
   I don't find any 'g' in ./bin/.
3) I don't know how to update easily the source in 'build/libreoffice-3.2.99.2'
4) I edit code in 'clone/module' and 'git diff' from there but, for building,
   I have to go to 'build/libreoffice-3.2.99.2/submodule' where I have done a
local
   git, modify the patch (paths are too long in it eg :
   a/module/submodule --> a/submodule), 'apply' it, 'build', 'apply -R', and if
   it's ok, get back to clone/module and undo my work (with the editor or with
   'apply -R')

There must be an other way less tedious...

http://thread.gmane.org/gmane.comp.documentfoundation.libreoffice.devel/1133

Have you seen this thread? Basically if you want to contribute, not just
build, then the best is to build in rawbuild, then you can easily test
your changes.

Attachment: pgpO5hgPx4Him.pgp
Description: PGP signature


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.